TEST TORG Software. Test Organisation 1 The role

TEST TORG Software. Test Organisation 1 The role of testing in the software life cycle 13 Test Responsibility in a middle sized project 2 Verification and Validation 14 Test Responsibility in a large project 3 Goals of Testing 15 One Level Test Organization 4 Test work distribution 16 Two Level Test Organization 5 Test Responsibilities 17 Three Level Test Organization 6 The Developer as a Tester 18 Four Level Test Organization n im GEOS 7 The End User as a Tester 19 Test Environment 8 The Analyst as a Tester 20 Test Activities 9 The Tester in the Team 21 Testing semantic levels against each other 10 The internal Test Team 22 Test Principles 11 The external Test Factory 23 The Test Equation 12 Test Responsibility in small projects 24 The Test Project

TEST TORG-1 The Role of Testing in the Software Life Cycle Project Request Requ docu Design docu. Module specs. Requ analysis Requ-based Test cases Data-based Test cases System design Module design Coding Code-based Test cases Code Docu. System test Integration test Module test Debugging System Test docu. Integration Test docu Module Test docu.

TEST TORG-2 Verification und Validation Verification = the System is true, i. e. The System was made right Problem Verification Validation = the System fits the purpose The right system was made. Validation Requirements Structural analysis Form Actual Construction = specified Construction Specification Solution Funktional analysis Content Actual performance = required Performance

TEST TORG-3 Goals of Testing 1. Testing is the empirical approach to finding defects in a software system. 2. Testing has two major goals: to find defects before the user does to gain trust in the system 3. The attainment of the first goal can only be measured in terms of the number of defects found relative to the number of defects in the system. 4. The attainment of the second goal can be measured in terms of the test coverage, the higher the test coverage, the greater the trust in the system. 5. These two questions give way to two further questions: how many defects does a system have? what should be covered in a system?

TEST TORG-4 Test Work Distribution Developer Units Unit Test (White Box) Procedures, Modules, Subroutines, Classes Components Developer/Tester Team Integration Test (Grey Box) Packages, Interfaces, Files/Tables Subsystems System User Interfaces System Interfaces, Databases Tester System Test (Black Box)

TEST TORG-5 Test Responsibilities Potential Candidates The Developers themselves The Users The Analysts The Tester in the Team An internal Test Team An external Test Lab

TEST TORG-6 The Developer as a Tester Self Control Developer Controller Shiciophronia Alternative: Pair Programming = Mutual control

TEST TORG-7 The End User as Tester User Department or User Representative Test data Live Data Samples Test Results Development Team

TEST TORG-8 The Analyst as a Tester User Department Analyst Requirement Docu Test Specification Test Data Development Team Test Documentation Test Objects

TEST TORG-9 The Tester in the Team Project Leader Integrated Tester System Architect Tester Developer

TEST TORG-10 The Internal Test Team Project Office Anforderungen Test Team Design Team Developer Team Test Results Developer Team

TEST TORG-11 The external Test Lab Code Components Error Reports Developers develop and test their Components Testers integrate components and test the System

TEST TORG-12 Test Responsibility in a small Project Developer Module Developer as Tester System

TEST TORG-13 Test Responsibility in a middle sized Project Developer Modules Tester In the Team System

TEST TORG-14 Test Responsibility in a large Project Development Team Components Test Team System

TEST TORG-15 One Level Test Organization Developers and Testers are together in one Team The developers code and the testers test.

TEST TORG-16 Two Level Test Organization Analyst s and Users Test Requirement Specs Developers System Components Technical Test Cases Error Reports Unit Test & Integration Test

TEST TORG-17 Three Level Test Organization Analysts Requirement Specs Logical Test Cases Developers Components Testers Error Reports Unit Test & Integration Test Technical Test Cases Error Reports Integration Test & System Test Docus

TEST TORG-18 Four Level Test Organization Requirements 1 n n 1 Analysts System Design n stated implemented by n implied derived 1 n n Tests 1 tested by 1 Developers tested_by 1 Designers implements 1 Code Components Tests 1 n n System Test Cases Testers 4 -Layer GEOS Project Organization

TEST TORG-19 Test Environment Acceptance Test Process Test strategy Test methods System test Integration test Unit test Test Procedures Test Levels Test Tools Batch Online Distributed Test Environments Internet

TEST TORG-20 Test Activities Test planning Test execution Test evaluation Test documentation Test Planning Test Evaluation Test Execution Test Documentation Interconnection between test activities

TORG-21 TEST Testing semantic Software Levels against each other Integration Test R: Requirements Unit Test D: Design R/D Soll D/C C: Code Soll Ist Ist R/R D/D C/C R/C System Test In the Unit Test the Code (C) is compared with the Design (D). In the Integration Test the Design (D) is compared with the Requirements. In the System Test the Code (C) is checked against the Requirements (R).

TEST TORG-22 Test Principles Principle of Decomposition: The whole is tested by testing all the parts and all relationships between the parts. Principle of Repetition: Every test must be repeatable. Principle of Measurability: Software behavior must be measurable on a numeric scale Principle of Infinity: An infinite test is not a valid test. Principle of Functional completeness: Every Function in a System has a purpose and must be tested against that purpose. Principle of Redundancy: A redundant test case adds no value to the test Principle of Test Environment: The environment of a system ist part of the system test.

TEST TORG-23 The Test Equation = Test Strategy + Test Method + Test Tools + Test Organisation + Test Audit Without a Strategy a test is not oriented. Without a Method the test is not effective. Without a Tool the test is not efficient. Without an organization the test is not controllable. Without an audit the test is not reliable.

TEST TORG-24 The Testprojekt Requirements analysis Business Modelling Requirement Specification Test Design Test Specification Development Project Parallel Projects Test Project Test Preparation Test Execution Test Evaluation Software