Manual Testing


Updated On 02 Feb, 19


Software Testing Introduction - What is testing - Why test software - Waterfall and V Model in Software Development Life Cycle - Software Requirements Analysis - Software Testing - How to create a powerful test strategy - Agile Testing - Example Agile Test Strategy and Agile Test Plan - Manual Testing Training - What is Test case - QA Tester Interview Questions - Example - How to write effective test cases quickly - What is test data and what are the types of test data - System Testing - Software Testing - Regression Testing - Software Testing - Requirements Traceability Matrix - RTM - Software Testing Tutorial - Reports - how to test software reports - How to report bugs effectively - Testing Basics - Software Test Report - Software Testing Tutorial - Software tester job role - Equivalence Partitioning and Boundary Value Analysis - Software Testing Tutorial - Decision Table Testing Explained with Examples - Software Testing Tutorial - Use Case Testing: Test Design Technique - State Transition Testing - Software Testing Tutorial - How to get Industry Domain Knowledge - How to Test Software without Requirements - Top tips to get software testing jobs - How to become Software Testing Expert - Test Estimation techniques, formula, example and Q&A - Test Lead Interview Questions And Answers


Lecture 18: Use Case Testing Test Design Technique

4.1 ( 11 )

Lecture Details

Use Case Testing Test Design Technique

In this video, we understand use cases, review a sample use case and write test cases for the example use case. A use case is a list of steps to complete a task in the system. These steps define the sequence of interactions between the actor and the system under test. The actor can be a user of the system or it can be another system. The use case lists the main scenarios (and optional exceptional scenarios). A use case may be accompanied by a use case diagram, but not always.
In use case testing, we review the use case e.g. the ATM cash withdrawal use case should only have the steps related to cash withdrawal, not the steps to view balance or deposit cash because the latter steps belong to other use cases. The use case should list all the steps in the normal workflow (scenario). Each step in the use case should be testable. The use case should list each alternate workflow. We design test cases to test the normal workflow and each alternate workflow. We can design the test data using other test design techniques like equivalence partitioning and boundary value analysis. When we run the test cases, we should look out for any missing workflow(s), any missing step(s) in any workflow, boundary value defects etc.

Sample Use Case Name Cash withdrawal
Actors Customer, Bank
Description This use case describes how the Customer uses the ATM system to withdraw cash from his her bank account.
1. The ATM system is online.
2. The ATM system has sufficient cash available.
Normal workflow
1. The Customer will insert their debit card.
2. The System will prompt for the PIN.
3. The Customer will enter the PIN.
4. The System will display the option to "Withdraw Cash".
5. The Customer will select the option to withdraw cash.
6. The System will prompt for an amount.
7. The Customer will enter an amount.
8. The System will submit the amount to the Bank for approval.
9. The Bank will confirm the transaction.
10. The System will dispense the cash amount.
11. The System will return the card.
12. The use case ends with a success.

Alternate workflows
4a. If the PIN is invalid,
1. The System will return the card.
2. The use case ends with a failure.

8a. If the amount is invalid (see additional business rules),
1. The System will display an error message and prompt for another amount.
2. The use case resumes at step 7.

10a. If the Bank declines the transaction,
1. The System will return the card.
2. The use case ends with a failure.

3a,5a,7a If the Customer selects the option to "Cancel",
1. The System will return the card.
2. The use case ends.

Additional business rules UCW1 - The System will dispense a maximum amount of $100 in a single transaction.
Post-conditions The Customer will receive their cash amount.

Online training in Programming, Scripting, Technology, SQL, Software Testing, QA, Automation Testing with Selenium, Load Testing with JMeter, Database testing and others

Software Testing Space - Quality content on test automation and performance testing using tools, automated testing, test strategies, manual testing, news updates and general self help guide at httpinderpsingh.blogspot.com

1. Subscribe to our channel to enjoy the new videos. If you like the videos, please like and share.

2. Subscribe to our Software Testing Space blog at httpfeedburner.google.comfbamailverify?uri=SoftwareTestingSpace&loc=en_US

3. Join Software Testing Space group in LinkedIn at httpwww.linkedin.comgroups?gid=3055677

Copyright © 2009-2015 Software Testing Space All Rights Reserved.

"use case"
"use case testing"
"test case"
"Test Design"
"software testing"
"testing software"
"software testing tutorial"
"agile software testing"
"testing tutorial video"
"testing training"
"qa training"
"quality assurance training"
"qa testing training"
"testing training online"
"qa training online"
"testing training courses"
"qa training courses"
"testing tutorial video"
"testing online training free"
"qa online training free"
"software testing training online"
"quality assurance training online"
"qa tester training"
"software testing courses for beginners"
"testing courses online"
"equivalence partitioning"
"boundary value analysis"
"use case examples"
"use case testing examples"
"use case samples"
"use case testing tutorial"
"test design techniques"
"process flow"
"normal workflow"
"alternate workflow"
"post condition"
"ATM example"
"Software Testing (Industry)"



0 Ratings
comment person image


Excellent course helped me understand topic that i couldn't while attendinfg my college.

comment person image


Great course. Thank you very much.