This paper provides a table to describe the different testing strategies that need to be done to make the testing effort successful under different environments.
When we work in a organization, sometimes it will be difficult to plan which types of tests to run, especially in a fast-paced environment. There is every possibility that in the process of testing an application we might miss the critical tests.
This article provides a table below to describe the different testing strategies that need to be done to make the testing effort successful under different environments. Based on my experince working with different environments, it’s always a good practice to cover the below tests at a minimum.
| Test Environment | Type of test | Importance | Possible Detection of critical factors |
| Development | BAT (Build Acceptance test) | High | It is very important to Perform BAT test in Development environment Before moving into Functional test environment. This test need to be done by testers in Dev env after all code complete is done by Development and ready for Deploying into FT Env.
By performing BAT test we can make sure that This build we are going to get is in testable condition. By which we will save lot of time if we can understand the build performance in the Dev env itself. |
| Functional test | Functinal, Compatibility, regression, integration, performance. | High | These tests at a minimum will cover all key aspects of testing. |
| Smoke, Stability, usability | High | As in most organizations, QA environment is replica of production environment, it is important to make sure to perform these tests, which will determine the quick functionality and stability. | |
| Production | DAT (Deployment Acceptance Test) | High | This is a very important test that can be done after deploying the system into production. Real time data will be used to make sure that all the functional pieces after deployment working fine.
This needs to be done before users start using. |
