TestOps
TestOps (or test operations) refers to the discipline of managing the operational aspects of testing within the
TestOps helps teams scale their teams, tests, and quality processes in and effectively.
Elements of test operations (TestOps)
TestOps involves several important disciplines that can be broken down into:
Management —
Control — As teams and tests grow in number and diversity, they naturally increase complexity. Change control processes such as
TestOps Features
DevOps integration — TestOps exists to ensure that the product development pipeline has all the testing frameworks and tools needed. It is common for QA engineers to rely on the pipelines that IT puts together without much input. TestOps changes this by owning test activities related to DevOps, allowing QA engineers and developers to have full ownership and visibility of the development pipeline, so they can tailor it to meet their needs.
Cloud integration — Integrating tests and test runs with cloud providers
Enhanced test planning — Automation is not effective if the entire codebase has to get tested every time a line of code is changed. TestOps provides a centralized platform that makes it easier for testers and developers to plan what tests to write, as well as identify what tests to run and when.
Test lifecycle management — Automated tests follow a lifecycle including creation, evaluation, active, and quarantine or removal. The status of the test should impact how it is treated in build automation systems like CI/CD.
Test
Real-time
TestOps vs. DevOps [11]
DevOps is a broader, more inclusive concept that includes software feature planning, code development, testing, deployment, configuration, monitoring, and feedback. It was an attempt to integrate some of the disconnected toolchains. Testing is included in the broader DevOps methodology.
TestOps[12] is not simply providing additional emphasis on testing. It is focused on operational aspects of testing that are necessary to ensure that testing, whether performed in development, production, or in its own testing phase, is well planned, managed, controlled, and provides insights to enable continuous improvement.
The siloed working mindset is aimed to be removed from activities such as continuous delivery, software testing (manual and automated testing), environment setups, infrastructure and log management, and built-in security enforcement.
References
- ^ https://www.devopsonline.co.uk/devops-and-the-emergence-of-testops/
- ^ "Who Should Test Software?". Istqb Exams at Home Worldwide - Astqb - Istqb in the U.S.
- ^ https://www.professionalqa.com/test-management
- ^ https://www.diva-portal.org/smash/get/diva2:1117878/FULLTEXT02 [bare URL PDF]
- ^ "What is UX Research?".
- ^ "What is Software Testing Life Cycle (STLC)?".
- ^ https://iaonline.theiia.org/change-control-audits-a-must-for-critical-system-functionality
- ISBN 978-3-319-31543-0, retrieved 2022-11-04
- ^ "11 Test Automation Metrics and their Pros & Cons".
- ^ https://www.researchgate.net/profile/Mohamed_Mourad_Lafifi/post/What_test_should_I_do_to_measure_effectiveness_of_an_Automation_Project_that_we_implemented/attachment/59d63c5179197b80779994cb/AS%3A414847972986881%401475918872521/download/Useful+Automated+SOftware+Testing+Metrics.pdf [bare URL PDF]
- ^ "DevOps and the emergence of TestOps!". April 2019.
- ^ "What is TestOps (How Microsoft Does it)". 15 July 2021.