Post-production Monitoring
Once the application is deployed to the production server. Now, it’s time for testers to check the application on the production server.
Step 1: Smoke Testing
This testing is carried out by developers once the deployment is done. Developers will usually check whether the updated changes are reflected, the page is loading, the URL is working, and so on. Once they have done the smoke testing, they will hand it over to testers to start the regression testing.
Step 2: Regression Testing
This testing is carried out by testers. Here, they do end-to-end testing for the deployed application. They use different production user data to check the entire application. This testing mostly involves manual testing.
Step 3: Testing Report
In case of any issues, that will be reported to the development team. If the fix is small they will do it on that day or mostly they will push it to the next deployment release and testers will provide a sign-off by mentioning the issue. If there is no issue, testers will provide a sign-off with no issue statements.
Step 4: Maintenance
After the application is released, the maintenance or support team will take care of the application and monitor it 24/7. In case of any issues, that will be reported to the respective team.
Collaborative Load Testing Strategies for Agile Teams
Collaborative load testing or load testing in an agile environment is nothing but it ensures that our application can perform under heavy traffic load. The process of load testing is to test the application’s performance under heavy traffic and ensure the scalability and SLA responses and violations of each service used in the application. This testing is one of the important methods to carry out before each product release. It ensures the stability, scalability, and actual performance of the application.
Table of Content
- What is the Agile Process?
- What is Agile Performance Testing?
- Impact and Benefits of Performance Testing in Agile Environment
- Performance Testing Activities
- Post-production Monitoring
- Conclusion
- FAQs