Principles of Software Testing for Testers Module 8:

Principles of Software Testing for Testers Module 8:

Principles of Software Testing for Testers Module 8: The RUP Workflow As Context Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 1 Objectives Identify the remaining workflow details of the RUP Test Discipline. Identify some additional key practices for successful software testing. Understand the testing workflow in the context of an Iteration

Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 2 Review: Where Weve Been Quick Review of RUP Workflow Details So far, we have covered: Define Evaluation Mission Test and Evaluate Achieve Acceptable Mission

Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 3 Verify Test Approach Other Workflow Details Verify Test Approach Validate Build Stability Improve Test Assets Review Test Workflow Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 4

Verify Test Approach - Content Outline Overall focus is on the workflow detail: Verify Test Approach Definition of the workflow detail Brief overview of activities and artifacts typical of the work Checking whether your approach is workable Considerations for testability Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 5 Verify Test Approach Activities and Artifacts

This section focuses on proving that the approach you plan to use is workable. We will spend time looking at activities that support the concept of Testability. Note that it is a good practice to implement tests as concrete proof that the approach will work. Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved

6 Verify Test Approach - Purpose Will the approach work and produce accurate results? Will it fit the project constraints? Do the techniques give us adequate coverage? What risks remain? Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 7

Discussion Exercise 8.1: Testing Project Risks What are the most common risks in testing projects? What do you do about them? Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 8 Checking Whether Your Approach is Workable Risk analysis is a fundamental activity in RUP Analyze the risks in your plan for testing Ask how workable your test approach will be There are an infinite number of tests for your program What tests are you implicitly choosing not to run and

what issues will you miss? How much time can you spend not immediately finding defects? Project management, training, documentation, If you skimp on those other tasks How much can you learn and improve? How can complex tasks succeed? Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 9 Improving Testability Testability involves Visibility the tester can see (and understand) what is going on

Control the tester can force something to happen. Systems dont magically become testable. Testability is designed in (or not). Testability features are built into a program, and should be discussed when product requirements are discussed. Its up to you to ask for them. Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 10 Improving Testability: Examples Visibility

Component-based architecture Instrumentation for tracing and profiling Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 11 Exercise 8.2: Improving Testability 1. Pick a product 2. Form project teams a. Each team takes a different part of a product b. Be specific about the part of a product 3. List 10 useful testability features a. 5 for visibility

b. 5 for control 4. For each, answer: a. b. c. d. Is it available today? If so, do you use it? When would you have to request this to get it? What would it take (work / cost) to get it? Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved

12 Validate Build Stability Other Workflow Details Verify Test Approach Validate Build Stability Improve Test Assets Review Test Workflow Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 13 Validate Build Stability - Content Outline Overall focus is on the workflow detail:

Validate Build Stability Definition of the workflow detail Brief overview of activities and artifacts typical of the work Why build verification testing is so important The scope of build verification tests Automation Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 14 Validate Build Stability Activities and Artifacts This section focuses on Build Verification

Tests (BVTs) We will discuss some key issues associated with BVTs including deciding on appropriate Test Suites. A BVT is specialized Test and Evaluate work, so you will notice many common elements. Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved

15 Why Build Verification Tests are So Important (1/2) Frequent builds are a valuable risk management activity Errors detected early Errors traceable quickly to a small number of changes Design changes reviewed quickly As the project nears completion, more people depend on details of the user interface and functionality of the program. They need to know about changes (and to review them) as soon as possible. Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved

16 Why Build Verification Tests are So Important (2/2) Bad builds can waste an enormous amount of testing time Build verification is part of the configuration management process. It prevents versions Delivered with wrong components With key test-blocking errors, or without critical (agreed) fixes to errors, or without key features That are less efficiently testable than planned Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved

17 Organizational Considerations Who should run the BVT? Programmers? Testers? Configuration mgmt technicians? Release engineering team? Who should create and maintain the BVT? Group independence matters less for BVT Structure the BVT so that any authorized person can run it, from any group Allow different groups to add cases to the BVT, but leave pruning to the test group Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved

18 Automation of BVTs and Build Process Most of the BVTs should be automated Rapid ROI: you run the tests every build anyway BVTs allow an automated build-verify-deploy sequence Maintain / refactor BVTs to prevent false negatives Mixed BVTs often desirable Primarily automated, extended with Manual testing for short term issues Build-critical bugs are fixed Specific work items delivered

Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 19 Discussion Exercise 8.3: Build Verification Tests Describe your build process Describe your build verification testing How successful or unsuccessful is your BVT? What would you change? Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved

20 Improve Test Assets Other Workflow Details Verify Test Approach Validate Build Stability Improve Test Assets Review Test Workflow Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 21 Improve Test Assets - Content Outline Overall focus is on the workflow detail:

Improve Test Assets Definition of the workflow detail Brief note of activities and artifacts typical of the work Considerations for Improving Test Assets Maintenance Costs Artifacts you might consider improving Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 22 Improve Test Assets Activities and Artifacts This section focuses on making

sure regular improvements are made to the test effort. We will discuss some of the key concerns in making ongoing improvements to test assets and activities. Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 23

Considerations for Improving Test Assets Point of this workflow detail is simple and direct. You make a large investment in test ideas, test cases and scripts (whether manual or automated), test documentation, tester training materials, and so on. These are your long term assets. It is important to protect and increase their value. Every iteration in every project involves change. Changes may make parts of some assets outdated. Change is inevitable, so plan a maintenance strategy. If you cannot maintain your assets efficiently, you risk losing their value over time. Principles of Software Testing for Testers

Copyright 2002 Rational Software, all rights reserved 24 Discussion Exercise 8.4: Cost Considerations What Assets need to be maintained? Test Scripts? Test Suites? Test Cases? Test-Ideas Lists? Change Requests? Test-Idea Catalogs? Automation Frameworks? Others? Can you afford to maintain them all?

Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 25 Module 8 - Content Outline (Agenda) Other Workflow Details Verify Test Approach Validate Build Stability Improve Test Assets Review Test Workflow Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved

28 Review: Iterations Inception Elaboration Construction Preliminary Architect. Architect. Devel. Iteration Iteration Iteration Iteration Devel. Iteration

Transition Devel. Transition Transition Iteration Iteration Iteration Each iteration results in an executable release (internal or external). Iterations are the heartbeat or rhythm of the project and a governing principle for testing in RUP. Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 29 The Test Workflow Occurs in Each Iteration

This diagram represents testing work within an Iteration. All workflow details can be performed in a single Iteration. There are usually several Test Cycles within the Iteration. Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 30 Each Build Is a Candidate for a Cycle of Testing

Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 31 Module 8 - Review What does it mean to Verify the Test Approach? Name one key aspect that needs to be considered? Why are Build Verification Tests Important? When should you consider improving your test assets?

Principles of Software Testing for Testers Copyright 2002 Rational Software, all rights reserved 32

Recently Viewed Presentations

  • Tags - California Public Utilities Commission

    Tags - California Public Utilities Commission

    Sub Group will confirm/modify by consensus. V1G. Charging. V2G (Would also include V2H and V2B) Discharging. Aggregated. Where an Entity manages more than one load. OVGIP, DCH, EVSE Service Provider. Non-Aggregated. Individual Loads. Unified. Where each of the elements or...
  • Jeopardy prompt and response template - Edl

    Jeopardy prompt and response template - Edl

    Review Jeopardy Eng 4 Cognate terms Antonym 100 Points Antonym 100 Points unrelated Antonym 200 Points A risible situation poignant Antonym 200 Points Antonym 300 Points An evening full of folderol Antonym 300 Points significance In a bilious frame of...
  • CBT for Somatic Symptom and Related Disorders

    CBT for Somatic Symptom and Related Disorders

    Somatic Symptom Disorder. One or more distressing or disruptive somatic symptom. Excessive thoughts, feelings or behaviors related to the somatic symptoms. Worries about seriousness of symptoms. High level of anxiety about health or symptoms. Excessive time and energy devoted to...
  • Case Presentation Conference -Memorial- January 24, 2002

    Case Presentation Conference -Memorial- January 24, 2002

    Case Presentation Conference-Memorial-January 24, 2002 Jason Hunt M.D. Brian Kerr M.D. Peter Rigby M.D. Chief Complaint 65 y.o. female presents with complaint of decreased hearing in the left ear.
  • Interação com Agentes Pedagógicos Animados: Um Estudo Comparativo

    Interação com Agentes Pedagógicos Animados: Um Estudo Comparativo

    Então, se um aluno rientado a performance que sempre tira uma nota boa, tirar uma nota excelente é um evento não esperado e gera satisfação com maior intensidade. O outro trabalho que também infere as emoções do aluno através de...
  • Commonwealth of Virginia's Disaster Response System

    Commonwealth of Virginia's Disaster Response System

    Mission Statement To protect the lives and property of Virginia's citizens from emergencies and disasters by coordinating the state's emergency preparedness, mitigation, response and recovery efforts. May 4, 2015
  • web.stanford.edu

    web.stanford.edu

    Optimal Routing Abtin Keshavarzian Yashar Ganjali Department of Electrical Engineering Stanford University June 5, 2002 Motivation Outline Background: Cells vs. Packets Basic extensions of cell switching algorithms Stability of packet switching algorithms Waiting Algorithms Non-waiting Algorithms Stability under i.i.d. traffic...
  • Single Line Tethered Glider - Rochester Institute of Technology

    Single Line Tethered Glider - Rochester Institute of Technology

    Bridle attached at two points on the fuselage causes structural failure at the wing root with 180 MPa. ... Works well when the ball joints are kept in tension as seen in Fig 1. ... Single Line Tethered Glider