LF-3378 Test Plan

Owned by Denis Dovganyuk
Last updated: Jun 27, 2023
3 min read

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

 

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

  • Ensure that FO / FM / EO are able to view this modal

  • Ensure that the FW is not able to get access to this model

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

N/A

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

  • Ensure that the field beginning date should be in the date format for the users localization

  • Ensure that the field finishing date should be in the date format for the users localization

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: info icon and “Confirming repeating crop plan”

    • Label and text: “Beginning”

      • Value: Populated from the the value selected for the beginning date

      • Must include the day of the week

      • Should be in the date format for the users localization

    • Label and text: “This plan will repeat”

      • Value: “every <X> <periods> on <day_of_week>”

      • <X>, <periods>, and <day_of_week> should all be populated from the values selected previously

    • Label and text: “Finishing ”

      • Value:

        • If “On” had been selected, display “on <date_to_finish>.”

          • <date_to_finish> should include the day of the week

          • <date_to_finish> should be in the date format for the users localization

        • If “After” had been selected “after <Y> repetitions.”

          • <Y> should be bolded

      • Label and text: “This will create”

        • Value: “<X> new crop plans and <Y> new tasks”

        • <X> and <Y> should be bolded

    • Primary button: “Confirm”

    • Secondary button: “Go back”

N/A

N/A

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

User should be able to see following transitions:

  • None

User Should be able to perform the following actions:

  • Click “Save” to …

    • If generated from “Repeat crop plan

  • Click “Go back” to return to the previous screen

  • Click anywhere outside the modal to persist state and return to where the modal was generated from

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?