Challenge Overview
Project Overview
Styx Dashboard is a web application used to monitor various types of server metrics. It consists of the frontend displaying the data and backend windows services collecting metrics data to be displayed.
Challenge Objective
The goal of this competition is to develop a quality assurance plan and test scenarios to ensure that the frontend requirements are met and the application works correctly. The plan and scenarios should test the application requirements for both positive and negative cases.
This challenge must cover both the free version and full version but test scenarios for them should be in different sheet.
Please make sure you cover all pages from the prototype and all related requirements from the application specification.
IMPORTANT
When writing test scenarios you must properly define data setup so we can use that to support a bug hunt later. For example if you have test cases to test two aspects (maybe two corner cases) it is not realistic to clear out the database between test cases. We need the data to somehow co-exist, say, define them for different comm server instances maybe. You do not need to exactly produce the script to generate/load data, but should define the nature and amount of data and we can use f2f to generate bulk data.
Test Type Descriptions
Only the following types of tests are in scope for the current contest. So please prepare the test scenarios document for the current application by considering the following tests.
- Functional Test
- Performance Test
- Integration Test
- GUI Test
Technologies
- HTML
- ASP.NET
- Angular.js
Provided Resources
Documentation Provided
The following documentation will be available in the challenge forum:
- Specification
- Prototype (note the prototype needs to be put under a web server in order for it to work)
Final Submission Guidelines
Submission Deliverables
- Test Scenarios Document: word document, must be compatible with Microsoft Word
- QA Plan Document: spread sheet, must be compatible with Microsoft Excel
Final Submission
- Your final submission must contain a single .zip file with all the submission deliverables.
- For each member, the final submission should be uploaded to the Online Review Tool.
- You must not include any identifying information, such as your handle, in your submission. Your submission should be anonymous and you will be scored down in screening for not complying.