QA and Testing

QA and Testing : QA and Testing When do you Test? Staging Environments and Types of Tests Who does the testing? And Why? Describe various types of software tests and explain how and why each is used black and white boxes Quality Assurance

Slide2 : Figure 8.1 The Final Construction Phase

Slide3 : Where does Final Testing Occcur? In the last Staging Environment

Generic Model of Software Testing : Generic Model of Software Testing

Types of Tests : Types of Tests Unit test (fig. 7.6, p. 437-439) System test/Integration (p. 453-459) includes stress test (volume tests) User acceptance test (p. 489, Figs.9.2 and 9.4) (user acceptance review) Regression test

Unit Testing : Unit Testing Testing individual modules of code or methods before integration with other software Driver module used for testing Sets values of input parameters Calls module to be tested and passes input parameters Accepts return parameters from tested module

Integration Testing : Integration Testing Tests the behavior of a group of modules or methods Test both normal processing and exceptions Errors can include: Interface incompatibility Incorrect parameter values Run-time exceptions Unexpected state interactions http://opensourcetesting.org/unit_dotnet.php NUnitASP

System Testing : System Testing Tests the behavior of the entire system Build and smoke test is performed daily to discover any problems with daily builds Performance/stress test checks time-based requirements Acceptance test is performed to determine whether system meets user requirements

Examples : Examples

How does Microsoft Organize for Testing? : How does Microsoft Organize for Testing?

Technical Reviews : Technical Reviews Opens design and construction process to input from other people Other programmers can frequently see errors missed by original programmer Similar to author writing and editor reviewing Walkthroughs and inspections Reduce number of errors by factor of 5 to 10 Reduce testing costs by 50%

Two Approaches to Testing - black box (p. 453) and white box (aka glass box) : Two Approaches to Testing - black box (p. 453) and white box (aka glass box) Black box Data Response White box If Then Else Loop

Two Approaches to Testing black box p. 453) and white box (aka glass box) : Two Approaches to Testing black box p. 453) and white box (aka glass box) Types of Test Black Box White Box Unit/functional Small set of data Look in module Test Systematic end of yr, qtr System Test Small dataset, NA systematic Stress Test High Vol website Database perf review User Accept Production test NA (alpha/beta) vs reqm’ts Regression Repeating test for each change

Test Cases : Test Cases Important part of testing is specifying test cases and data Test cases specify one or more events to which software must respond Starting state Events to which software responds Expected response or ending state Analysis phase documentation is useful in preparing test cases

Slide15 : A Test Specification Form

Test Cases for Delivery 2 : Test Cases for Delivery 2 You may choose to write up the results of your test cases - include unit, system and interface tests Or You may prepare and print a bugzilla report with your bug listing (min 20 bugs) or show you did at least 30 test cases Or be creative – see example

In-Class exercise : In-Class exercise Devise a validity test to see if the numbers you were given are a triangle Description Test Data Results Equilateral Ex 5, 5, 5 Equilateral Scalene Ex 4,3,6 Scalene Isosceles Ex 3,3,4 Isosceles Equilateral Ex 3, 3, 6 Error

Exhaustive set of Unit Test Cases for a Date valid date between 1/1/93 and 12/31/2009 : Exhaustive set of Unit Test Cases for a Date valid date between 1/1/93 and 12/31/2009

Quality Assurance (QA)Requirements >Design Specs > Test Specs : Quality Assurance (QA) Requirements >Design Specs > Test Specs

Accenture Testing Examples : Accenture Testing Examples Application Requirements Window Definitions – Unit test Control-Action-Response Diagrams Assembly Test Conditions - Integration and System Test

Application Requirements : Application Requirements Describes: Business functions to be provided User considerations Quality, others (ex: security, maintainability, scalability, etc.)

Window Definition : Window Definition Should specify: Window function CRUD Modes Field data sources Performance considerations Security considerations Business rules / data validation Error handling

Control-Action-Response : Control-Action-Response Describes how controls should respond to a user’s actions

Component Test Conditions : Component Test Conditions Defines the conditions for testing the detailed behavior within a module Derived from the Module Specification

System Test Conditions : System Test Conditions Defines the conditions for testing the functional requirements

Assembly Test Conditions : Assembly Test Conditions Defines the conditions for testing the interfaces between modules

Data Conversion : Data Conversion

Two Approaches to Reloading Database Content After a Structural Modification : Two Approaches to Reloading Database Content After a Structural Modification

A Complex Data-Conversion Example : A Complex Data-Conversion Example

Slide34 : Common Hardware Tests • Access speed • Processing speed • Server capacity • Peak load http://www.mindcraft.com - benchmarking and price performance measures

Test Overview : Test Overview

Test Overview continued : Test Overview continued

Backup : Backup

Slide38 : Gantt Chart of Test Activities for Purchased Software Project Planning documentation System Pharmacy Prescription System Symbols Scheduled activity Completed activity Analyst Signature Page Date 1 of 1 Activity Build test data files Perform vendor test of hardware Individual Assigned Test software with vendor data Test software with our test data 1. Verify labels 2. Verify log entries 3. Verify end-of-day log 4. Verify summary report Test Procedures 1. Start-up 2. Data entry 3. Label generation 4. Termination 5. Report Generation 6. Backup 7. Error recovery 8. Doctor file maintenance Meet with users and management for approval Fred, Tito Fred, Tito Fred, Tito Fred, Tito Fred, Tito Fred and users ‘’ ‘’ ‘’ and users ‘’ ‘’ ‘’ ‘’ ‘’ ‘’ ‘’ users, mgrs Tracy Bell

Test Your Knowledge - Final Construction Management Grid : Test Your Knowledge - Final Construction Management Grid

Slide40 : Test Your Knowledge Your Knowledge