CCLKD: Create Tests for the Mock Report Generator
License and Copyright Notice
By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).
What is the goal or the problem, and why is it important?
The goal is to design and implement testing for the mock report generator from issue #28 (closed) that could be re-used for the actual report generator testing we will conduct in issue #10 (closed).
How are you going to achieve the goal or solve the problem?
We will use test driven development as we implement to generate a series of tests that will test the mock report generator against scenarios that range in complexity to ensure we cover all areas necessary for the clients needs. We will use Katalon testing software to run our test cases.
What will be produced as a result of this effort and where will it live on GitLab?
Test cases that cover all necessary areas such as reading in data from the csv we created, interpreting and properly formatting the data into a report, ensuring that the report generated meets our mock format, and other test scenarios that may have unique qualities to them. We will put our test cases in the scratch work project as that project properly suites issues that focus mainly on creating drafts of future implementations.
Give a justification of weight or due date.
- Due date: 4/25/2023
- Weight: 6
- Justification: Creating mock test cases depends on the mock generator so the weights should match each other and we want to have a little wiggle room to ensure we think of every possible test case incase we think of any down the road.
Who will do it, and what will they do?
All team members will look for and implement tests as we build the the report generator, what this will do is allow for each team member to think of different scenarios and situations that may occur during the report generation process that require proper testing to make sure that everything is working properly. Logan, Collin and Kevin will produce the majority of the implementation and the entire team will work to ensure as many test cases as possible are covered.
-
Test cases completed
What was the outcome?
Screenshots and the excel file that was generated as a result, see comments below for screenshots.