De presentatie wordt gedownload. Even geduld aub

De presentatie wordt gedownload. Even geduld aub

Gastcollege 21-03-2012 Testing in practice Bart Knaack Logica

Verwante presentaties


Presentatie over: "Gastcollege 21-03-2012 Testing in practice Bart Knaack Logica"— Transcript van de presentatie:

1 Gastcollege Testing in practice Bart Knaack Logica

2 © Logica All rights reserved Who am I? Bart Knaack, Senior Test Advisor, Logica, The Netherlands 15 years experience in IT, of which 12 in testing. Developer, Development Lead, Tester, Testautomator, Testcoordinator, Testmanager, Testadvisor. Trainer in Testmanagement

3 © Logica All rights reserved Paper clippings No. 3

4 © Logica All rights reserved Testpyramide Testgrip TestFrame RRBT

5 © Logica All rights reserved The goal of testing is to find errors Footer appears here

6 © Logica All rights reserved Testing is trying to build convidence in system, by trying to diminish that confidence (and hopefully not succeeding) D. Graham Footer appears here

7 © Logica All rights reserved Why testing? Prevent defects during operation of the system. Verify intended functionality Validation vs Verification €€€ €€€ €€€ €€€ DefinitionDesignDevelopmentProduction

8 No. 8© Logica All rights reserved Test levels in the V-model Acceptance Test Component Integration Test Component Test System Integration Test System Test User needs, Requirements, Business processes System Specification Technical Design & Code S t a t i c T e s t i n g D y n a m i c T e s t i n g Test specification Test execution Black box White box terms according to:

9 © Logica All rights reserved Glass-box testing Also called ‘white-box’ or ‘structural’ testing Testers have access to the system design – They can Examine the design documents View the code Observe at run time the steps taken by algorithms and their internal data – Individual programmers often informally employ glass-box testing to verify their own code

10 © Logica All rights reserved Black-box testing Testers provide the system with inputs and observe the outputs – They can see none of: The source code The internal data Any of the design documentation describing the system’s internals

11 © Logica All rights reserved Test Techniques Boundary Value Analysis Equivalence partitioning Branch Coverage testing

12 © Logica All rights reserved Equivalence Partitioning Requirements divide data in ranges of equivalent behavior. All people between 25 and 65 have to pay premium for their retirement. All people older than 65 get a pension. All people earning less then €5000 do not have to pay premium. These classes need to be tested

13 © Logica All rights reserved Equivalence Partitioning Requirements divide data in ranges of equivalent behavior. All people between 25 and 65 have to pay premium for their retirement. All people older than 65 get a pension. All people earning less then €5000 do not have to pay premium. These classes need to be tested

14 © Logica All rights reserved Boundary Value Analysis Requirements contain values All people between 25 and 65 have to pay premium for their retirement. All people older than 65 get a pension. All people earning less then €5000 do not have to pay premium. These values form the basis for setting up testcases

15 © Logica All rights reserved Boundary Value Analysis Requirements contain values All people between 25 and 65 have to pay premium for their retirement. All people older than 65 get a pension. All people earning less then €5000 do not have to pay premium. These values form the basis for setting up testcases

16 © Logica All rights reserved You are done testing when all possible tests have been executed Footer appears here

17 © Logica All rights reserved No Risk, No Test Footer appears here

18 No. 18© Logica All rights reserved RRBT: risks versus requirements Product RisksRequirements Matching risks with requirements Matching requirements with risks Risk, no requirement: Add requirement (earlier error detection) Delete risk (No useless testing) Requirement, no risico: Adapt Risico lijst (better coverage) Delete Requirements (no useless development, no “frails”)

19 No. 19© Logica All rights reserved Combine productrisks en requirements Analyse requirements Analyse risico’s Assess Impact risks Prioritze requirements Define testcases Must test Should test Could test Won’t test Must have Should have Could have Won’t have

20 No. 20© Logica All rights reserved 20 Kwaliteitsattributen ISO9126 FunctionaliteitPortabiliteitOnderhoudbaarheidBruikbaarheidBetrouwbaarheid Geschiktheid Nauwkeurigheid Connectiviteit Veiligheid Functionaliteits naleving Volwassenheid Fout tolerantie Herstelbaarheid Betrouwbaarheids naleving Begrijpelijkheid Leerbaarheid Opereerbaarheid Aantrekkelijkheid Bruikbaarheids naleving Tijdsbeslag Middelenbeslag Efficiency naleving Analyseerbaarheid Wijzigbaarheid Stabiliteit Testbaarheid Onderhoudbaarheids naleving Aanpasbaarheid Installerbaarheid Inschikkelijkheid Uitwisselbaarheid Portabiliteits naleving Kwaliteitsattributen ISO 9126 FunctionaliteitPortabiliteitOnderhoudbaarheid Efficiëntie BruikbaarheidBetrouwbaarheid Geschiktheid Nauwkeurigheid Connectiviteit Veiligheid Functionaliteits naleving Volwassenheid Fout tolerantie Herstelbaarheid Betrouwbaarheids naleving Begrijpelijkheid Leerbaarheid Opereerbaarheid Aantrekkelijkheid Bruikbaarheids naleving Tijdsbeslag Middelenbeslag Efficiëntie naleving Analyseerbaarheid Wijzigbaarheid Stabiliteit Testbaarheid Onderhoudbaarheids naleving Aanpasbaarheid Installerbaarheid Inschikkelijkheid Uitwisselbaarheid Portabiliteits naleving Kwaliteitsattributen ISO9126

21 © Logica All rights reserved Functional testing Usability testing Performance testing Stress testing Penetration testing Types of testing Footer appears here

22 © Logica All rights reserved Visibility of system status Match between system and the real world User control and freedom Consistency and standards Error prevention Recognition rather than recall Flexibility and efficiency of use Aesthetic and minimalist design. Help users recognize, diagnose, and recover from errors Help and documentation Heuristic evaluation (Nielson) Footer appears here

23 © Logica All rights reserved Most of the time spend in testing is wasted effort. Footer appears here

24 © Logica All rights reserved Quality is always under pressure Planning and Specification DevelopmentTesting

25 © Logica All rights reserved Tasks of a tester Requirements Analysis Risk Analysis Testcase Preparation Stakeholder Involvement Test Execution Bug Reporting Bugfix meetings Retesting Reporting


Download ppt "Gastcollege 21-03-2012 Testing in practice Bart Knaack Logica"

Verwante presentaties


Ads door Google