What is Operational Readiness Test and how to perform ORT testing?
Operational Readiness Test is one of the software testing strategy. Operational Readiness Test is performed at final stage of testing when all other testing activities are performed and build is ready for live deployment.
In Operational Readiness Test we basically test for –
Database backup – Database backup is necessary when any disaster happens or any data gets corrupted. Generally every web application have one database which stores the data in database. It could be any kind of data like customer profile, price of product, images, articles, number of products, login and password information etc. Database backup should be scheduled on every specified time and this task should perform on regular basis. On Operational Readiness Test perspective, you should test and validate that database have been backed up successfully without loss of data. Testing can be performed with help of developers or tools implemented to take the database backup on specified time for the application developed.
Database Recovery – Database recovery testing should be performed whenever it might chances to loss of data. Loss of data can be happen at any point of time and reason could be anything network failure, website down, Operating System or any disaster. If any issues happens with database you should be able to recover the lost data and able to restore it. Recovery and restoration could be perform either manually or automatically depends on what mechanism is applied for the application developed.
Software Installation and Configuration– Software Installation and Configuration test is performed to check the software developed is getting installed successfully to the system. Each steps of installation instruction should be described and there should not be any difficulty or issue to install the software. Also Installation and configuration test should perform to secure that the deployment package, scripts and configurations work according to installation instructions. Deployed components to ORT shall be packaged and distributed to the available environment. Verification of installation, configuration and of major functionality should be done by execution of (preferably automated) Smoke Tests.
Rollback – Rollback test should be performed once any new deployment is done and after deployment application is not working as expected. You should be in condition to rollback the application to last known working configuration in case problems occurs during the deployment. If any new deployment planned, make sure the previous working build is available if situation comes to roll back the application to the previous working version.
Failover – Failover testing verifies that application proceeds as normal when a redundant component fails. To execute a failover test you need to have defined failover scenarios. If a failure occurs in one component, you should have reason or cause that what causes failure? Failover test could be perform for network failover, component failover, server failover etc. For example – If you place any order online, your order should be placed successfully even any backend component gets failed. A server could have many instances running by which request reaches to the server, so if any instance get failed then other instances should be capable to handle the request.
Supportability – In Supportability testing we perform following testing – Installation test, Rollback test and Monitoring. Installation test and Rollback have been explained above. In monitoring we check – Handling of events generated when system is malfunctioning. We perform verification of monitoring mechanisms for the system. How is Availability, performance and capacity being measured and reported.
Reliability – In Reliability test we perform Failover test and Recovery routines which are explained above. Also we check that Recovery Routines work within the conditions specified.
Performance – Generally performance testing performed separately but in Operational Readiness Test you should verify the application behavior under load. Start performing load test with specified number of users and check the application behavior manually. In other words we can say perform sanity checks of the application under load.
Regression – In regression testing you should perform testing of the other application functionalities which are not part of new implementation. You should check the functionality of other modules are working as expected and the new change has no effect on existing features. Generally Regression Tests executed to secure and verify that integration to external systems work and there is no effect on most critical business functionality.
Maintainability – Performing maintainability testing we test installation routines and rollback for updates/patches for database, infrastructure and application. Maintaining the application should be easy.
Security – Following test approaches should be performed during security testing – Security Information and Event Management, Penetration Testing, Intrusion Detection and Prevention, Access control, source code review, data protection etc.
For more detail on Security testing Clikc Here.