Beta Testing

Are you interested in development collaboration opportunities? Do you have the type of team that dives into new software with enthusiasm? Do you have ideas on which new eDOC software features would the best benefit your credit union? 

 

If you are willing to help us test new software versions, you may just get your wish. We are excited to welcome our peers to participate in our beta testing process. If your credit union would like to participate in the beta testing of new software versions, we need you! If you are interested, please contact our Client Development team.

 

What a Beta 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 and passes along information about the software changes and beta test procedures to all other CU employees.
  • Tests (or at least tries) every new feature in the release, even those they do not normally use.
  • Logs details from all CU employees about problems found, including samples of error messages, research into the specific steps taken, conditions at the time the problem occurred, and what the employee saw and experienced.
  • Contacts eDOC quickly when issues arise so they can be researched and addressed in a timely manner within the beta period.
  • Gives specific, detailed feedback about new features and enhancements.

 

What a Beta Site Receives

  • Early Training – Our Support team (and item processing team where applicable) will hold a beta training for your designated contact person(s) to explain what will be changing and any specific areas we need you to concentrate on for special testing. We will record this session and make it available to your team in case they can’t make the session.
  • Early Documentation – We’ll have a draft of the release notes ready for your employees. This will give an overview of all of the major changes in the release. You may need to supplement this with special instructions for your staff according to your situation.
  • One-On-One Support – A representative from our Support team will work directly with your designated contact person(s) to answer questions and relay information about updates.
  • Prompt Attention – As program adjustments are needed to address issues that arise during beta testing, our team will work to make sure you receive regular updates.

 

Beta Site FAQ's

Q: Is there a limit to the number of CU's that can be in the beta pool for a release?Q: Is there a limit to the number of CU's that can be in the beta pool for a release? 

 

 

 

Q: I'd like to be a beta site, but my coordinator is out of the office during part of the beta period. Can I still participate?Q: I'd like to be a beta site, but my coordinator is out of the office during part of the beta period. Can I still participate? 

 

 

 

Q: Will there be documentation for my staff to use?Q: Will there be documentation for my staff to use? 

 

 

 

Q: Can my credit union be a beta for more than one software version in a beta period?Q: Can my credit union be a beta for more than one software version in a beta period? 

 

 

 

Q: Who do I contact if I have questions or issues during beta?Q: Who do I contact if I have questions or issues during beta?