Rekayasa Perangkat Lunak Part-12 Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Outline of this presentation What Testing is Testing In Development Process Types Of Testing and Definitions Verification & Validation Purpose and Goal of Testing Who Tests Software Testing Technique Testing Step Testing Strategy Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

What’s Wrong? T F A=2 ? A=A + 0.1 A=0 Print A Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Testing is to execute a program with the purpose of finding defects What testing is 1) Common definition Testing is to execute a program with the purpose of finding defects testing 2) Wider definition ”Testing is a technical investigation of a product, done to expose quality-related information.” Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Testing in Development Process Testing activities take place in all parts of software development From requirement eliciting to final shipment Testing is part of the development process Testing is part of the company business process Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Testing in Development Process Testing During implementation: test to verify that software behaves as intended by the designer. Testing After implementation: test for conformance with requirements and reliability, and other non functional requirement Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Testing in Development Process Testing activities take place in all parts of software development From requirement eliciting to final shipment Testing is part of the development process Testing is part of the company business process Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Types of testing and definitions Validation and Verification Validate correctness or suitability vertical experts to confirm master results Verification confirm software operates as it is required to double check to ensure results match those previously validated and if not then re-validate them Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Testing can take place as part of each phase of development . Rational Unified Process (RUP) Transition Construction Inception Elaboration Core Workflow Maintenance Testing Development Design Analysis Requirements Testing can take place as part of each phase of development . Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Phase Rational Unified Process (RUP) Transition Construction Inception Elaboration Core Workflow Maintenance Testing Development Design Analysis Requirements Testing can take place as part of each core workflow involved in development organization. Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Verification & Validation Software V & V defined as a systems engineering methodology to ensure that quality is built into the software during development. Software V & V is complementary to and supportive of quality assurance, project management, systems engineering, and development. Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Verification & Validation versus Debugging a process that establish the existence of defects in a system Debugging a process that locates and corrects these defects Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Verification versus Validation Software Verification Process is a process for determining whether the software products of an activity fulfill the requirements or conditions imposed on them in the previous activities. Software Validation Process is a process for determining whether the requirements and the final, as-built system or software product fulfills its specific intended use. Is a whole life-cycle process - V & V must be applied during each phase of the software development process. Verification and validation should establish confidence that the software is fit for purpose This does NOT mean completely free of defects Rather, it must be good enough for its intended use and the type of use will determine the degree of confidence that is needed Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Verification versus Validation “Are we building the system in the right way?” The system should conform to the specification It does what you specified it should do Validation: “Are we building the right system? ” The system should do what the users really requires Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Verification versus Validation Sometimes one of these word is used to mean both verification and validation: Verification in the meaning: verification and validation, or Validation in the meaning: verification and validation Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

The V & V Objectives There are two principal objectives: To discover and rectify defects in a system To assess whether or not the system is usable in an operational situation. Is a whole life-cycle process - V & V must be applied during each phase of the software development process. Verification and validation should establish confidence that the software is fit for purpose This does NOT mean completely free of defects Rather, it must be good enough for its intended use and the type of use will determine the degree of confidence that is needed Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

The V & V Objectives Software V & V determines that the software performs its intended functions correctly. Ensure that the software performs no unintended functions Measure and assess the quality and reliability of software. Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

The V & V Objectives As a software engineering discipline, software V & V also assesses, analyzes, and tests the software on how it interfaces with systems elements Influences the performance, or reacts to stimuli from system elements Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

The V & V process V & V Is a whole life-cycle process V & V should be applied at each stage in the software process. Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Execution base testing Static and Dynamic V&V Are we building the system In the right way? Check correspondence between a program and its specification Static Verification F or mal specifica tion High-le v el design R equir ements Detailed Code/ Program Pr ototype Dynamic Validation Are we building the right system? Execution base testing Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Static and Dynamic V&V Static Verification Concerned with analysis of the static system representation to discover problems Analysis of all documents produced that represent the system Can be applied during all stages of the software process Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

(static verification) observing product behaviour V & V Static Inspect artifacts Dynamic = “testing” Execute systems Statisk kontra dynamisk testning Dynamisk test = mjukvara exekveras i syfte att hitta defekter Statisk test = artefakter granskas i syfte att hitta defekter Statisk och dynamisk testning är komplementära verifieringstekniker. Den ena kan inte ersätta den andra, bägge bör användas för att verifiera överensstämmelse med krav. to discover problems (static verification) observing product behaviour (dynamic validation) Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Complements each other V & V Static Inspect artifacts Dynamic = “testing” Execute systems Statisk kontra dynamisk testning Dynamisk test = mjukvara exekveras i syfte att hitta defekter Statisk test = artefakter granskas i syfte att hitta defekter Statisk och dynamisk testning är komplementära verifieringstekniker. Den ena kan inte ersätta den andra, bägge bör användas för att verifiera överensstämmelse med krav. Complements each other Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

V & V Static Dynamic = ”Testing” Review Inspection Walkthrough Unit test Integration test Acceptance test System test Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Purpose and goal of testing are situation dependent Find defects Maximize bug count Block premature product releases Help managers make ship/no-ship decisions Assess quality Minimize technical support costs Utvärdering av kvaliteten på en produkt - Buggrapporten behöver ej vara lättförståelig, det är inte buggfixning vi är ute efter… [Kaner 2004] Utvärdera att Minimera teknisk supportkostnad – Det är viktigt att fånga de fel som skulle rendera i många supportsamtal oavsett hur allvarliga de är i övrigt [Kaner 2004] Minimera risken för personskador – allt annat är ”out of scope” med denna målsättningen Hitta scenarier som funkar (trots buggar) – typ: ”Vi ska dema systemet i morgon, vad kan vi göra” Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Purpose and goal of testing are situation dependent (cont) Conform to regulations Minimize safety-related lawsuit risk Assess conformance to specification Find safe scenarios for use of the product (find ways to get it to work, in spite of the bugs) Verify correctness of the product Assure quality Utvärdering av kvaliteten på en produkt - Buggrapporten behöver ej vara lättförståelig, det är inte buggfixning vi är ute efter… [Kaner 2004] Utvärdera att Minimera teknisk supportkostnad – Det är viktigt att fånga de fel som skulle rendera i många supportsamtal oavsett hur allvarliga de är i övrigt [Kaner 2004] Minimera risken för personskador – allt annat är ”out of scope” med denna målsättningen Hitta scenarier som funkar (trots buggar) – typ: ”Vi ska dema systemet i morgon, vad kan vi göra” Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Purpose and goal of testing are situation dependent (cont) Testing cannot show the absence of errors, only their presence We test a program to find the existence of an error If we find no errors then we have been unsuccessful If an error is found debugging should occur Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Unsuitable objectives with testing Show that a system does what it is supposed to do Showing that a system is without errors Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

Finished, Questions? Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi