Douglas HoffmanCopyright © 1999 2013, SQM, LLC.1 Test Automation Architectures: Planning for Test Automation Florida Tech Testing 2 January 27, 2014 Douglas.

Slides:

Advertisements

Similar presentations

GUI Testing By Norbert Haché. Contents b What is GUI testing b Elements of GUI testing b Old Approach (TRUMP Project) b Scripting b Capture / Replay b.

Advertisements

2004 Cross-Platform Automated Regression Test Framework Ramkumar Ramalingam, Rispna Jain IBM Software Labs, India.

TTCN-3 Test Case Generation from arbitrary traces Capture & Replay Bogdan Stanca-Kaposta & Theofanis Vassiliou-Gioles (Testing Technologies)

Actors and use cases Use-case diagram Brief notation Prioritization Fully dressed notation Requirements Functional requirements  Use-cases.

T-FLEX DOCs PLM, Document and Workflow Management.

6/1/2015Ch.31 Defining Enterprise Architecture Bina Ramamurthy.

Use-case Modeling.

Informatics 43 – May 5, Restatement of goals Want to verify software’s correctness  Need to test  Need to decide on test cases  No set of test.

Systems Analysis and Design in a Changing World, Fourth Edition

The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.

IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? Why do we care about the difference.

Hierarchical GUI Test Case Generation Using Automated Planning Atif M. Memon, Student Member, IEEE, Martha E. Pollack, and Mary Lou Soffa, Member, IEEE.

WNT Client/Server SDK Tony Vaccaro CS699 Project Presentation.

7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.

Recall The Team Skills Analyzing the Problem

IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? What is data, information and.

© 2008 IBM Corporation Behavioral Models for Software Development Andrei Kirshin, Dolev Dotan, Alan Hartman January 2008.

High Level: Generic Test Process (from chapter 6 of your text and earlier lesson) Test Planning & Preparation Test Execution Goals met? Analysis & Follow-up.

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Verify the quality and.

Introduction to Software Testing

New Features of APV-SRS-LabVIEW Data Acquisition Program Eraldo Oliveri on behalf of Riccardo de Asmundis INFN Napoli [Certified LabVIEW Developer] NYC,

Automating your Business Processes Using Oracle Workflow Therron Hofsetz Logical Apps, Inc.

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Automatically control.

Włodzimierz Funika, Filip Szura Automation of decision making for monitoring systems.

Software Testing Lifecycle Practice

Copyright (c) Cem Kaner Black Box Software Testing (Academic Course - Fall 2001) Cem Kaner, J.D., Ph.D. Florida Institute of Technology Section:

Software Component Technology and Component Tracing CSC532 Presentation Developed & Presented by Feifei Xu.

Capture and Replay Often used for regression test development –Tool used to capture interactions with the system under test. –Inputs must be captured;

From Use Cases to Test Cases 1. A Tester’s Perspective  Without use cases testers will approach the system to be tested as a “black box”. “What, exactly,

INFSO-RI Enabling Grids for E-sciencE Logging and Bookkeeping and Job Provenance Services Ludek Matyska (CESNET) on behalf of the.

Testing Workflow In the Unified Process and Agile/Scrum processes.

What is software testing? 1 What are the problems of software testing? 2 Time is limited Applications are complex Requirements are fluid.

Copyright (c) Cem Kaner. All Rights Reserved. 1 Black Box Software Testing (Professional Seminar) Cem Kaner, J.D., Ph.D. Professor of Computer.

April 2004 At A Glance CAT is a highly portable exception monitoring and action agent that automates a set of ground system functions. Benefits Automates.

Software Testing Reference: Software Engineering, Ian Sommerville, 6 th edition, Chapter 20.

Lightning Talks Presented at the Software Test and Performance Conference 2008 San Mateo, California April 17, 2008.

® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.

1 Use Case Diagrams Use Case Actor Use case description Use case realization (Scenario) Use case relationships –Extends –Uses.

What is Testing? Testing is the process of exercising or evaluating a system or system component by manual or automated means to verify that it satisfies.

Framework for MDO Studies Amitay Isaacs Center for Aerospace System Design and Engineering IIT Bombay.

Modelling Class T07 Conceptual Modelling – Behaviour References: –Conceptual Modeling of Information Systems (Chapters 11, 12, 13 and 14)

Eliciting Integration Scenarios As discussed during Meeting

Systems Analysis and Design in a Changing World, Fourth Edition

Chapter 8 Testing. Principles of Object-Oriented Testing Å Object-oriented systems are built out of two or more interrelated objects Å Determining the.

Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.

August 2003 At A Glance The IRC is a platform independent, extensible, and adaptive framework that provides robust, interactive, and distributed control.

Facilitating testing and monitoring of number entry systems in medical devices Abigail Cauchi, Christian Colombo, Mark Micallef & Gordon Pace.

1 TestDescription Schema Implementation in SAMe ATE ATML Meeting – Boston, MA October 2006.

7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.

© 2009 Artisan Software Tools. All rights reserved. Testing Solutions with UML/SysML Andrew Stuart, Matthew Hause.

George Wang, Ph.D. COMP 380/L Lesson 2. Use Case Use cases are a way to capture system functionalities (i.e., functional requirements) Based on use case.

AndroidGUITAR Final Design 6/24/ Group Members 6/24/  Matthew Green  Matt Brown  Chris Carmel  Asif Chowdhury  James DeBolt  Matt Orlove.

SOFTWARE TESTING TRAINING TOOLS SUPPORT FOR SOFTWARE TESTING Chapter 6 immaculateres 1.

Tool Support for Testing

Systems Analysis and Design in a Changing World, Fourth Edition

MIS 120 Test Planning.

PLM, Document and Workflow Management

Recall The Team Skills Analyzing the Problem

Behavioral Models for Software Development

ARTIFICIAL INTELLIGENCE IN SOFTWARE TESTING

Introduction to Software Testing

Taxonomy of Test Oracles

Design and Implementation

Notefied (web publishing)

Typical Workflow - today

CSE 1020:Software Development

 Is a machine that is able to take information (input), do some work on (process), and to make new information (output) COMPUTER.

T-FLEX DOCs PLM, Document and Workflow Management.

Presentation transcript:

Douglas HoffmanCopyright © , SQM, LLC.1 Test Automation Architectures: Planning for Test Automation Florida Tech Testing 2 January 27, 2014 Douglas Hoffman Software Quality Methods, LLC Heather Heights Place Saratoga, California Phone

Douglas Hoffman2 Test Automation is not just machines running tests! Copyright © , SQM, LLC.

Douglas Hoffman3 Test Automation Architecture through reporting results From selecting what to test Copyright © , SQM, LLC.

Douglas Hoffman4 Manual Software Tests Person initiates each test case Person must interact with the test, SUT, or the environment during the test case Person is required to act in order that analysis of test results takes place Person summarizes and reports results Copyright © , SQM, LLC.

Douglas Hoffman5 Automated Software Tests Able to run two or more specified test cases Able to run a subset of all the automated test cases No intervention needed after launching tests Automatically sets-up and/or records relevant test environment Runs test cases Captures relevant results Compares actual with expected results Reports analysis of pass/fail Copyright © , SQM, LLC.

Douglas Hoffman6 Levels of Automation Somewhere on a continuum: Fully automated software testing Semi-automated software testing Human software testing Copyright © , SQM, LLC.

Douglas Hoffman7 Key Automation Factors Components of SUT Important features and capabilities SUT environments Testware elements Access to inputs and results Form of inputs and results Copyright © , SQM, LLC.

Douglas Hoffman8 Simple Testing Model (Black Box) System Under Test Test InputsTest Results Copyright © , SQM, LLC.

Douglas Hoffman9 System Under Test Test Inputs Precondition Data Precondition Program State Environmental Inputs Test Results Postcondition Data Postcondition Program State Environmental Results Expanded Testing Model (Black Box) Copyright © , SQM, LLC.

Douglas Hoffman10 Test Oracles Copyright © , SQM, LLC.

Douglas Hoffman11 Testing Model With Oracle Test Results Postcondition Data Postcondition Program State Environmental Results Test Oracle System Under Test Test Inputs Precondition Data Precondition Program State Environmental Inputs Test Results Postcondition Data Postcondition Program State Environmental Results Copyright © , SQM, LLC.

Douglas Hoffman12 Architecting Automation Models for the SUT and environment Break down the software testing problem Decide on location(s) of automation Decide on level(s) of automation Describe the automation architecture (components and relationships) Copyright © , SQM, LLC.

Douglas Hoffman13 A Model For SUT System Under Test User GUI Functional Engine API Data Set Remote GUI User Copyright © , SQM, LLC.

Douglas Hoffman14 Break Down The Testing Problem System Under Test User GUI Functional Engine API Data Set Remote GUI User Copyright © , SQM, LLC.

Douglas Hoffman15 Location and Level for Automated Testing Availability of inputs and results Ease of automation Stability of SUT Practicality of Oracle creation and use Priorities for testing Copyright © , SQM, LLC.

Douglas Hoffman16 Automated Test Sequencing Testware version and configuration management Select the subset of test cases to run Set-up and/or record environment Run test exercises Monitor test activities Capture relevant results Compare actual with expected results Report analysis of pass/fail Copyright © , SQM, LLC.

Douglas Hoffman17 An Automated Software Testing Process Model Tester Test List Automation Engine Data Set Testware SUT Test Results         Copyright © , SQM, LLC.

Douglas Hoffman18 Automation Process List the sequence of automated events Identify elements of each event Decide on location(s) of events Determine flow control mechanisms Design automation mechanisms Copyright © , SQM, LLC.

Douglas Hoffman19 Conclusions Architecture design begins with analysis Model the SUT Break down testing problem Model the testing process Design the automation architecture KISS Copyright © , SQM, LLC.