SQA Software Quality Assurance SQA Lecture 9 Test

SQA Software Quality Assurance

SQA Lecture: 9 Test Plan & Test Case www. company. com

SQA TEST PLANNING STLC can be roughly divided into 3 parts: • Test planning • Test Design • Test Execution Test Plan is a dynamic document. The success of a testing project depends on a well written test plan document that is current at all times. Test Plan is more or less like a blue print of how the testing activity is going to take place in a project. www. company. com

SQA TEST PLANNING It should have the clear information on the following steps: • • • www. company. com Scope Out of scope Assumptions Scheduled Roles & Responsibilities Deliverables Environment Tools Defect Management Risk & Risk Management Exit criteria

SQA TEST PLANNING & TEST MANAGER VS 2010 Here a few important pointers regarding a test plan: • Test Plan is a document that is the point of reference • It is also a document we share with the Business Analysts, Project Managers, Dev team and the other teams. This is to enhance the level of transparency into the QA team’s working to the external teams. • It is documented by the QA manager/QA lead • Test Planning is typically allocated 1/3 rd of the time it takes for the entire QA engagement. The other 1/3 rd is for Test Designing and rest is for Test Execution. • Test plan is not static and is updated on an on demand basis. www. company. com

SQA For us testers, test cases are the real deal – the stuff that we spend most of our times around. We create them, review them, execute them, maintain them, automate them- well, you get the picture. No matter how experienced we are and what role we play in a project – we would still work with test cases. www. company. com

SQA TEST CASE – WHAT AND HOW? “Documentation specifying inputs, predicted results, and a set of execution conditions for a test item. ” The aim is to divide the software function into small units of function that is testable with input, and producing result that is measurable. So, basically a test case is a feature/function description that should be executed with a range of input, given certain preconditions, and the outcome measured against expected result. By the way, there is a common misconception relating to test cases and test scripts, or even test suite. Many people use them interchangeably, and that is a mistake. In short, a test suite is a compilation of multiple test cases. www. company. com

SQA APPROACH TO TEST CASE WRITING • Function: Test each function/ feature in isolation • Domain : Test by partitioning different sets of values • Specification based: Test against published specifications • Risk based: Imagine a way in which a program could fail and then design tests to check whether the program will actually fail. • User: Tests done by users. • Scenario/ use case based: Based on actors/ users and a set of actions they are likely to perform in real life. • Exploratory: the tester actively controls the design of tests as those tests are performed and uses information gained while testing to design new and better tests. www. company. com

SQA TEST CASE WRITING PROCEDURE • • • Study the application Standardize an approach for test case writing Identify sets of test cases - Main vs. Sub Decide on a structure - Format Test case name • Description • Prerequisites • Steps • Input • Expected result • Actual result • Status • Comments www. company. com

SQA Test Reports www. company. com