Fundamentals of Software Quality Assurance & Testing
- 1. FUNDAMENTAL OF SOFTWARE QA & TESTING By Md. Mehedi Zaman Himel Software Quality Assurance Engineer Email: mehedizamanhimel@gmail.com Skype: mehedi_zaman
- 2. Agenda • What is Software Quality Assurance (SQA) • Why SQA is important • SDLC (Software Development Life Cycle) • STLC (Software Testing Life Cycle) • Verification & Validation (V&V) • Seven Principle of Software Testing • SQA Planning involvements
- 3. What is Software QA & Testing • Software Quality Assurance is a process & a set of activities to identify and verify the correctness, completeness, and quality of a Computer Software. • Software Testing is an organized activity to check whether the actual results match the expected results (client-end) and to ensure that the software system is defect free.
- 4. Why Software Testing is Important • Software Testing is needed mostly to ensure a quality product for the customer with least bugs • It is important because software bugs could be expensive or even dangerous • To prevent the loss of time • To check the compatibility of software in different situation in different stage • To keep the business reputation high and strong
- 6. STLC (Software Testing Life Cycle) Requirement Analysis Test Planning Test Case Development Test Environment Setup Test Case Execution Test Cycle Closure
- 7. Verification & Validation • Verification is a process of evaluating the intermediary work products of a software development lifecycle to check if we are in the right track of creating the final product. Basically verification refers to the internal structure of the product (architecture & coding level) • Validation is the process of evaluating the final product to check whether the software meets the business needs. Basically validation refers to the behavior and expected outcome of the product (interface and external level)
- 8. Seven Principle of Software Testing • Testing Shows Presence of Defects: The process of Testing always shows the number of defects in a software or shows that there defects in a software, but cannot ensure that the software is error free. • Exhaustive Testing is impossible: To generate a test, there could be a huge number of combination for test cases, test data, input & output which is exhaustive. So we have to focus on risk and priorities so identify maximum defects. • Early Testing: Testing Activities should be started as early as the requirement is confirmed in Software Development Life Cycle (SDLC).
- 9. SevenPrincipleofSoftwareTesting • Defect Clustering: Identifying the module that contains most of the defects. • Pesticide Paradox: Reviewing the Test Cases regularly so the unwanted repetition of same kind of testing can be stopped with the addition or modification of new Test. • Testing is Context Dependent: Different kinds of apps or websites are tested differently. Like a banking app and a social media app can’t be tested as same way. • Absence-of-error-Fallacy: Testing should not only shows error but also need to fulfill user’s need.
- 10. SQA Planning involves • Analyzing Product: Collect the information about the software (How the software will work, use of the product, about end-user) • Designing Test Strategy: Defining scope of testing, Selecting the types of testing to apply, Record the risks & issues • Creating Test Objectives: Listing the features need to test, Set the goal like expected results. • Defining Testing Criteria: Suspend Criteria & Exit Criteria • Resource Planning: How much resource you are having right now and how you are planning to use it. This resources includes Human resource (SQA, Tester, Manager) & System Resource (Server, Testing Tool, Connectivity, PC)
- 11. SQA Planning involves • Plan Test Environment: Prepare the related Software and Hardware before executing the predefined test cases. (ex: Web server, Database, Connectivity, Web browser) • Scheduling and Estimation: Scheduling and assigning the hours that needed for a testing to be done. It may varies from resource to resource and task to task (Specification creating, Test Execution, Test Report, Deliveries etc.) • Focus on deliverables: Prepare and deliver the documents like Test Plan, Test Cases (Pre-Docs), Test Data, Matrix, Scripts (Live Docs), Test Report, Release note, Manual (Post-Docs).
- 12. Thank You