Refactor the irrigation task architecture LF-2875 - Getting issue details... STATUS
Role: N/A
User preferences:
Values with units are displayed in the user measurement system preference
API: N/A
Dates: N/A
Switching farms:N/A
Input constraints: N/A
Data transformation:
Lists should default to alphabetical sorting
Cascading effects: N/A
Synchronous/ Asynchronous: N/A
External service: N/A
Test Suite
Test Step # | Description | Test Data | Expected Result | Actual Result | Pass/Fail |
1 | While signed on to a farm as FO/FM/EO. Ensure that the default system of measurement for said farm is set to metric and begin and complete the creation of a custom irrigation task. Ensure that all inputs(including optional) have a value, and user the water usage calculator to set estimated water usage | Irrigation task creation succeeds, the user is redirected to the tasks view and a task card for the task exists. During creation irrigation task type drop-down displays the list of irrigation task in alphabetical order and “Other“ option is displayed as per UI requirement | |||
2 | User clicks on the task card for the above task | All details are displayed correctly | |||
3 | Using a DB tool user checks the details of the above irrigation task | Details are persisted correctly as per Jira ticket, base object attributes are implemented and the value is stored based on default unit of measurement | |||
4 | Via UI user changes their system of measurement preference to imperial and navigates to the read only view for the above task | Task details are correct | |||
5 | User creates another irrigation task as in step 1 | Irrigation task creation succeeds, the user is redirected to the tasks view and a task card for the task exists | |||
7 | User repeats step 2 to 4, changing the system of measurement to metric in step 4 | Only one default exists in the location default table. Only one record exists in the irrigation type table | |||
8 |