Your feedback helps us catch bugs, improve usability, and build better software. You don’t need to be a developer—spotting confusing instructions, unreadable text, or a button that does absolutely nothing counts too.
Before diving in, please read these guidelines.
1. Understand what beta means
Beta software is still being developed. Features may change, updates can introduce problems, and test data may be reset or removed.
Use test files and content you can afford to lose.
Back up your files and database before installing or updating.
Avoid using beta builds for essential production work.
Never upload confidential information, real customer data, or sensitive documents.
Use designated test payment methods unless staff explicitly arrange otherwise.
2. Write useful bug reports
Search existing reports before starting a new one. If the issue already exists, add your findings there.
Report one issue per topic and use a descriptive title. “Settings disappear after restarting” tells us more than “Doesn’t work.”
Copy this template when reporting a problem:
Product name:
Version/build:
Operating system:
Browser and version, if applicable:
Theme/addons/extensions involved, if applicable:
Desktop or mobile:
Steps to reproduce:
1.
2.
3.
What you expected:
What actually happened:
Does it happen every time?
Screenshots or relevant error messages:
Workaround, if you found one:
Remove passwords, license keys, API keys, tokens, personal information, and private server details before posting screenshots or logs.
If an update fixes your reported issue, please return and confirm it.
3. Test normal use—not just the shiny features
Try the tasks you would actually use the product for: installation, updates, settings, navigation, uploads, saving, editing, and restarting.
Where supported, check:
- Light and dark modes.
Different screen sizes and mobile layouts.
Keyboard navigation and readable text.
Error messages and recovery after a failed action.
Whether settings remain saved after refreshing or restarting.
Compatibility with the relevant host application, theme, or addon.
Tell us what you actually tested. A quick look and a complete workflow are both useful, but they provide different evidence.
4. Keep feedback respectful and constructive
Honest criticism is welcome. Explain what went wrong, why it matters, and what would make the experience better.
No harassment, personal attacks, hate speech, or targeted abuse.
No spam, repeated demands, or deliberately derailing reports.
Respect differences in experience and technical knowledge.
Don’t pressure other testers to provide support.
Keep discussions focused on the product and issue being tested.
Critique the software, not the person. Bugs already create enough drama without casting us all in the sequel.
5. Respect access, licenses, and testing boundaries
Access to a beta does not automatically grant permission to redistribute it.
Don’t share private builds, paid packages, license keys, or restricted downloads without permission.
Test only devices, installations, and accounts you’re authorized to use.
Don’t run destructive tests, automated flooding, or load tests without staff approval.
Don’t access or alter another person’s content or data.
If you discover a security problem, report it privately to an administrator. Don’t post exposed information or exploit instructions publicly. Stop once you have enough information to describe the issue safely.
6. Allow time for investigation
Staff may ask for additional details or a retest on a newer build. Duplicate reports may be merged, and some issues will take longer to resolve than others.
Suggestions are welcome, but submitting an idea does not guarantee it will be added. Beta access also does not promise a release date, free license, or reward unless a specific testing program states otherwise.
Accounts that abuse the testing environment or repeatedly ignore these guidelines may lose testing access.
Want to become a Beta Tester? Signup here now.
Thanks for helping improve Zovanta Software. Now let’s find the bugs before they start charging rent. 😄