Test Environment
(Redirected from Testing Environment)
Jump to navigation
Jump to search
A Test Environment is a deployment environment that allow human testers to perform software-system quality assurance tasks (which exercise new and changed code via either automated checks or non-automated techniques).
- …
- Counter-Example(s):
- See: Continuous Integration.
References
2020
- (Wikipedia, 2020) ⇒ https://en.wikipedia.org/wiki/Deployment_environment#Testing Retrieved:2020-5-1.
- The purpose of the test environment is to allow human testers to exercise new and changed code via either automated checks or non-automated techniques. After the developer accepts the new code and configurations through unit testing in the development environment, the items are moved to one or more test environments. Upon test failure, the test environment can remove the faulty code from the test platforms, contact the responsible developer, and provide detailed test and result logs. If all tests pass, the test environment or a continuous integration framework controlling the tests can automatically promote the code to the next deployment environment. Different types of testing suggest different types of test environments, some or all of which may be virtualized to allow rapid, parallel testing to take place. For example, automated user interface tests may occur across several virtual operating systems and displays (real or virtual). Performance tests may require a normalized physical baseline hardware configuration, so that performance test results can be compared over time. Availability or durability testing may depend on failure simulators in virtual hardware and virtual networks. Tests may be serial (one after the other) or parallel (some or all at once) depending on the sophistication of the test environment. A significant goal for agile and other high-productivity software development practices is reducing the time from software design or specification to delivery in production. Highly automated and parallelized test environments are important contributors to rapid software development.