Phased Testing: Testing Systems Undergoing Change - Baubak Gandomi at PNSQC 2022
This paper deals with the challenge of verifying and testing the success of system changes. This is often overlooked when testing, however as systems are moving more and more to continuous delivery, such tests become increasingly relevant. Some the more common system changes are:
- Database changes
- Application Upgrades
- Server and Cloud changes
Our experience is that validating that a system works after a system change is quite hard. We see the following challenges:
- How do distinguish between problems related to the change, and those inherent in the product?
- How can a problem be clearly identified and reproduced?
We think that traditional test approaches have limitations when testing for change. Instead, we present a new approach to writing tests that allows us to test how a use case is affected by a system change. We call this approach Phased Testing. Phased Testing, allows our test scenarios to be leveraged for validating system changes. This is done by empowering our scenarios in two ways:
1. By allowing test scenarios to be interruptive.
2. A test scenario is declared only once, but we are able to execute it with all the possible interruptions it may be subjected to.
Baubak Gandomi, Test Automation Architect - With more than 20 years of experience in the software industry, I am specialized in the management of software quality and life-cycle. I enjoy getting projects with no Continuous Integration / Deploy up and running.
I have a passion for the un-testable, so if you want to discuss projects I would be glad to discuss such problems with you. I have studied in Sweden and in Germany, and graduated from the university of Stockholm. I have mainly worked in Sweden and in France. and have been at Adobe for the last 8 years as a test automation architect.
Видео Phased Testing: Testing Systems Undergoing Change - Baubak Gandomi at PNSQC 2022 канала PNSQC
- Database changes
- Application Upgrades
- Server and Cloud changes
Our experience is that validating that a system works after a system change is quite hard. We see the following challenges:
- How do distinguish between problems related to the change, and those inherent in the product?
- How can a problem be clearly identified and reproduced?
We think that traditional test approaches have limitations when testing for change. Instead, we present a new approach to writing tests that allows us to test how a use case is affected by a system change. We call this approach Phased Testing. Phased Testing, allows our test scenarios to be leveraged for validating system changes. This is done by empowering our scenarios in two ways:
1. By allowing test scenarios to be interruptive.
2. A test scenario is declared only once, but we are able to execute it with all the possible interruptions it may be subjected to.
Baubak Gandomi, Test Automation Architect - With more than 20 years of experience in the software industry, I am specialized in the management of software quality and life-cycle. I enjoy getting projects with no Continuous Integration / Deploy up and running.
I have a passion for the un-testable, so if you want to discuss projects I would be glad to discuss such problems with you. I have studied in Sweden and in Germany, and graduated from the university of Stockholm. I have mainly worked in Sweden and in France. and have been at Adobe for the last 8 years as a test automation architect.
Видео Phased Testing: Testing Systems Undergoing Change - Baubak Gandomi at PNSQC 2022 канала PNSQC
Показать
Комментарии отсутствуют
Информация о видео
Другие видео канала
Agile Team Size - It Makes Huge Difference w/Michael MahPNSQC2015 - Ken Pugh05 End to End Quality with the Sonar Ecosystem and the Water Leak Metaphor G Ann Campbell, SonarSouWeb Application Attack Surface - Measurement and ImplementationSoft Skills a Tester Should Have - Mesut DurukalINVITED SPEAKER How Testing Strategy can Increase Developer Efficiency and Effectiveness Brian OkkenAgile Risk Management in the Large Enterprise | 2019 Webinar SeriesInformation Security -- Practices and Trends in Agile Enterprises - PNSQC WebinarKEYNOTE Who Owns Quality in Agile - Katy Sherman, Premier, IncPNSQC 2013 - Douglas HoffmanPNSQC President Brian Gaudreau - Call for Software Quality ProposalsPNSQC2016 Submit Your Abstract and Be Part of Software Quality HistoryKEYNOTE Cultivating a Champion Mindset to Dramatically Improve Your Life, Darlene Bennett GreeneTest Architectures and Support Environments for IoT - Jon Hagar, Grand Software TestingPNSQC2021: Ritu Walia - QA Best Practices - GUI Test Automation For EDA SoftwareLightning Talk - Q & A10 Embedding Security in Product Lifecycle Arvind Srinivasa Babu, McAfee LLC & Deepti Chauhan, McAfe06 - From 3 to 1 Easier Said Than Done with Shiva Srinivasan02 Influencing Change Levi Siebens, Vertafore04 Building a Customer Quality Dashboard – A Case Study John Ruberto, First DataSecurity Metrics with Caroline Wong