Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing refactor - Autosuggest #134

Open
AmarJagpal-ONS opened this issue Jul 25, 2024 · 0 comments · May be fixed by ONSdigital/design-system#3327
Open

Testing refactor - Autosuggest #134

AmarJagpal-ONS opened this issue Jul 25, 2024 · 0 comments · May be fixed by ONSdigital/design-system#3327

Comments

@AmarJagpal-ONS
Copy link

AmarJagpal-ONS commented Jul 25, 2024

As Software Engineer
I want update the testing structure of the components
So that it is standardised across all Design System and improves automatisation of testing

Description
As an outcome of the recent spike #59 it was identified that testing of all our components need to be refactored. This will enable standardisation and increase automation of testing.

Test refactoring instructions have been documented in Confluence

For the reference, please use the example of the test refactor for the Header component

Acceptance Criteria
Testing refactor needs to meet the following criteria:

  • Clearly structured.
  • Follows naming conventions.
  • Consistent.
  • Concise.
  • Suited to our codebase.
  • Compatible with existing testing framework.

Linked User stories/epics
See all the links provided in the description

Technical details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants