Versions Compared

Old Version 2

changes.mady.by.user Mwayanjana Bolokonya (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Mwayanjana Bolokonya (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Jira Legacy
serverSystem JIRA
serverId815f41e5-e5fb-3402-8587-82eccc3ffab0
keyLF-3067

We shouldn’t have situations where the beta server doesn’t successfully deploy, but the export server does.

Area / scope to test

Front end

Back end

Model

Notes

Requirement specific constraints

  • Ensure that when deployment of the beta server fails, deployment of the export server also fails

  • Ensure that when the beta server is deployed the export server is also deployed

 

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?

Locale based constraints

 

 

 

Things like date format, and number format for phone numbers and currency inputs

User preferences constraints

 

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 appro