Page Comparison

Acceptance criteria

For Design system the main output is Components' library. To define if developed component is aligned with initial design and requirements, for each story set of Acceptance criteria is submitted. It includes the following levels:

...

There is also a set of criteria that applies across all stories and can therefore be applied to each story, but not repeated within each story. Relevant DoD criteria are listed below:

1. Code is peer-reviewed;

2. Code is checked-in;

3. Design & Code Component’s code is merged to master branch;

4. Component meets WCAG 2.1 AA;Security standards have been met;

5. Coding standards have been met;

6. Performance standards have been met;

7. Code is deployed to test environment;

8. HTML is validated with Nu HTML Checker;

9. Code/feature passes regression testing;

10. Code/feature passes smoke testingComponent meets acceptance criteria;

11. Visual regression testing passed (Percy when available);

12. Cross-browser testing is passed (link to the support page (needs to be approved first));

13. Code Component interface is documented in Storybook;

14. UAT and BUAT are is passed;

15. Documentation BUAT is updatedpassed;Feature is signed

16. off by stakeholdersBasic overview documentation is published to Storybook;

17. Feature Component is released to AWS Code Artifact.