Software Testing: Types, Approaches, Plan, Cases, Logs, Results

This presentation provides an overview of software testing, including the different types of testing, approaches to testing, creating a test plan, writing test cases, maintaining test logs, and analyzing test results. It also includes incident reporting, bibliography, traceability matrix, Gantt chart, and budget for testing the online backstage management system.

ITECH7409:
SOFTWARE TESTING
NAME OF THE STUDENT
NAME OF THE UNIVERSITY
AUTHOR’S NOTE

INTRODUCTION
• The application of estage has been developed to manage online backstage while the design of the
application is made such that it would be able to select roles of each stakeholders which have been
associated with various managements of backstage. Users of this system have to login in information
system through selection of specific roles while also passing authentication mechanism to use various
features which are provided by this system. When the user is login successfully, users are automatically
redirected to welcome page in which various links are provided accordingly to different users. The users
could also select various options like logoff, home, discipline, sections and competitors.

TYPES OF SOFTWARE
TESTING
• Unit testing
• Black box testing
• White box testing
• Black box testing

TEST APPROACH
In order to proceed with testing of software applications, various different approaches should be
evaluated so that selection of best approach could be done in order to test online backstage
system for management.
• Unit testing
• Integration testing
• Business requirement testing
• User acceptance testing

TEST PLAN
• Features that are needed to be tested
• Features that are not needed to be tested
• Testing tool and environment

TEST CASES
• IT CONSISTS OF THE FOLLOWING
• CASE NAME
• PURPOSE
• INPUTS
• EXPECTED OUTPUTS & PASS FAIL CRITERIA
• TEST PROCEDURE

TEST LOGS
Task Artefacts Projected Completion
Test plan completion Preparing test plan doc v1.0 13/05/2019
Test environment preparation Hardware and software elements 20/05/2019
Record and execute test case Collection, Preparing test plan doc v1.0, Documenting Test
Result
27/05/2019
Change tracking and submitting defects of
the system
Unit test result documentation 03/06/2019
Integration testing Preparing test plan doc v1.0 10/06/2019
Client Acceptance Preparing test plan doc v1.0 17/06/2019

TEST RESULTS
Test Case Use Case ID Description Result
TC-1 UC-1 The role is needed to be selected from drop down The password and username is needed to be validated for granting the access to the user
TC-2 UC-2 The database is modified, updated and viewed for the selection of
profile section for a user
A message is needed to be popped up displaying successfully updated the records and take
confirmation for returning to user profile
TC-3 UC-3 Reboot option should be opted a node list is needed to be displayed
with the information of all nodes linked with the system.
After completing the reboot, a pop up message should be displayed with the current machine
status for handling programs
TC-4 UC-4 Management of add and delete option by administrator and monitor
/control user operation.
Generation of pop up message on successfully creating user
TC-5 UC-5 Addition or deletion of nodes from the admin profile Displaying a confirmation dialogue for verification of the step
TC-6 UC-6 Allowing the admin to click the node and start it or power it off Displaying message on start-up and changing the status of the node.
TC-7 UC-7 The menus are needed to be listed when the administrator clicks on
different option for account and the development of online backstage
management system
The user list is generated with their types and names.

INCIDENT REPORT
A notification is needed to be generated by the tester associated with testing the online backstage
management system and the notification is given below:
• Notification for software development team alerting them for reducing errors in the codes
• Defining the testing rules
• Assign personnel for usability testing

INCIDENT REPORT (CONTD.)
The incident report is also needed to be forwarded to the directors and the reporting is needed to
be done via email. The contract information is needed to be identified and the report should have
the following details:
• Contact information of the test team
• Description of the incident
• Effort status and determining the incident cause.

BIBLIOGRAPHY
• Barr, E. T., Harman, M., Mcminn, P., Shahbaz, M., & Yoo, S. (2015). The oracle problem in software testing: A survey. IEEE transactions on software engineering, 41(5), 507-525.
• Black, r. (2014). Advanced software testing-vol. 2: guide to the istqb advanced certification as an advanced test manager. Rocky nook, inc..
• Briand, l., Nejati, S., Sabetzadeh, M., & Bianculli, D. (2016, may). Testing the untestable: model testing of complex software-intensive systems. In proceedings of the 38th
international conference on software engineering companion(pp. 789-792). Acm.
• Deak, a., Stålhane, T., & Sindre, G. (2016). Challenges and strategies for motivating software testing personnel. Information and software technology, 73, 1-15.
• Godefroid, p. (2015). Between testing and verification: software model checking via systematic testing. In haifa verification conference.
• Harman, m., Jia, Y., & Zhang, Y. (2015, april). Achievements, open problems and challenges for search based software testing. In software testing, verification and validation
(ICST), 2015 IEEE 8th international conference on (pp. 1-12). Ieee.
• Kempka, j., Mcminn, P., & Sudholt, D. (2015). Design and analysis of different alternating variable searches for search-based software testing. Theoretical computer science, 605,
1-20.
• Long, t. (2015, july). Collaborative testing across shared software components (doctoral symposium). In proceedings of the 2015 international symposium on software testing
and analysis (pp. 436-439). Acm.

TRACEABILITY MATRIX
Test Case Document
Business
Requirement ID#
Business Requirement /
Business Use case
Functional
Requirement ID#
Functional Requirement /
Use Case
Priority Test Case ID# Execution
Status
Defect#
BR_1 Reservation Module FR_1 One Way Ticket booking High TC#001
TC#002
pass
FR_2 Round Way Ticket TC#003
TC#004
pass
FR_3 Multicity Ticket booking High TC#005
TC#006
Fail Defect#4523
BR_2 Payment Module FR_4 By Credit Card High TC#007
TC#008
pass
FR_5 By Debit Card High TC#009 pass
FR_6 By Reward Points Medium TC#010
TC#011
pass
Project Name: Online BackStage Management System
REQUIREMENTS TRACEABILITY MATRIX
Business Requirements Document
BRD
Functional Specification Document
FSD

GANTT CHART

BUDGET
Task Name Cost
Testing of online backstage management system $10,550.00
Understanding Requirement $1,100.00
Establishment of Traceability Matrix $600.00
Test Case Development $2,000.00
Peer review of the Test Cases $400.00
Incorporation of review comment in test case $250.00
Execution of the steps in test case $250.00
Mark the status Pass or Fail $500.00
Raise defects for the test case that has failed $2,500.00
Sending daily status of test to team lead $1,750.00
Completion of execution of test for the test cases $1,200.00