Use Case Based Testing in Software Testing: A Comprehensive Guide, Lecture notes of Software Engineering

Software Testing Lecture Slides

Typology: Lecture notes

2020/2021

Uploaded on 07/03/2021

muhammad-haris-15
muhammad-haris-15 🇵🇰

6 documents

1 / 14

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Chapter 5:
Dynamic Analysis-Test Design Techniques
Software Testing
Lecture 7
Use Case Based Testing
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe

Partial preview of the text

Download Use Case Based Testing in Software Testing: A Comprehensive Guide and more Lecture notes Software Engineering in PDF only on Docsity!

Chapter 5:

Dynamic Analysis-Test Design Techniques

Software Testing

Lecture 7

Use Case Based Testing

Use Case Based Testing Use Case:  (^) List of steps to achieve a goal  (^) Interaction between the actor and system  (^) Captures functional requirements of the system  (^) Document describing end to end behavior of the system from user perspective

  • User Action
  • System behavior  (^) It defines the main scenarios (and optional exceptional scenarios)
  • Scenario is sequence of events or workflow

Use Case Based Testing  (^) Black Box Testing  (^) Tests are designed to execute user scenarios  (^) Helps us to identify test cases that exercise the whole system.  (^) Testing of typical and exceptional workflow scenarios for the system  (^) Functional Testing  (^) Done from two side

  • Actors
  • Stakeholders  (^) Helps to uncover integration defects

Deriving Test Cases with Use Cases  (^) Tests check the typical use of the system

  • Test case table for normal scenarios  (^) Every extensions must be tested by a test case
  • Test case table for exceptions  (^) If more than one extension exists test the functionality of the important one  (^) Important for acceptance of system

Example 1: Flight Reservation Application Use Case Name Login Use case Description A user login to System to access the functionality of the system. Actors Customer, Admin Pre-Condition System must be connected to the network. Main Success Scenario Step Description A:Actor S:System 1 A: Enter Agent Name & Password 2 S: Validate Password 3 S: Allow Account Access Extensions 2a Password not valid S :Display Message and ask for re-try 4 times 2b Password not valid 4 times S :Close Application

Example 2: ATM Use Case Name: Cash Withdrawal Actors : Customer, Bank Description: This Use case describes how the customer uses the ATM system to withdrawal cash from his/her bank account Pre-conditions:

  1. ATM system is online
  2. The ATM system has sufficient cash balance.

Example 2: ATM Withdraw Cash

Extensions:

Example 2: ATM Withdraw Cash Additional Business rule:  (^) The system will dispense a maximum of $100 in a single transaction Post conditions:  (^) The system will receive their cash amount. Now do Use Case Testing

  1. Review the use case whether the requirements are complete or not
  2. Review the Exceptions workflows whether they are complete or not.

Advantages and Disadvantages of Usecase based testing Advantages:  (^) User focused  (^) Access better  (^) Quality requirements Disadvantages:  (^) Not suitable for non-functional requirements

Thank you