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?
Earn CollabRebate $$ for beta-testing!
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!
Specific Requirements for the Next Release
|Beta Test Begins||Full Release to Online CUs||Teams Affected Most|
|19.10||September 15, 2019||October 20, 2019||
|CollabRebate for Beta Test: $3,000
Beta CUs selected: TBD
|CUs Eligible for This Release||Eligible||Reason|
|Xtend Shared Branch Participants||No||Because of changes to the member tables in this release, CUs using Xtend Shared Branching will not be able to participate in this beta.|
|CUs with shared employee arrangements with other CUs||*||*It is not possible for a CU in a shared employee arrangement to participate in a beta-test unless all parties in that arrangement also agree to participate in the beta. Other eligibility rules also apply.|
|Co-Op (National) Shared Branching Participants||Yes||CUs using Co-Op Shared Branching will be able to participate in this beta.|
|Data Analysts||Yes||This release includes many VAT enhancements, as well as multiple updated tables impacting data analysis and reporting.|
|EFT||Yes||Included in this release are enhancements to address handling for member ATM/debit cards, as well as changes to the credit card ordering process for CUs using multiple PAN. A strong EFT team offering multiple PAN credit cards is desired.|
|Member Service (& Online Banking)||Yes||We are seeking a strong member service team to test additional features and updates, including new Skip Pay frequencies, employee security templates and tools, Tracker improvements, workflow changes, and new eAlert options. We would also like a credit union to test the new member-driven online banking activation scheme for first time enrollment.|
|Accounting||Yes||Accounting staff should be aware and ready to test changes to the GL chart of accounts and investments register.|
|Audit||Yes||This release will include the full deployment of the BSA auditing tools.|
|HSA Certificates||Yes||We are interested in a CU that has a desire to implement HSA certificates.|
Feedback From Recent Beta-Tests
- 19.05 Beta Mid-Test Feedback (all CUs)
- 19.05 Beta Final Feedback (all CUs)
- 18.07 Beta Mid-Test Feedback (all CUs)
- 18.07 Beta Final Feedback (all CUs)
- 17.10 Beta Mid-Test Feedback (all CUs)
- 17.10 Beta Final Feedback (all CUs)
- 17.03 Beta Mid-test Feedback (all CUs)
- 17.03 Beta Final Feedback (all CUs)
How to Earn the Beta-Test CollabRebate
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? 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!
…keep reading to learn about what you’ll be committing to, and what you’ll get as a beta-tester.