Test Case MTEST Test Design

Running head: MTEST TEST DESIGN
Test Case MTEST Test Design
Name of the Student
Name of the University
Author Note

1MTEST TEST DESIGN
Question 1: Real world example of software failure
There are multiple aspects from which software failures can occur. These can be
updating software applications without having measures in place to test the application after
applied changes through retesting, regression testing (Harman, Jia & Zhang, 2015). An
important aspect is the security setup of software applications as applications having known
vulnerabilities present are targeted and exploited first by the attackers (Böhme & Paul, 2015).
The glitches and problem areas of applications generate undesired output and making the
software unreliable.
A software failure resulted in thousands of call drops for third party call centres who
are in the business of assigning and directing help calls to the emergency line 911. As per the
reports the software used in tracking as well as assigning calls contained counters which
topped at 40 million. The moment this 40 millionth call got placed, all other calls suffered a
bottleneck thereby cutting connections to more than 11 million citizens in more than seven
different states through the 911 hotline for emergency help calls.
The software in question is the automated system from Intrado for assigning uniquely
identifiable codes to the incoming calls before passing them which basically helps in tracking
phone calls moving in and out of the system.

2MTEST TEST DESIGN
Question 2: Identifying the test cases according to the scenarios created
based on requirements of the software
Equivalence class partitioning, error guessing, negative test cases and boundary value
analysis are the type of tests performed in identifying the test cases for MTEST. The list of
test cases for the software MTEST marking and grading application is given below.
Design of MTEST Test Cases
Test Case#
Scenario
Description Test Case
MTA001
Validate
validity of title
record sets
Verify that title
records having
data are
accepted by
MTEST
MTA003
Validate
question
number (1 -
999)
Verify that
error code
present when
question count
equals 0
MTA005
Validate
question
number (1 -
999)
Verify
execution of
input files
when question
count is 1
MTA006
Validate
question
number (1 -
999)
Verify
execution of
input files
when question
count is 999
MTA007
Validate
question
number (1 -
999)
Verify that
error code
present when
question count
equals 1000
MTA008
Validate count
of record sets
in columns (10
- 59)
Verify error for
multiple record
sets for
questions 1-50
MTA009
Validate count
of record sets
in columns (10
- 59)
Verify presence
of single record
between
columns (10-