1 / 8

Use Case Testing Bin Ma – u4446201 Ji Zhang – u2580936 Lavanya – u4441325

Use Case Testing Bin Ma – u4446201 Ji Zhang – u2580936 Lavanya – u4441325. Definition of use case A use case is a sequence of actions performed by a system, which combined produce a result of value to a system user.

eleanor-rowe
Download Presentation

Use Case Testing Bin Ma – u4446201 Ji Zhang – u2580936 Lavanya – u4441325

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Use Case TestingBin Ma – u4446201JiZhang – u2580936Lavanya – u4441325

  2. Definition of use case A use case is a sequence of actions performed by a system, which combined produce a result of value to a system user. Use cases are a type of process flow model, so they are similar in concept (and in how to test them), to classic flow models like data flow diagrams and cause-effect graphs. Use cases capture requirements in a readable, refutable format. Relationship between use cases and requirements Use Case requirements

  3. Identify alternative course in RRP • Brainstorming, Checklist, Fault tree, Functional and non- functional requirement • Participants • stakeholders drawn from different backgrounds • domain expert and an end-user • Project Manager, Analyst, System Designer, Programmer, End User Requirement Review Process

  4. The test case(s) verifies that the system does in fact perform this function as expected which described by the use case • Path-Based Test Cases • Input-Based (Domain) Test Cases • Boundary Value Test Cases • Feature Interaction Test Cases Developing method from use case to test case

  5. Automation tools • Requirement management tools: • CaliberRM Borland • IBM Rational RequisitePro IBM • DOORS Telelogic • Automatically generate test case: • NetBeans 3.6, Eclipse Java IDE • Visual Test IBM • Test::LectroTest Perl

  6. Finding scenarios in a use case From: http://www.ibm.com/developerworks/rational/library/04/r-3217/

  7. Typical non-functional requirements: • Performance, Scalability, Capacity, Availability, Reliability, etc. • Cover non-functional requirements in use case testing: • Add the non-functional requirements to the use case document. • Identify the use case specify Non-functional requirements

  8. Advantages: • focus attention on the user, rather than on the actions the system performs. • incorporated with OOA/D methodologies and widely accepted. • a systematic approach to developing the information necessary for test design. • Disadvantages: • no agreement on appropriate methodology. • not typically used to specify performance, fault-tolerance, etc. Pro and con of use case testing

More Related