Software Test Document For Online Backstage Management System

Each group will need to submit a Software Test Document. The document will describe, in as much detail as possible, a full testing suite for the Online Backstage Management System. The testing suite should include descriptions of the unit, integration and system testing levels and contain a detailed requirements traceability matrix.

To create the Software Test Document, groups should use the format shown in the sample Software Test Documentation shown.

• master test plan
• level test plans for unit, integration and system testing levels that should relate to the requirements traceability matrix
• level test designs for unit, integration and system testing with details of the specific test data for each of the test cases

Critically evaluate software requirements as inputs toward testing of the final solution

Analyse and critically evaluate appropriate tools and techniques to support the testing process

Develop a good understanding of selecting and applying measures and models used for testing that are compliant with the appropriate professional industry standards such as the ACS and IEEE

Critically reflect on the outcomes of software testing and propose strategies for improving quality and performance outcomes in the software process

Analyse and critically evaluate software requirements and proposed solutions

Apply complex decision making to select appropriate testing techniques

Write professional level management, planning, quality assurance and testing documentation for a software system

Apply effective testing techniques to software systems of varying scales and test levels

Work in a team to evaluate and implement appropriate methods for determining quality and reliability in software systems

Undertake quality assurance processes

Develop and maintain plans for scheduling quality assurance tasks including software testing

Carry out the process of software testing and writing reports detailing the results;

Implementation of project management principles with respect to software testing

Purpose and Objectives of the Test

The software testing plan is created for online backstage management system and the different strategy for testing the project are adopted for the creation of the software testing plan. The purpose and the objectives of the software testing plan is documented below:

The following things are required to be reviewed for testing the functionality of the online backstage management system.

1. The requirement of the project and the information that exists for the development of the project.
2. Analysis of the business requirement and the transaction that are required to be critically tested.
3. Strategies and the types of testing is required to be selected for the implementation of the testing plan
4. A testing schedule is required to be prepared for the proper working of the testing plan and help to develop a quality end product.

The document is prepared to act as a base platform for testing the online backstage management system. The main objectives of the project is to analyze that the project meets the requirement of the project and the document should act as a guideline for the testing team for testing the functionality of the system that are embedded as a functional module. The test document also helps to evaluate the quality of the final build product and reduce the number of errors in the system.

In this section the different scope for the development of the online backstage management system are discussed with respect to the in scope and the out scope items.

The main scope of the testing plan is that the software is tested in a PC with intel i3 processor and 4 GB of ram. The following tests are done such as unit testing, system integration testing, system testing and final acceptance testing. For performing each of the test one week time is taken and thus the total testing procedure continues for 1 month. In the testing of the software the following functionality of the software are tested such as:

• The login validation of the admin
• Adding or deleting new user for the system
• Controlling different nodes
• Updating of the profile of the user
• Addition or deletion of a node.

The performance of the software depends on the hardware and the platform where it runs and thus it is out of scope of the project. The cluster of computers where the software is targeted to run is also kept out of scope for testing the software.

The following table is created for assigning roles and responsibility to the resources involved in testing of the software application “Online Backstage management System”.

There are different types of test plans such as mater test plan, testing level specific test plan and testing type specific test plan. The scope of the project is required to be prepared for identification of the limitation of the project and the following tests are required to be done for creation of the test plan. The testing level specific test plan is followed for the preparation of the test document of the online backstage management system.

1. Unit Testing- The test is done to verify the logic of the program which is compared with the structure of the program and the knowledge of the testing team. As a customer, unit testing is not something you will find in a final result it's a kind of testing performed amid the coding stage. The testing team can simply determine that a potential engineer that is employed utilizes unit testing amid the advancement stage to guarantee your item has decreased consistent bugs.
2. Integration Testing- The entire system is considered for testing and the functionality of the system is tested according to the proposed design and the specification of the project. The different components and the modules created for adding functionality to the online backstage management system is required to be integrated and tested for proper working of the whole system. The system integration testing is required to be done on multiple platform such that the prepared application should work on all platforms.
3. Business requirement- The test is done to verify the requirement of the customer and meet the business requirement and increase the efficiency of the online backstage management system. The software product developed is required to be analyzed according to the business requirement and different criteria for performing the test is required to be developed for testing the functionality of the system. The test case is required to be designed and the results of the test is required to be verified for tracking and managing the defects of the final software product.
4. User acceptance testing- The test is required to be performed by a group of friendly user and the objectives of this testing is that the customer expectation is required to be met. It is the final phase of the testing and it is performed before launching the software in the market. The main target for performing the user acceptance testing is validation of the end to end flow of the business. The user acceptance test environment is separated from the normal test environment and the participants of the user acceptance testing are the client and the targeted end users.

The above mentioned tests are performed by creating a test case. The test cases are developed and shown in the table below:

The test case in the above table are described in the following table for increasing the efficiency of development process of the online backstage management system.

Conclusion

For the creation of the test plan different steps are required to be followed such as the description of the test design which is further divided into description of the test procedure and description of the test case. The next step is the execution of the testing and storing the incident of the report and create a test log. The final step is the creation of a summary test report. The main goals of the report are to accomplish requirements that are described in the test plan and install a measurable, manageable and repeatable testing procedure. The various functionality of the components of the current version of the software are evaluated and the errors occurring in the system are resolved for development of a quality software product.

References

Considine, C., Crowley, S., Gardner, G., Shannon, C., Kwinn, M. J., Henderson, S. J., & Santamaria, P. (2016, April). Architecting a development and testing plan for the Army's common operating environment: Applying agile systems of systems development to army network acquisition. In Systems Conference (SysCon), 2016 Annual IEEE (pp. 1-6). IEEE.

Hass, A. M. (2014). Guide to advanced software testing. Artech House.

Lewis, W. E. (2016). Software testing and continuous quality improvement. CRC press.

Schultz, J. L. (2015). Software Testing Guide to Ensure Effective and Efficient Health Information Technology Testing (Doctoral dissertation, The College of St. Scholastica).

Sharma, C., Sabharwal, S., & Sibal, R. (2014). A survey on software testing techniques using genetic algorithm. arXiv preprint arXiv:1411.1154.