LF-2952 Test plan

User is able to complete creating field work task flow without selecting field work https://lite-farm.atlassian.net/browse/LF-2952

Area / scope to test	Front end	Back end	Model	Notes

Area / scope to test	Front end	Back end	Model	Notes
Requirement specific constraints	Test as per Jira ticket	N/A	N/A
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				Is this impacted by user or farm preferences such as language, system of measure, certification status?
Farm-level defaults / preferences
Numerical input constraints				Do we appropriately handle negative, very small, very large, or 0 as inputs?
Text input constraints				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				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				Are we making valid assumptions about what dates should be allowed?
Timezone driven interactions				If timezones play a role in the data, are they being displayed or converted appropriately?
Interaction / transitioning UI based constraints				Is the UI transitioning appropriately? Is the API providing da
Flow based constraints				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				Is the interaction synchronous, asynchronous, or does it support both? Can you simulate both if so?
Time-out / low bandwidth constrains				Does the feature fail gracefully under no bandwidth / low bandwidth environments?
Data transformation correctness				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	Complete flow to ensure field work task creation still functions			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?