logo

Software Testing Plan: Document

14 Pages2197 Words359 Views
   

Added on  2020-04-01

Software Testing Plan: Document

   Added on 2020-04-01

ShareRelated Documents
Running head: Software Testing1Software TestingNameAffiliate Institution
Software Testing Plan: Document_1
Running head: Software Testing2Table of Contents1. INTRODUCTION...........................................................................................................31.1. System Overview......................................................................................................31.2. Testing Approach......................................................................................................32. TEST PLAN....................................................................................................................52.1. Program Modules......................................................................................................52.2. Features to be Tested................................................................................................52.3. Features Not to be Tested.........................................................................................62.4. Environmental Requirements...................................................................................63. TEST CASE.....................................................................................................................73.1. Pass / Fail Criteria...................................................................................................113.2. Testing Procedure...................................................................................................113.3. Test Deliverables....................................................................................................113.4. Testing Tasks..........................................................................................................123.5. Responsibilities.......................................................................................................123.6. Test Schedule..........................................................................................................124. Conclusion.....................................................................................................................12References..........................................................................................................................14
Software Testing Plan: Document_2
Running head: Software Testing31.INTRODUCTIONThis report defines the process and expectations for testing online backstage managementsystem.1.1. System OverviewThe objective of this document is to offer a manual on the testing procedures and expectedoutput. It outlines the essential functionalities of the online backstage management systemand may be utilize to train the users of the system on the general system functionality. It willinclude testing of individual modules to ensure it meets the user requirements and aligns withthe expected output. The basic overview of this document outlines test plan, that is, featureto be tested, those not to be tested, technical environmental requirement, test cases, testdeliverables, test procedure among others. The goal of this test procedure is to make surethat the system meets the set specification, high level of confidence, accuracy andimportance or project deliverables. 1.2.Testing ApproachTesting is an activity of assessing a software and application components to uncover thevariance between present and needed objectives and to analyze the characteristic ofcomponents of application under development. The process of assessing the onlinebackstage management system involves manual and automatic tests. Set of customscripts perform automatic tests on items of the system that don’t require interaction of theuser. On the other hand, testers or developers test manually items that require userinteraction. Testing is a very reliable operation. As such, testing an application is acontinuous operation done through the development stages of a system. Test plans shouldbe generated at each test level (Hass, 2014).
Software Testing Plan: Document_3
Running head: Software Testing4Component Testing- component is the smallest unit of any system. As such, Componenttesting is a method of testing the smallest unit of any system or application. Anapplication can be assumed as a merge and integration of several small individual units.Before testing the whole system, it is important that every component or the lowest unitof the system is tested carefully. In online backstage management system, every unit istested independently. Each unit gets an input, some processing is done and generates theresult. The output is then approved against the anticipated feature (Myers, Sandler &Badgett, 2012). Integration Testing- System Integration Testing is done to validate communicationbetween the units of an online backstage management system. It involves validation ofthe low and high-level software needs stated in the Software Requirements descriptions.It also validates the online backstage management system's conformity with others andexamine the interface between units. Units are tested individually first and thencombined to form a system. Security Testing- Efforts will be made to access the online backstage management systemwithout right authentication. Testing should be done to make sure that only grantedauthentication accesses occurs. Test carried out attempts the scripting of the cross-sitesafety holes and overflow buffer to make sure the system is not exposed to a maliciousthreat. Performance Testing- is carried out manually. Test team will test the system bycommunicating with it through the user interface and determine if the response time iswithin acceptable/ reasonable limits. Response time is the amount of time the systemtakes to respond to users’ requests. Performance testing is considered unsuccessful if thetester can determine response, in hours or minutes, with a normal clock. (Homes, 2013).
Software Testing Plan: Document_4

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Software Testing
|5
|643
|199

Software Test Documentation
|16
|2799
|68

Software Test Documentation
|13
|2472
|425

Software Test Documentation
|18
|3251
|77

Software Testing: Types, Approaches, Plan, Cases, Logs, Results
|15
|1230
|76

Software Test Documentation for eStage Backstage Management System
|20
|4069
|113