Release testing

As a customer testing a software release, you'll primarily focus on user acceptance testing, which involves verifying if the software meets your specific needs and works as expected in real-world scenarios. This process helps identify bugs and issues that might not be caught by internal testing, ensuring a production-ready product.

1. Understand the release: Familiarize yourself with the new features, changes, and expected behaviors of the release. Review the documentation, release notes, and any support tickets marked as fixed by the release by Jadu.
2. Test with real-world scenarios: Use the software as you would in your normal workflow, performing tasks that are critical to your work and the purpose of the software. Ensure that business critical features that impact your front-end users, such as integrations and form processes, are also tested.
3. Test customizations: Check any custom developments or integrations specific to your version of the software.
4. Identify and report issues: If you encounter any bugs, errors, or functionality issues, document them with clear steps to reproduce, screenshots, and a description of the expected vs. actual behavior and raise a support ticket.

tip

You may find creating your own spreadsheet listing everything you want to test helpful to ensure you follow the same process and scenarios for each release.