User Acceptance Testing
User Acceptance Testing (UAT) acts as the last phase of the software development process where business functions are tested in a real-world scenario. If the software works as required and without issues during normal use, one can reasonably extrapolate the same level of stability when the software is released.
The UAT scenarios are critical to validate the software before going live. The scenarios should be based on best practices to ensure they are within the bounds of what is being implemented. UAT also further enhances the user’s education of NetSuite and helps reduce go-live and post go-live issues. Verifying the software and potentially uncovering unknown issues before going live are essential elements for customer success.
UAT Considerations
User Acceptance Testing should be done in a test environment, such as a sandbox or development account. The test environment should be safe and isolated from the production environment, and it should permit users to develop and test new implementations and customizations without affecting the production environment. Define your user base as accurately as possible, and identify a test case that is based on a real-world scenario so that your UAT reflects real use cases as much as possible.
To learn more about NetSuite’s different account types, see Understanding NetSuite Account Types and NetSuite Development Accounts.
Understanding UAT Performance
User Acceptance Testing (UAT) is a structured testing process that makes sure that all requirements are performing as the user wants and expects. During UAT, users may experience some aspects of the testing that may not meet their performance expectations, such as how long it takes to load a form or UI, save or edit a record, or complete an end-to-end process.
When an application’s performance affects the overall goal of each test, it’s crucial to understand the different factors that may contribute to the application's behavior. Knowing how to identify and isolate these factors is an essential part of understanding the issue.
To understand how these factors can affect user testing, see Tips to Optimize Performance.