Every new feature we build goes through at least 2 weeks of beta testing to make sure it's bug-free, user-friendly, and is the right solution to our churches' problems. Our team of beta testers is crucial in evaluating these improvements and giving us feedback about what works, what doesn't, and what could be improved. We are always looking for more people to join our beta testing team, so we get plenty of feedback before we release new features to the thousands of churches we serve.
Think your church would be a great beta tester? Are you the Master Administrator? Sign up to join our Beta Testing team today!
We think the Beta testing program is a great way for your voice to be heard in the development process. But don't just take our word for it. Here what one beta tester has to say:
|Why would I love beta testing?
||I'm worried about bugs in the software.
||How else do I make an impact?
Need some more information first? Check out our beta FAQs.
Frequently Asked Questions
Who is the ideal Beta Tester?
You would be a great fit for beta testing if you like to try out new things and provide feedback about what worked and what didn't. We especially appreciate people who can help us understand how their church operates and why their request would help make their lives better. The ideal beta tester isn't rattled by change, and they have a good process at their church for communicating about changes to other people too.
What are the benefits of beta testing?
In addition to our eternal gratitude, you get new features and bug fixes before anyone else. You also get to play a vital role in shaping the future of the Church Community Builder software, providing feedback and recommendations that will benefit thousands of churches.
What are the risks of beta testing?
While our team tests everything thoroughly before we release it, the beta code is inherently buggier than the stable version, especially around the new features being released. Changes happen more frequently and with less notice than on the stable code, so things may also feel less stable because of those changes.
How often do things change in beta?
We release new features to beta as frequently as every 2 weeks, and iterations or improvements to those features can come out daily. While beta can be a bit buggier than stable, bug fixes can also go out very quickly. So if something is broken in beta, it won't stay broken for long.
Does my whole church have to be on beta?
Yes. When you sign up to be a beta testing church, your entire Church Community Builder site is moved over to the beta branch of code. This means everyone who logs into your site will be experiencing the beta version. You may want to think through how you handle communication internally to make sure your people are informed about any software changes that happen during beta.
Why does my Master Administrator have to sign us up?
Your MA is your church's local expert on your instance of the Church Community Builder software, and our primary point person when it comes to communication. We want to make sure they are aware of any changes happening related to your account. If you aren't sure who your church's MA is, in your site, go to Help & Support > Church Contact Info.
How is communication handled when you're a beta tester?
We have a dedicated Beta Tester group in our Village site. When you join beta, we add you to that group. That is where all communication happens about new features, and we encourage you to post all of your questions, comments, and feedback through that group. You can have several members of your church participate in the beta testing group, and we encourage you to include anyone who would be directly affected by the changes and would provide helpful feedback.
What kind of time commitment is beta testing?
Plan on spending a couple of hours a week reading about new features, trying them out, and responding to comments in the group. Our beta testing program is the most effective when testers are really active in telling us about their experiences, so if you or someone from your church doesn't have time to participate in the dialogue, beta testing might not be for you.
How do I exit beta testing?
Moving to the beta code branch sometimes means there are database changes that happen to your church's site that can't be reversed until that feature is released to stable. Because of this, you can only leave beta at designated "off-ramp" times, which is typically every 8 weeks.
I don't think I'm ready to commit to beta testing, but I still want my voice to be heard!
We totally understand. Beta testing can be a big commitment, and it isn't for everyone. If you still want to provide us your thoughts about the future of the Church Community Builder software, consider joining our PEP Squad. This is a group of people who are willing to take surveys, answer questions, and try out prototypes of new ideas as we try to determine the future direction of the software.
I'm still on the fence. Can I talk to a human?
Yes! If you still have more questions or concerns before making the commitment, email us at firstname.lastname@example.org.