Test Plan Iteration 2
Test Plan
• Purpose:
- This document is to lay out the test procedures that will be conducted to ensure that upon the final delivery of the projects, that all agreed requirements are successfully met.
• Prerequisites:
- The deployment of a demo website to reside on a server to work as the UI for inputting sample requests. The website will allow users to choose between different preferences guards that will determine the Booleans guards to be sent to the selector engine.
- The development of a Graphic User Interface (GUI) that will demonstrate the actual results of the final product. This GUI will be used to compare results between the newly developed solution with the current working system.
- The creation of multiple ArchStudio 3.0 architecture descriptions to be used as a sample data for the ArchStudio 3.0 repository.
- The creation of sample Boolean guards to be used as input for the Selector engine.
- Test Cases:
• Input Processing Through the Deployed website
• Selector/Repository communication Use Case
• Performance enhancement
• Simultaneous Submission and processing of multiple requests
Test Case 1
Input processing
- Description: To test that ArchStudio Selector will correctly accept the assumed input.
- Prerequisites: Input data samples (Boolean guards), Architecture descriptions, and the UI website for sending requests (Inputs)
- Execution:
- User is to complete the selection process of the different preferences on the demo website.
- The selection data is gathered and then sent to the Selector engine as a request (Boolean guards).
- Selector is to process the data.
- Selector engine is to communicate the expected correct tags with Repository.
- Repository to send the correct Architecture description to output
- Output is to be matched with expected output.
Test Case 2
Selector/Repository Communication Use Case
- Description: To test that the ArchStudio Selctor engine is properly communicating with the Repository to ensure correct output.
- Prerequisites: Correct input data samples matched with valid Architecture designs.
- Execution:
- Valid submission of input to the selector.
- Selector engine processing of the Booleans guards and send them to Repository.
- Repository sends the correct Architecture description to output.
- The architecture description is matched with expected Architecture design.
Test Case 3
Performance Enhancement
- Description: This test case and the next one are the most important test case. This test case is to ensure that the desired and improved performance of the Selector engine processing time of request is reached.
- Prerequisites:
- This test case is not to be executed prior to successful completion of the previous test cases. Once the previous test cases are completed successfully, this case is to be executed.
- Graphic User Interface (GUI)
- This GUI is to demonstrate the performance improvement by showing the processing time of requests using the system with the new (to be developed) Selector solution.
- Execution:
- A request is sent to the system with a known input and output.
- The newly developed Selector solution to be used
- Results are sent to the GUI
- Same request is sent to the system, using the current (old) selector engine to be used.
- Results are sent to the GUI.
- GUI is to calculate and show the time different between the new solution and the current solution used for the Selector engine of ArchStudio 3.0
- This whole process to be repeated several times to cover all different kinds of inputs and output.
Test Case 4
Simultaneous Submission and processing of multiple requests
- Description: This test case to demonstrate the improved performance of the new solution to be developed developed when employed for multiple requests sent and processed simulatenously.
- Prerequisites:
- This test case is not to be executed prior to successful completion of the previous test cases. Once the previous test cases are completed successfully, this final case is to be executed.
- Input text file with multiple requests.
- Execution:
- Multiple requests are sent simultaneously to the system through the input text file.
- The system is to receive and process all of the requests at the same time.
- The correct architecture descriptions for all of the different requests are then fetched from the repository and sent to the output.
- Outputted architecture descriptions are matched with the expected output.
- Finally, GUI is to show the time performance for this mutli-request case.
Final Notes:
• If more than one solution is to be developed, then all test cases are to be repeated for each of the developed solutuions.
• Compared results must be shown for all the different solutions.
If multiple solutions exist, the developer must recommend one solution to the customer depending on the performance results that will be generated from the test cases.