So You Think You Can Write a Test Case
Presented by Srilu Pinjala
In the age of the Internet of Things (IoT), cloud computing, mobile communication, advanced extreme programming, and agile methodologies, we have come a long way. But did we come a long way in every aspect of software development and testing?
Why do we develop software? To practice great coding and to create products that will provide value and be successful.
Why do we test software? To make sure the requirements were met, bugs are found early on, and to passive aggressively give your developers a run for their money.
Software has been developed and tested, now what? Are we done? Is it time to move on to the next best thing or are we just getting started?
About a Test Case, we have been trained for decades that:
- Test cases have to be estimated as soon as a requirement or story has been accepted into a project or a sprint or sooner if possible.
- Test case is there to test a requirement or that the requirement has been satisfied. Hence we need to have ways to trace a test case to a requirement!!
- We have been asked to have sets of – Regression test cases, smoke test cases, functional test cases, end to end test cases, and more types of test cases.
- Taking it further we want to make sure the application is tested completely.
The problem with the 1997 mindset resulted in –
- Most companies have vague test cases or no test cases at all.
- Test cases written by one tester are not understood by other testers (or even humans).
- Test cases written for the requirements are not sufficient to test the end product.
- Higher number of test cases does not increase the quality of the product.
- There is no way to measure the completeness of testing a product.
- Redundant test cases cost more time and money but do not add extra value as per testing.
Let’s undo the damage and understand the real purpose of a test case and why it is one of the most important documents for supporting and testing a product.
About our speaker: Srilu Pinjala has 11 years experience in testing, test management, and automating. She has worked at Expedia, Porch, Amazon, IBM and more places where test cases were non-existent or the existing test cases were abysmal. She believes in exploring the product and fixing the requirements not the other way around. She uses the same approach to write test cases too. She enjoys testing customer facing applications. Connect with her – https://wwww.linkedin.com/in/srilupinjala; More fun stuff at – https://qasrilu.blogspot.com/
This event is fully booked.