Software QA/Testing SW

Software QA/Testing Test Organization Structure Software QA Test Plans Test Cases

Test Organization Structure

Software QA

Test Plans

Test Cases

The Testing Process Function testing Module testing Subprogram testing Program testing Acceptance testing

Small Team QA TL/QA Lead Test Engineer Developer Developer PM Small teams: -QA/Test part of the development team -QA tend to switch to developper

Medium Size Organization QA Developer Developer PM Development TL Test Engineer Test Engineer QA Lead

Large Organization QA QA Manager Test Engineer Test Engineer PM PM Development Manager

The Software QA Process Unit testing Developer Subroutine, module, class, informally Source-code testing Technical reviews Program testing Developer Development team Test/QA team Line by line in a debugger Walk through inspection, code reading Test plan/Test cases Integration testing Developer of the new code Process type Responsible Description Test of the module after the insertion of the new code

Defect Tracking Defect ID - unique ID Description - brief description of the defect Platform type - CPU,memory, disk space, vide card, etc. Defect’s current status - open/closed Developer/QA who detected the defect Date Severity - 1-4 Phase creation/detection - RD, architecture, design, etc. Date correction Person who corrected it Effort - in staff hours required to correct it Work product - product corrected, RD, FSD, DD, TP/TC Resolution - pending engineer fix, pending engineer review, pending QA verification, corrected, determined not to be a defect, unable to reproduce Other notes

Defect ID - unique ID

Description - brief description of the defect

Platform type - CPU,memory, disk space, vide card, etc.

Defect’s current status - open/closed

Developer/QA who detected the defect

Date

Severity - 1-4

Phase creation/detection - RD, architecture, design, etc.

Date correction

Person who corrected it

Effort - in staff hours required to correct it

Work product - product corrected, RD, FSD, DD, TP/TC

Resolution - pending engineer fix, pending engineer review, pending QA verification, corrected, determined not to be a defect, unable to reproduce

Other notes

Software QA Practices Begin review early in the software project Keep technical reviews focused on defect detection Keep technical reviews technical Keep track of what material has been reviewed Record the defects detected during reviews Verify that the works identified during the review is performed Make review results public to the project team Allow time in the schedule for reviews and correcting problems identified during reviews

Begin review early in the software project

Keep technical reviews focused on defect detection

Keep technical reviews technical

Keep track of what material has been reviewed

Record the defects detected during reviews

Verify that the works identified during the review is performed

Make review results public to the project team

Allow time in the schedule for reviews and correcting problems identified during reviews

Build engineering Large software organizations, multiple products Build schedule Release management Build Build testing Delivery

Large software organizations, multiple products

Build schedule

Release management

Build

Build testing

Delivery

Test Plan Template Overview - architecture of the program under test, test approach, goals, methodologies, arguments Definition - table: terms and acronyms related to the testing plan Bounds Scope- what will be tested and what not Setting- location where the test will be performed Quality risks Component testing - states, transactions, data flow, functionality, UI Integration testing - APIs, error handling, functionality, UI, performance System and acceptance testing - states, transactions, data flow coverage, functionality, UI, error handling, operations, reliability, date/time, localization, installation and configuration options, compatibility, documentation Proposed schedule/milestones - milestones from the Gantt chart (high level deliverables) Test Development and Configuration - Test plan complete, Test lab configured, Test suite complete Testing - Phases - Test cycles

Overview - architecture of the program under test, test approach, goals, methodologies, arguments

Definition - table: terms and acronyms related to the testing plan

Bounds

Scope- what will be tested and what not

Setting- location where the test will be performed

Quality risks

Component testing - states, transactions, data flow, functionality, UI

Integration testing - APIs, error handling, functionality, UI, performance

System and acceptance testing - states, transactions, data flow coverage, functionality, UI, error handling, operations, reliability, date/time, localization, installation and configuration options, compatibility, documentation

Proposed schedule/milestones - milestones from the Gantt chart (high level deliverables)

Test Development and Configuration - Test plan complete, Test lab configured, Test suite complete

Testing - Phases - Test cycles

Test Plan Template (cont) Tracking test tracking - list to manage the test cases, and the way the process is documented Test suites table- sequence of test case for all the test suites defect tracking - tool/database, classification and the way communication occurs (dev team, QA, mgmt) Phases (1,2,3,4,5…) - for each phase, the criteria essential for beginning/completing various test phases Release management - how a software component should be identified release (revision) number- compatibility, os version, tested/not testes, test phase/cycle Risks and contingencies training needs availability of additional development support Change history - changes and revisions made to the test plan Referenced documents

Tracking

test tracking - list to manage the test cases, and the way the process is documented

Test suites table- sequence of test case for all the test suites

defect tracking - tool/database, classification and the way communication occurs (dev team, QA, mgmt)

Phases (1,2,3,4,5…) - for each phase, the criteria essential for beginning/completing various test phases

Release management - how a software component should be identified

release (revision) number- compatibility, os version, tested/not testes, test phase/cycle

Risks and contingencies

training needs

availability of additional development support

Change history - changes and revisions made to the test plan

Referenced documents

Test Plan Phase Template Entry criteria documentation, specifications and requirements available? subprogram/program ready (runnable)? supporting utilities, accessories, prerequisites? previous test phase completed? lab, hardware, software, support ready? Stopping criteria - conditions/events to suspend test execution a entry condition could become unavailable too many errors in the program Exit criteria - when testing has been completed all planned tests cases and regression tests have run team/SwPM OK Resources - People, Hardware allocation, Software, Networks, Lab space, other resources Test Cycles - all test suites planned for a given phase

Entry criteria

documentation, specifications and requirements available?

subprogram/program ready (runnable)?

supporting utilities, accessories, prerequisites?

previous test phase completed?

lab, hardware, software, support ready?

Stopping criteria - conditions/events to suspend test execution

a entry condition could become unavailable

too many errors in the program

Exit criteria - when testing has been completed

all planned tests cases and regression tests have run

team/SwPM OK

Resources - People, Hardware allocation, Software, Networks, Lab space, other resources

Test Cycles - all test suites planned for a given phase

Test Cases Use Case Test - against a/several given usage/s System & Acceptance Test - program as a whole, real data Functional Test - functionality (module, program) Structural Test - driven by the structure of the program Boundary Test - test the boundary conditions Requirements-based Test - test against the original requirements Behavioral Test - a set of possible user actions Fault-based Test - error input response Regression Test - re-testing

Use Case Test - against a/several given usage/s

System & Acceptance Test - program as a whole, real data

Functional Test - functionality (module, program)

Structural Test - driven by the structure of the program

Boundary Test - test the boundary conditions

Requirements-based Test - test against the original requirements

Behavioral Test - a set of possible user actions

Fault-based Test - error input response

Regression Test - re-testing

Distributed Testing A B A B A B B A A and B test different conditions A and B test the same conditions A and B test some similar conditions and some independent A test conditions cover B tests conditions

Outside Beta Testing Expert consulting Reviews Customer relationship building Polishing the User Interface Compatibility testing General QA - as many testers as possible

Expert consulting

Reviews

Customer relationship building

Polishing the User Interface

Compatibility testing

General QA - as many testers as possible

EN ISO 9000 Family - EC type CE Marking A Production Phase B C D E No notified body to take action - one or more tests on one or more specific aspects - random product checks Conformity with the type as described in EC - one or more tests on one or more specific aspects - random product checks H G Design Phase NB examination for every individual product (certificate of conformity) F NB intervention, approve and control QS. ISO9002 (production, final product inspection and testing) -production QA without Design NB intervention, approve and control QS. ISO9003 (final product inspection and testing) -production QA without Design NB controls conformity with the type - EC (certificate of conformity) -production QA without Design EC-type examination (certificate of conformity) NB intervention, approves and control QS. ISO 9001 (design, production, final product inspection,testing) -QA without Design