Delivering an Effective Test Process: The Moment of Truth
In the world of software testing, the moment of truth arrives when you have your test requirements and scripts ready. What follows is the crucial phase of executing tests efficiently to ensure improved software quality. This involves proper preparation, strategic test execution, and keeping the bigger picture in mind throughout the process. By planning testing waves and prioritizing critical tests, you can effectively manage time and resources to deliver high-quality results.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Amadori Courses: Delivering an Effective Test Process Effective Test Execution 1
Amadori Courses: Delivering an Effective Test Process The Moment of Truth has arrived You have your test requirements A set of beautifully crafted test scripts You have mapped your tests against the requirements .. What happens next ? Introduction 2
Amadori Courses: Delivering an Effective Test Process Or Put Another Way .. YOU need to show exactly how all your preparation pays off in terms of improved software quality 3
Amadori Courses: Delivering an Effective Test Process Makes most efficient use of available time and resources by 1. By focussing on the areas which are of most importance 2. By identifying the key issues in the delivery 3. By providing stakeholders with timely and accurate metrics about the quality of the application under test Efficient Test Execution 4
1. Prepare properly 2. Hit the ground running How do we this? 3. Keep sight of the bigger picture at all times Amadori Courses: Delivering an Effective Test Process 5
Time for testing is always at a premium So do whatever you can before code is delivered to facilitate test execution Prepare Properly Amadori Courses: Delivering an Effective Test Process 6
Prepare Properly 1. Decide which tests you will try and execute first 2. Have a Rattle test prepared 3. Confirm that the test environment meets your requirements 4. Confirm that the test data you need will be available Amadori Courses: Delivering an Effective Test Process 7
You should have planned to test in waves of increasing depth Ensure that you know which tests are in the first wave of testing and which ones only get executed if the first wave goes well Run the most critical tests in each area first. If these fail, further testing in this area may have to stop until the issue is fixed Decide which tests you will run first
Dont assume a new build is ready for testing just because developers tell you it is Identify a set of testcases which you run against each and every new build which is delivered into test Have a Rattle Test prepared
What is a Rattle Test? Also termed a Smoke test Both mean more or less the same thing Amadori Courses: Delivering an Effective Test Process 10
Origins Smoke test Smoke forced into closed container to see if there are any cracks in it Rattle test You give an item a good shake and see if you hear rattling inside it Amadori Courses: Delivering an Effective Test Process 11
Should be small The quicker you can complete the test successfully the quicker proper testing can start Should cover only the key elements of the delivery Rule of thumb If ANY part of your Rattle test fails the entire build is deemed not fit for purpose So ONLY include tests which meet this criterion What should be in the Rattle Test? 12
If successful it provides assurance that the more detailed testing is possible If unsuccessful it QUICKLY highlights the fact that the build is not fit for purpose Aim of Rattle Test is NOT to embarrass developers It is to ensure that time is not wasted testing code that will never go-live May also highlight if a delivery schedule is too ambitious . Why is the Rattle Test so important? 13
You should have established what is required during test preparation BEFORE you start testing try to confirm 1. Are all the applications you need installed? 2. Are the right VERSIONS of each application present 3. Do you have what you need in terms of system access to run your tests If you can t do this BEFORE testing starts make sure that your Rattle test will identify issues in these areas Confirm the test environment meets your Requirements
You should have established what is required during test preparation BEFORE you start testing try to confirm 1. How much test data will be present 2. Is it current or historic data? Does this impact your test scripts? 3. Are there specific data items you need for your testing? If so are these items present If you can t do this BEFORE testing starts make sure that your Rattle test will identify major issues in these areas if they exist Confirm you have the test data you need to run your tests
1. If something can be done before code is delivered, do it! Hit the ground running 2. Be clear on what you plan to test, and Why 3. Aim to produce an overview of the new build as soon as your initial tests are complete Amadori Courses: Delivering an Effective Test Process 16
Aim of test execution is NOT to complete all of your tests It is to provide timely and accurate metrics to stakeholders Keep asking yourself What will this test tell me about the quality of the delivery? If there other testing I could be doing which will tell me more? If you get bogged down in one area, raise a blocking issue and move on Keep sight of the bigger picture .
Stakeholders shouldnt care how many tests you run each day They just need to know when the application can go- live Answering this question needs to be THE goal of test execution How you do this will be dealt with in the next session Keep sight of the bigger picture .
