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.
- The requirement of the project and the information that exists for the development of the project.
- Analysis of the business requirement and the transaction that are required to be critically tested.
- Strategies and the types of testing is required to be selected for the implementation of the testing plan
- 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”.
|
Role |
Responsibilities |
Resource Name(s) |
|
System Testers |
Planning for the activities to be tested Execution of the test cases Evaluation of the project report and identification of the errors in the project Measurement of the effort required to be applied in the software testing Analysis of the results of the test. |
|
|
System Developers |
To develop the software according to the requirement of the client Cooperate with the system tester and give feedback regarding the functionality of the system. Share knowledge and the expertise for the application they developed Accept the errors and resolve it immediately |
|
|
System Analysts |
Interview the users Creation of requirement for the business Creation of test scenario and development of the test case |
|
|
Users |
Description and reviewing the requirement of the business Reviewing and describing the profile of the user Testing the acceptance of the customer |
|
|
Administrators |
Installation of the system application Trouble shooting the hardware and the software Gather information regarding the system where it is running |
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.
- 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.
- 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.
- 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.
- 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:
|
ID of Use case |
Description |
|
UC-1 |
Use Case- Login |
|
UC-2 |
Use Case- Update Profile |
|
UC-3 |
Use Case- Reboot |
|
UC-4 |
Use Case- Adding or delete a user |
|
UC-5 |
Use Case- Adding or Deleting node |
|
UC-6 |
Use Case- Power up |
|
ID of Test Case |
Description |
|
TC-1 |
Use Case- Login |
|
TC-2 |
Use Case- Update Profile |
|
TC-3 |
Use Case- Reboot |
|
TC-4 |
Use Case- Adding or delete a user |
|
TC-5 |
Use Case- Adding or Deleting node |
|
TC-6 |
Use Case- Power up |
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.
|
Test Case |
Use Case ID |
Description |
Result |
|
TC-1 |
UC-1 |
The user is required to enter a username and password |
The username and the password validation is checked and the user is granted to access the system |
|
TC-2 |
UC-2 |
The information residing in the information system is edited and the view is updated for selection of the profile section of the user |
A pop up message is displayed on successfully updating the system and ask the user for confirming and returning back to the profile page of the user. |
|
TC-3 |
UC-3 |
The reboot option is required to be clicked and the nodes linked with system should be listed as a node list. |
A pop up message is required to be generated after rebooting is done and status of the machine becomes ready for handling different programs. |
|
TC-4 |
UC-4 |
The add and delete option is required to be managed by the system admin and control the operation of the users. |
A pop up message appears when a user is created successfully. |
|
TC-5 |
UC-5 |
Admin clicks on nodes button and selects add/delete node option |
Confirmation screen is displayed verifying that selected nodes are added/deleted |
|
TC-6 |
UC-6 |
Admin clicks the nodes button , Once the nodes are listed, clicks on the Red power button |
A message is displayed on startup and the colour of the button becomes green. |
|
TC-7 |
UC-7 |
To list the user menus the admin can click on the accounts option placed in the online back stage management system. |
.the list of the users are generated with their name and the types. |
|
Task |
Artifacts |
Projected Completion |
|
Completion of the test plan |
Test Plan document Version 1.0 |
13/05/2017 |
|
Preparation of the test environment. |
Hardware and software elements |
20/05/2017 |
|
Execution and recording the test cases |
Collection, Test Plan Document version 1.0, Test Result Document |
27/05/2017 |
|
Submission of the defects and tracking the changes to be done in the system. |
Unit Testing Results Document |
03/06/2017 |
|
Integration testing |
Test Plan Document Version 1.0 |
10/06/2017 |
|
Acceptance of the client |
Test Plan Document Version 1.0 |
17/06/2017 |
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.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
