WRITING TEST CASES AND TEST DATA FOR IT

Slides:



Advertisements
Similar presentations
Object Oriented Analysis And Design-IT0207 iiI Semester
Advertisements

Tutorial 9 – Creating On-Screen Forms Using Advanced Table Techniques
Requirements Specification and Management
MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
Software Quality Assurance Plan
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Software Testing.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Execution and Reporting Adrian Marshall.
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Design & Documentation Adrian Marshall.
Configuration Management
1 SOFTWARE LIFE-CYCLES Elements and Definitions. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance The WATERFALL.
High Level: Generic Test Process (from chapter 6 of your text and earlier lesson) Test Planning & Preparation Test Execution Goals met? Analysis & Follow-up.
Introduction to Software Testing
Test Design Techniques
Chapter 9 Introduction to ActionScript 3.0. Chapter 9 Lessons 1.Understand ActionScript Work with instances of movie clip symbols 3.Use code snippets.
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
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,
INTRUDUCTION TO SOFTWARE TESTING TECHNIQUES BY PRADEEP I.
SOFTWARE CONFIGURATION MANAGEMENT. Change is inevitable when computer software is built. And change increases the level of confusion among software engineers.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
Dynamic Testing.
Quick Test Professional 9.2. Testing Process Preparing to Record Recording Enhancing a Test Debugging Running the Test and Analyzing the Results Reporting.
Writing Test Cases Why writing and tracking test cases is important? What is a test design specification? What is a test case specification? How test procedures.
The Quality Gateway Chapter 11. The Quality Gateway.
Web form enhancement – What are categories? – How do categories work? – Displaying a category and an account code – Where do we choose a category?
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
1 Customizing Forms and Writing QuickBooks Letters Lesson 15.
SOFTWARE TESTING TRAINING TOOLS SUPPORT FOR SOFTWARE TESTING Chapter 6 immaculateres 1.
LINGO TUTORIAL.
Functional testing, Equivalence class testing
Subject Name: Software Testing Subject Code: 10CS842 Prepared By:
Software Testing.
EGR 115 Introduction to Computing for Engineers
Group mambers: Maira Naseer (BCS ).
Using SHOPFLOOR with QUALITY control
Software Requirements
Object oriented system development life cycle
Welcome to Designing Letters
Algorithm and Ambiguity
UNIT-4 BLACKBOX AND WHITEBOX TESTING
Systems Design, Implementation, and Operation
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
Designing and Debugging Batch and Interactive COBOL Programs
Engineering Processes
Introduction to Software Testing
A Few Review Questions Dan Fleck Fall 2009.
A Few Review Questions.
The purpose of testing Artifacts Test in the sw Life Cycle Workers
Chapter 1 Introduction(1.1)
APPLICATION LIFECYCLE MANAGEMENT(ALM) QUALITY CENTER(QC)
Course: Module: Lesson # & Name Instructional Material 1 of 32 Lesson Delivery Mode: Lesson Duration: Document Name: 1. Professional Diploma in ERP Systems.
Lab 1 Introduction to C++.
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
PROGRAMMING AND LANGUAGES
PART06 Hands-on Training Identifying Test Scenarios and Test Cases.
APPLICATION LIFECYCLE MANAGEMENT(ALM) QUALITY CENTER(QC)
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Moodle Training — Advanced Topics —
PART 2 LESSON XX Creating Test Cases
Team 7- SCRIPTONOMICS Advanced movie script analytics made simple
Paper by D.L Parnas And D.P.Siewiorek Prepared by Xi Chen May 16,2003
HP Quality Center 10.0 The Test Plan Module
A Few Review Questions Dan Fleck Spring 2009.
Chapter 9 Testing the System Shari L. Pfleeger Joann M. Atlee
Test Cases, Test Suites and Test Case management systems
Software Requirements
Team 7- SCRIPTONOMICS Advanced movie script analytics made simple
UNIT-4 BLACKBOX AND WHITEBOX TESTING
Presentation transcript:

WRITING TEST CASES AND TEST DATA FOR IT Gennadi Jakutin

General meaning of test case concept A test case is a set of actions with the expected results based on requirements for the system Test cases have to provide full coverage of all technical (system) requirements for the product which is being tested Test cases should include a description of the functionality to be tested, and the preparation required to ensure that the test can be conducted. An effective test cases have to be developed from the position of “Constructive demolition”

Why do we need to test with strongly formalized but flexible test cases The key of successful testing lies in efficiency of the selected Test Cases Better test cases have more reliable results as well as lower cost in three categories: Productivity Testability Scheduling reliability Certain determination Aims Expected results Prevention of ambiguity We should be able to easily transform test cases for: Reusing for maintenance releases Regression testing

Requirements to quality of Test Cases Accurate Economical Repeatable and self standing Appropriate Traceable Self cleaning

The beginning of development of test cases The project Set of documents which describes the plan of test operation. Test projecting and developing test cases Improving and debugging test cases

Structure of the test case A test case specification shall have the following structure: Test case specification identifier Test items Input specifications Output specifications Environmental needs Special procedural requirements Intercase dependencies

Types of Test Cases Which one is the best one? Step-by-step Scenario goes from screen to screen Many processing rules Matrix Many variations of filling in a form Same inputs, different configurations or platforms Automated scripts Long lifecycle of testing

Example Step-by-Step test cases Action Expected result Pass/Fail 1 Click on element “Delivery cost” in Main Menu Delivery cost Menu displays on the screen P/F 2 Enter value “101” in the field of weight of cargo delivery “Weight of delivery is incorrect” error message appears 3 Enter value “0” in the field of weight of cargo delivery 4 Enter value “100” in the field of weight of cargo “Weight of delivery is 100 OZ” message appears

Example of matrix text case Suppose that we have 4 Size fields which have same input requirements: Must be greater than 0, but less than 1000 Must be integer Value -1 1000 12.3 ABC %^$ 1 999 Expected Result Fail Pass Length P/F Height Width Weight

Example of Automated script Case "TXT": # Edit Text # Parameters:Text Field Name, Value report_msg1("Setting the value in the textfield : "&params[1]&" as "&params[2],DEBUG); if(obj_exists(params[1],10) != E_OK) { FINAL_RESULT = "FAIL"; INTER_ACTION = "ERROR"; append(REMARKS_STRING,"Object : "&params[1]&" doesnot exist, so terminating the testcase."); desktop_capture_bitmap(MMName & "-" & TC_NUM ); } else ret = edit_set(params[1], params[2]); if(ret < 0) examine("edit_set",ret); append(REMARKS_STRING,“Text was inserted in“ &params[1] &“text field”); break;

Developing data for test cases Classes of equivalence. Oriented on lowering overall number of test cases Dividing input area of program into data classes Positive Negative Boundary values. Choosing elements on the borders of classes

Improving of test cases Testability Controlling length Cumulative cases Productivity Templates Clones Test management software

References Rapid Testing First Edition Robert Culbertson, Chris Brown, Gary Cobb How to write better test cases Dianne Runnels ieeestd-829-1998Test_documentation, IEEE www.wikipedia.org