List of assumptions that the code will not explicitly address/check
E.g. We will assume input is correct (explaining why there is no validation)
Requirements
[ ] 1. List of numbered conditions to be met for the feature
[ ] 2. E.g. Every column/row must display a value, i.e. cannot be empty
[ ] 3. Numbers for reference & checkboxes for progress tracking
Limitations
A list of things this work will specifically not do
E.g. This feature will only handle the most frequent use case X
Affected Components
A tentative list of anticipated repository items that will be changed, labeled
with "add", "delete", or "change". One item per line. (Mostly, this will be a
list of files.)
change: File path or DB table ...
add: Environment variable or server setting
delete: External executable or cron job
DESIGN
Interface Change description
Describe changes to usage. E.g. GUI/command-line changes
Code Change Description
Describe code changes planned for the feature. (Pseudocode encouraged)
Tests
[ ] 1. A description of at least one test for each requirement above.
[ ] 2. E.g. Test for req 2 that there's an exception when display value is ''
[ ] 3. Numbers for reference & checkboxes for progress tracking
FEATURE REQUEST
Inspiration
There are no fcirc calculation tests for multi-tracer/label data
Description
Add tests based on the data in Michael's spreadsheet.
Alternatives
none
Dependencies
none
Comment
none
ISSUE OWNER SECTION
Assumptions
Requirements
Limitations
Affected Components
A tentative list of anticipated repository items that will be changed, labeled with "add", "delete", or "change". One item per line. (Mostly, this will be a list of files.)
DESIGN
Interface Change description
Describe changes to usage. E.g. GUI/command-line changes
Code Change Description
Describe code changes planned for the feature. (Pseudocode encouraged)
Tests