Test Design and Analysis for MTEST

Running head: MTEST TEST DESIGN AND ANALYSIS
MTEST Test Design and Analysis
Name of the Student
Name of the University
Author Note

1
TEST CASE IDENTIFICATION FOR MTEST
Question 1: Real world example of software failure
A range of factors can be at play leading to software failures. In most cases these can
be due to making repeated changes without any plans for conducting follow up tests (Grottke
et al, 2015). Another vital role is played by the security aspect which is always under scanner.
When software programs are built without addressing the loopholes, attackers spare no time
in exploiting the vulnerabilities causing damages to both end user and the service provider
(Kanewala, Bieman & Ben‐Hur, 2016). Glitches and incomplete builds of the software
programs result in generation of erroneous output.
Flights in the aviation industry generally get cancelled because of bad weather and not
software. However in December 2014, one air traffic control centre (ATC) was compelled to
close down the airspace over London as the software tasked with management of departures
as well as arrivals started malfunctioning. Although this software got repaired almost
immediately and brought back up at the pretty fast, the consequences suffered as a result
major and affected flights widely. Heathrow ended up reporting a cancellation of more than
50 flights many of which had to turn back to their originating locations.
The entire incident was considered to be a technical problem at the Air Traffic
Control centre of Swanwick in England. This particular ATC is known for repeatedly
suffering from one issue to another. The responsible governing body NATS had to apologise
for the incident. Though official report by NATS blamed power outage, other reports
mentioned of a bug in the software responsible for sequencing landing and take offs that
could have been prevented if better software testing was conducted before implementation.

2
TEST CASE IDENTIFICATION FOR MTEST
Question 2: Identifying the test cases according to the scenarios created
based on requirements of the software
Different software testing strategies utilized for identifying the test cases of the
marking and grading application MTEST are negative testing, error guessing test cases,
boundary value analysis and equivalence class partitioning (Scott et al, 2015). The list of test
cases are given in the table below.
MTEST Application Test Design
Test Case_ID Scenarios Test Cases
Verify that
input files with
question count
0 gets
executed
MTST001
Validate that
the title record
has data
Verify error
script for title
records having
no data
MTST002
Validate No. of
questions >= 1,
<= 999
Verify that
input files
having No. of
questions: 1
get executed
MTST003
Validate No. of
questions >= 1,
<= 999
Verify that
input files
having No. of
questions: 999
get executed
MTST004
Validate No. of
questions >= 1,
<= 999
Verify that
error script
present when
No. of
questions
equal 0
MTST005
Validate No. of
questions >= 1,
<= 999
Verify that
error script
present when
No. of
questions
equal 1000