We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byCharles McPherson
Modified over 2 years ago
QWE March © 2002 The authors, all rights reserved. Experiences in Testing the Pocket PC
QWE March © 2002 The authors, all rights reserved. Overview Scope of the Project Introduction to Model Based testing Case Study: the Pocket Inbox Conclusions
QWE March © 2002 The authors, all rights reserved. Project Scope Pocket PC : Operating platform developed by Microsoft for handheld devices. Contracted to develop software models for five applications: Contacts, Calendar, Inbox, Pocket Word and Connectivity Manager.
QWE March © 2002 The authors, all rights reserved. Model Based Testing: The Big Picture
QWE March © 2002 The authors, all rights reserved. Modeling with Finite State Machines A state is a condition of the software where a specific set of inputs can be applied. Two states are considered equal if the same inputs can be applied and they produce the same result.
QWE March © 2002 The authors, all rights reserved. Building Models : An Example
QWE March © 2002 The authors, all rights reserved. Case Study: the Pocket Inbox General Information 5,000 transitions 1,500 states Most complex application we tested Design choices Limited number of messages Input peculiarities
QWE March © 2002 The authors, all rights reserved. Case Study: Exploration Explore the application in order to discover and build a mental representation of its functionality For demonstration purposes, we only use a partial model
QWE March © 2002 The authors, all rights reserved. Case Study: Inputs Identify all user inputs 1. New: to go to a new message window 2. Ok: to leave the New Message screen and save the current message 3. Send: to leave the New Message screen and send the current message 4. Space: space character 5. AlphanumericChar: any alphanumeric character
QWE March © 2002 The authors, all rights reserved. Case Study: Input Applicability Identify the individual characteristics used to define the states of the application? 1. New: this input is applicable at any time. The user can press the New button when the general inbox screen is showing, when the window is New Message and whether he/she has entered text inside a New Message window. 2. Ok: this input is applicable when the window is a New Message. Whether the To field is empty or not does not make a difference. 3. Send: this input is applicable only when the window is a New Message and the To field is not empty. 4. Space: this input is applicable when the window is a New Message. 5. AlphanumericChar: this input is applicable when the window is a New Message
QWE March © 2002 The authors, all rights reserved. Case Study: State Variables Window = Inbox, NewMessage This operational mode records which window the user is on. For this model, only two windows are considered as possible. To Field = Empty, NotEmpty This operational mode records if the value of the To field is empty or not. It is useful to determine whether the Send is enabled or not.
QWE March © 2002 The authors, all rights reserved. Case Study: Transitions
QWE March © 2002 The authors, all rights reserved. Case Study: Test Cases
QWE March © 2002 The authors, all rights reserved. Case Study: Test Cases BUG
QWE March © 2002 The authors, all rights reserved. Conclusions Model-based testing needs to be coupled with exploratory techniques with the dual benefit of attaining a better, more current understanding of the system and harvesting many bugs along the way. Models are beneficial, not only as a point of reference for testing purposes, but also as a living specification of the functionality it represents and as a basis for test automation. Having a good automated test oracle is vital to the effectiveness of automated testing in general and model- based testing in particular.
QWE March © 2002 The authors, all rights reserved. Conclusion As long as finite state machines are used, there are inescapable critical issues to be dealt with: model building and maintenance, state explosion, and model correctness. There is need for more practical pointers on how to work around, or at least reduce the impact of these factors. Finally, studies need to be performed on answering the question: is model-based testing worth the effort when it comes to finding faults? Our preliminary results show that, for a very good, close-to-release, stable product, the number of faults uncovered by model-based testing is slightly disappointing if we severely limit the time during which we can run tests. The strongpoint of model-based testing is that it finds bugs with different characteristics: those that require long complicated sequences of inputs to be exposed.
QWE March © 2002 The authors, all rights reserved. Contact Information Web : Telephone : (321) Regular Old-Fashioned Mail : Herbert Thompson Department of Computer Sciences 150 W University Boulevard Melbourne, Florida 32901
Thursday, November 1, 2001(c) 2001 Ibrahim K. El-Far. All rights reserved.1 Enjoying the Perks of Model-based Testing Ibrahim K. El-Far Florida Institute.
An Introduction to Object Modeling An Introduction to Object Modeling The approach of using object modeling during systems analysis and design is called.
1 Introduction to Software Engineering Rajkumar Buyya Grid Computing and Distributed Systems Lab Dept. of Computer Science and Software Engineering University.
Interface Development: Integrating M&Ms Designer and Azteca Cityworks at the City of Concord, North Carolina June 2005 Copyright © 2005 O ne GIS, Inc.
Automata Theory November 2002 Introduction & NFAPart 1:
Converting DataQuest Reports or UDR’s to Excel or Word.
Software Upgrade & Conversion DBS2000 to Global Edge.
Planning an automatic provisioning system for a local telephone operator Instructor: Jorma Virtamo Supervisor: Jorma Virtamo This thesis was done at Partel.
1 Computer Systems & Architecture Lesson 3 5. Designing the Architecture.
1 Test documentation and Test case design Iana Mourza QA Lead/Release Lead VMware, Inc
(c) Copyright 2002 Ibrahim K. El-Far. All rights reserved. Presented at Quality Week Europe Selecting an Appropriate Software Testing Method Ibrahim.
COMPILER CONSTRUCTION WEEK- 4: INTRODUCTION TO COMPILER & INTERPRETER.
Mobile Development Introduction to Visual Studio Development Rob Miles Department of Computer Science.
Deiva Preetha/Sornalakshmi Asst Prof SRM University, Kattankulathur School of Computing, Department of IT 1.
State Machines An approach to assembler coding. Intro State Machines are an integral part of software programming. State machines make code more efficient,
NWSC November Math Cohort Meeting WELCOME! Nancy Berkas Cyntha Pattison.
What is the Value of Architecture Andrew L Macaulay Global Head of Architects Community March 2006 In collaboration with Microsoft Architect Insight Conference.
New Mexico Broadband Program Introduction to the Internet Module 1 Understanding the Internet Key Features of Websites Navigating within a website.
Tools and techniques that support user interface development Design support is needed because designing software is typically very complex and requires.
2 Welcome To Defect Management Training Objective: The objective of this course is to learn about standards that emphasize a best practice approach for.
Public Information Version 3.1: 1/1/2012 Introducing Instant Business Intelligence To IT BI Project Managers What you need, when you need it
Help Desk Procedures Topic 1 : What is a Help Desk? (by Greg Webb, Copyright © TAFE NSW) 1. Introduction In this unit you will learn what a help desk.
Copyright D Gurney 2006 Critical Thinking An Introduction to Situation Awareness and Decision Making This presentation provides an overview of how to improve.
1 IT Essentials I v. 3 Module 1 Information Technology Basics.
Software Quality Management CIS 376 Bruce R. Maxim UM-Dearborn.
Research Methods in Crime and Justice Chapter 10 Survey/Interview Research Methods.
Of An Expert System. Introduction What is AI? Intelligent in Human & Machine? What is Expert System? How are Expert System used? Elements of ES Who are.
Exploratory Testing – an improved approach Jayapradeep Jiothis Narendra Kumar by.
Advanced Software Engineering by Prof. Dr Jan Pajak Topic ASE-5 System-engineering based approach to Software Engineering.
© 2016 SlidePlayer.com Inc. All rights reserved.