LF-2656 Test plan

Requirement specific constraints

If no “Valid until” date is provided or “this document does not expire” is checked, document does not expire.

If no “Valid until” date is provided or “this document does not expire is checked, set “this document doesn’t expire” to true when POSTing the document.

If no “Valid until” date is provided or “this document does not expire is checked, set “no expiration” to true in the database.

Role based constraints

N/A

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

All copy is in users preferred language

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

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

Documents with expiry date are set as expired after said date

Expiry date is set for documents with expiry date

Valid_until has a value only for documents with expiry date

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

Timezone driven interactions

Documents are moved into to the archived section appropriately

N/A

N/A

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

Interaction / transitioning UI based constraints

New documents with no valid until date or “this document does not expire” checked appear in the valid section

N/A

N/A

Is the UI transitioning appropriately? Is the API providing da

Flow based constraints

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

New documents with no valid until date or “this document does not expire” checked appear in the valid section

Is the data persisted as expected post-transformation?

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

Outcome correctness

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

Switching farms

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

Notification constraints

Should a notification be marshalled based on this action?

Cascading effects

Valid documents that is documents that have no expiry date that were created with a certification export period and documents that are valid for said period all appear in the export

Are there logical places

Integration constrains

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?