As a developer I need improved acceptance criteria and functional requirements

[raftmsohani]

Description: During working on #2757, a table was developed that represented detailed acceptance criteria for the issue in question (see tables in #2757). Each row in the table shows one acceptance criteria either directly or indirectly. Although the table helped developing the logic, qasp revealed one of the ACs (row 3) was missed.

This ticket is created to improve listed ACs by adding associated test cases to each AC such that dev team can easily test each AC and further improve both reliability and development speed.

Acceptance Criteria: Create a list of functional outcomes that must be achieved to complete this issue

• [ ] Outcome 1
• [ ] Outcome 2
• [ ] Outcome 3
• [ ] Testing Checklist has been run and all tests pass
• [ ] README is updated, if necessary

Tasks: Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue

• [ ] Task 1
• [ ] Task 2
• [ ] Task 3
• [ ] Run Testing Checklist and confirm all tests pass

Notes: Add additional useful information, such as related issues and functionality that isn't covered by this specific issue, and other considerations that will be helpful for anyone reading this

• Note 1
• Note 2
• Note 3

Supporting Documentation: Please include any relevant log snippets/files/screen shots

• Doc 1
• Doc 2

Open Questions: Please include any questions or decisions that must be made before beginning work or to confidently call this issue complete

• Can we agree on some standard language like the cucumber/gherkin format?
• Scenario: Sunday isn't Friday Given today is Sunday When I ask whether it's Friday yet Then I should be told "Nope"
• do we want this ticket to make a datafile generator based on above and/or incorporating our unit test factories?

[andrew-jameson]

Implementing this ticket would vastly improve the test code related to #2970 for example.