So what’s the difference between beta and “active” beta?
This page describes traditional beta testing for software prior to full implementation to all clients. Active beta is a whole different animal that lets us release live software in the field, for everyone to test over an extended period. Learn more about Active Beta
Does your credit union like to be in on the ground floor of new tools and ideas?
Have you got the kind of team that dives into new software with enthusiasm?
Are you an early adopter just chomping at the bit to get at that next new software feature?
If you’re willing to help us test other new tools at the same time, you just might get your wish.
We’re always on the lookout for credit unions willing to participate in the beta-test period for major CU*BASE software releases. If your credit union would like be in the pool considered for beta testing new features and enhancements, we need you!
Earn CollabRebate $$ for beta-testing!
To increase the effectiveness of our beta-test process, we need as many eligible CUs in our beta pool as possible. We recognize that beta-testing is an added challenge for your busy teams, and we also know how important a good beta-test is for the success of our releases with all of our clients. So we’re putting our money where our mouth is by offering a CollabRebate reward for active beta-test participants.
- How much money are we talking? For each of our 2-3 major releases per year, we’ll offer between $2,500 and $5,000 per beta-test CU. The amount will be determined prior to the release according to the number of projects and relative complexity of the release. For example, for a recent release we offered a beta-test CollabRebate of up to $3,000.
- What do you mean, “up to?” If your credit union actively participates in the beta by staying in contact with our teams and completing the necessary feedback forms, we’ll award the full amount. (In the past we have had credit unions start off with a bang then back out partway through the test period, so we do reserve the right to adjust the amount if appropriate, based on a credit union’s actual participation.)
- What do we have to do? You’ll need to agree to the rules and tasks outlined below, including completing our feedback form and returning it to our QC team within 1 week after the end of the beta test.
- Can anyone be a beta? As described in more detail in “Part 2” below, not every release can be beta-tested by every credit union, so first check the requirements to see if you are eligible. And while we do want multiple beta test sites, we need to keep the project manageable. So we reserve the right to choose the final selection of beta CUs for each release.
- When will I know I am in the beta? We will make the announcement on the Wednesday three weeks prior to the beta test start date. You will contacted immediately by our QC team to arrange for your training web conference a week or two prior to the beta release.
- What if I can’t gear up my team that quickly? Then perhaps beta-testing is not right for your credit union. The reality of our development track is that software releases move very rapidly. Our beta credit unions need to be able to hit the ground running. But rest assured we are behind you every step of the way and you will receive targeted, one-on-one support during the beta period. And don’t forget that CollabRebate waiting for you when you hit the finish line!
What a Beta CU Does
- Assigns a designated contact person(s) to coordinate directly with our QC team at least once a week during the beta period.
- Attends beta training (done via web conference) and passes along information about the software changes and the beta-test procedures to all other CU employees.
- Tests (or at least tries) every new feature in a release…even stuff they don’t normally use a lot.
- Logs details from all CU employees about problems found, including samples of error messages, research into the specific steps taken, conditions at the time of the problem occurred, and what the employee saw and experienced.
- Contacts us quickly when issues arise so we can research and address them in a timely manner within the beta period.
- Gives specific, detailed feedback about new features and enhancements to help our testers and documentation teams.
What You Get from Us
- Early training…Our QC and documentation team will hold a beta-training web conference with your designated contact person(s) to explain what will be changing and any specific areas we need you to concentrate on for special testing (for example, we may want you to work with software as is for a while, then change a configuration setting and work with it some more under the new settings).
- Early documentation…We’ll have a draft version of the Release Summary ready for your employees. This will give a basic overview of all of the major changes in the release (we’ll use this summary during our training with you). You may need to supplement this with special instructions for your staff, according to your situation.
- One-on-one support…A representative from our Quality Control team will work directly with your designated contact person(s) to answer questions and relay information about updates.
- Prompt attention…As we make program adjustments and address issues that come up during the beta period, you will receive regular GOLD updates. This typically happens about once a week, but could be even more often if needed. Our goal is to keep your teams working, so we work hard to address critical issues quickly.