Protocol: Run Cypress tests for Logs.js

State Tests

Description: Ensures that the component properly traverses through the various states. 

: Logs, Summary Page Rendered and Filters

Currently logs of 9 types populated (Fertilizing, Pest Control, Harvest, Seeding, Field Work, Soil Data, Irrigation, Scouting, Other)

• Procedure

  1. Login and go to Logs page from menu

  2. Check logs are rendered, and then for Activities, Crops and Fields filters check default filter selection and manipulate each one

• Expected Results

  • after navigating to logs page, logs for all items are shown

  • all filters set to general selection as default to show all results ('All', ‘All Crops’, ‘All Fields’) and changes in selection to all three of these changes the logs rendered below accurately

Logs, Date Range on Logs View

• Procedure

  1. navigate to logs page, filter by date range

• Expected Results

  • only those that fit time range are rendered in logs table with all relevant fields still visible

Task Oriented Functional Tests

Description: Ensures that the component is able to handle expected input.

Logs, Edit Date

• Procedure

  1. Select a log, modify the date and return

• Expected Results

  • in table, new date should show with that log

: Logs, Adds Pesticide log - Custom Product

• Procedure

  1. from logs page navigate to add a ‘Pest Control’ log

  2. add custom product

• Expected Results

  • ‘Pest Control’ log form renders and able to click add custom product form and fill with name and save

: Logs, Adds Pesticide log - Target

• Procedure

  1. from logs page navigate to add a ‘Pest Control’ log

  2. add custom product - test target group drop down and fill other category

• Expected Results

  • clicking add target groups, renders Add a Disease page with working drop-down and empty name input

Logs, Add Harvest Log

• Procedure

  1. Add a harvest log - save without selecting crop and then with crop

• Expected Results

  • default for drop-down empty and crop required otherwise error

Logs, Add Seeding Log

• Procedure

  1. Add a seeding log - attempt save without and with crop

• Expected Results

  • default for drop-down empty and crop required otherwise error

Logs, Add Field Work Log

• Procedure

  • Add a Field Work log - attempt save without and with crop

• Expected Results

  • default for drop-down empty and crop required otherwise error

Logs, Add Soil Analysis Log

• Procedure

  • Add a Soil Analysis log

• Expected Results

  • empty fields default, clicking on ‘Show more info’ gives more fields to fill, should get error when not specifying field, depth or texture

Logs, Add Irrigation Log

• Procedure

  • Add a Irrigation log - attempt save without and with crop/type

• Expected Results

  • default for drop-downs and fields are empty, crop and type are required so not having them gives error

Logs, Add Scouting Log

• Procedure

  • Add a Scouting log for field with crops and again for field without

• Expected Results

  • defaults empty, field and type are required so not having them gives error

Logs, Add Other Log

• Procedure

  • Add an Other log for field with crops and again for field without

  • Expected Results

    • defaults empty, field with crops should show crops input, field cannot be empty

Logs, Edit and Delete for all Log types

• Procedure

  1. Edit the details of each log

  2. Delete the log

• Expected Results

  • Changes persist, when deleting confirmation modal shows

Fertilizing log features/cases (changes are coming based on last meeting):

• No field, only product selected

• custom product

• field with crops - crop field appears right now default empty

• many crops and many fields versus fields and no crops versus product and no fields or crops

• if no product specified in all cases error when saving

Logs, Add Fertilizing Logs - Custom Product & Field without crops

• Procedure

  1. from logs page navigate to add a ‘Fertilizing’ log

  2. click add custom product, choose a template product and check values populated - save - check error

  3. fill product name - save

  4. choose field, click drop down to find custom product

• Expected Results

  • all values in custom product should be set to 0 default

  • selecting product template changes all values and error arises if no name specified

  • return to original page after save, then find custom product in drop down and save log

  • this log should now be listed with fields and crops as ‘None’

Logs, Add Fertilizing Logs - Field with crops

• Procedure

  1. from logs page navigate to add a ‘Fertilizing’ log

  2. choose farm with crops, and fill in details

  3. fill product name - save

  4. repeat with multiple crops selected and multiple fields

• Expected Results

  • when selecting field with crops, crop field appears

  • in log- values under field and crop not None - when multiple shows the word Multiple

Test-to-Fail

Description: Tests which should cause errors or not be accepted as input 

Protocol: Perform these tasks on the following site.

Keep this category separate or in the flow above to check is fine?