LF-2997 Test plan

Owned by Mwayanjana Bolokonya (Unlicensed)
Last updated: May 31, 2023 by Denis Dovganyuk
3 min read

Use Pill component in AbandonTask https://lite-farm.atlassian.net/browse/LF-2997

Area / scope to test

Front end

Back end

Model

Notes

Area / scope to test

Front end

Back end

Model

Notes

Requirement specific constraints

  • New UI elements as per Jira ticket

  • Cascading effects

N/A

N/A

 

Role based constraints

  • Ensure that only FM / EO / FO can enter the abanon task flow

Only assignee or FM/EO/FO can post to this endpoint

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

  • Ensure that all copies are in the users prefered languages

  • Ensure that certification status of the farm doesn’t matter

N/A

N/A

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

Farm-level defaults / preferences

N/A

N/A

N/A

 

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

  • Ensure that the user can’t select “The original due date” if the original date is in the future .

  • Ensure that the user is not able to select any future date when he clicks on the “Another date”

  • Ensure that the user is able to select any date in the Past when he clicks on the “Another Date”

  • Ensure that in the Postman the user is not able to PATCH this request if the date of abandonment is somewhere in the future.

  • Ensure that the data is correctly stored, once the user completes the abandonment flow.

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

  • The “original due date” radio has the original due date in the pill next to the radio , it can’t be selected ( should be greyed ) if the “original due date “ is in the future

  • The “today” radio has the current date in the pill next to it

  • In the “another date” the user is able to select any date in the past or current date.

  • If original due date is selected the abandonment date or if the original due date is in the future the error should be displayed

  • Ensure that the data is stored correctly in the database

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

Timezone driven interactions

  • Ensure that the original due date and today date are correct to the user

 

  • Ensure that Abandon date is persisted correctly

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

Interaction / transitioning UI based constraints

  • If “original due date” or “today” are selected the date pill is also selected

  • if “another date” is selected Label: “Which date?” and Input: a standard date picker are displayed AND focus automatically shifts to the input

N/A

N/A

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

N/A

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 constrains

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

  • Ensure that the correct notification is displayed once the user abandons the task

N/A

N/A

Should a notification be marshalled based on this action?

Cascading effects

  • Ensure that the user is not able to edit any info after the completion of the abandonment flow

N/A

N/A

Are there logical places

Integration constrains

  • Ensure that if in the farm there is more than one user both users should see that the task has been abandoned, with the same abandoned date

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?