LF-3362 Test Plan

Owned by Denis Dovganyuk
Jun 26, 2023
3 min read

https://lite-farm.atlassian.net/browse/LF-3362

Area / scope to test

Front end

Back end

Model

Notes

Area / scope to test

Front end

Back end

Model

Notes

Requirement specific constraints

  • Testing as per Jira Ticket

N/A

  • Ensure that in the database all the information is stored correctly

 

Role based constraints

  • As a FO / FM / EO I want to be able to repeat a crop plan so that I can quickly and easily document all my crops

  • Ensure that as a FW I am not able to enter this flow

 

N/A

N/A

Does role determine what a user can see or do? Is this enforced uniformly across the front end and back end?

User preferences constraints

N/A

N/A

N/A

Is this impacted by user or farm preferences such as language, system of measure, certification status?

Numerical input constraints

  • Ensure that Label: “Repeat every” has Value range: 1 - 50

  • Ensure that the: Label and number selector: “After <X> repetitions” has Value range : 1 - 20

N/A

N/A

Do we appropriately handle negative, very small, very large, or 0 as inputs?

Text input constraints

N/A

N/A

N/A

Do we appropriately handle blank, very small, and very large inputs? Is there a strict format (such as email) that must be followed?

Date based constraints

N/A

N/A

N/A

Are there logical restrictions on what dates can be input? Should a use be able to complete something in the future for example.

Date based assumptions

N/A

N/A

N/A

Are we making valid assumptions about what dates should be allowed?

Timezone driven interactions

N/A

N/A

N/A

If timezones play a role in the data, are they being displayed or converted appropriately?

Interaction / transitioning UI based constraints

Per UI, user must…

.. see the following:

  • Title: “Repeat crop plan”

  • Sub-title: “Copy this crop plan and all its tasks according to the following schedule.”

  • Label and datepicker: “Beginning”

    • Default value: Current date

  • Label: “Repeat every”

    • Number selector

      • Default value: 1

      • Value range: 1 - 50

      • Required

    • Unit selector

      • Values: {“week(s)”, “month(s)”, “year(s)”}

      • Default value: “week(s)”

      • Required

  • Label: “Repeat on”

    • Day of week selector

      • Values: Sunday → Saturday (per UI)

      • Single select

      • Default selection is the day of the week of the completed_date from source plan if available, otherwise the due_date from the plan being repeated

      • Required

  • Label: “Finish”

    • Radio buttons

      • Label and number selector: “After <X> repetitions”

        • Default value: 3

        • Value range: 1 - 20

        • Required

      • Label and datepicker: “On”

        • No default value

    • One of the two selections must be made and fully populated

  • Primary button: “Save”

  • Secondary button: “Cancel”

N/A

N/A

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

User Should be able to see the following transitions:

 

… be able to perform the following actions:

N/A

N/A

Is state being preserved appropriately in a flow? If I go back and then forth, is it maintained? Is state invalidated when it should be?

Synchronous / asynchronous constraints

N/A

N/A

N/A

Is the interaction synchronous, asynchronous, or does it support both? Can you simulate both if so?

Time-out / low bandwidth constraints

N/A

N/A

N/A

Does the feature fail gracefully under no bandwidth / low bandwidth environments?

Data transformation correctness

N/A

N/A

N/A

Are values appropriately updated when units change? Is it WYSIWYG?

Outcome correctness

N/A

N/A

N/A

When inputting known inputs with expected outputs - do you get the results you expect? Have you tested several “cases” of this?

Switching farms

N/A

N/A

N/A

Does this feature respond well to switching farms (and returning)?

Notification constraints

N/A

N/A

N/A

Should a notification be marshalled based on this action?

Cascading effects

N/A

N/A

N/A

Are there logical places

Integration constrains

N/A

N/A

N/A

Do we need to ensure state is consistent between LiteFarm and the external service? What failure cases do we need to handle? How do we report back the outcome to the user or external service?

Concurrency

N/A

N/A

N/A

How do changes made to records affect other users on the farm? e.g. What happens when a record is soft deleted while another user is viewing said record?