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

Revisit our component testing strategy #2502

Open
3 of 5 tasks
Tracked by #1389
vanitabarrett opened this issue Jan 17, 2022 · 0 comments
Open
3 of 5 tasks
Tracked by #1389

Revisit our component testing strategy #2502

vanitabarrett opened this issue Jan 17, 2022 · 0 comments
Labels
epic Epics are used in planning project boards to group related stories javascript

Comments

@vanitabarrett
Copy link
Contributor

vanitabarrett commented Jan 17, 2022

What

There are various issues with our tests, coupled together with the fact that we don't currently have any JavaScript unit tests.

There may be some 'quick wins' we can do to give us more confidence. Other things, like adding unit tests, may be dependant (or at least made easier) by revisiting our tooling choices generally.

Why

Our current test setup doesn't give us a lot of confidence when making changes to our JavaScript code. If we're going to be making changes to the way our JavaScript is structured and de-duplicating code, we may want to put better testing in place first so we're more confident about these changes.

Who needs to work on this

Developers

Who needs to review this

Developers

Done when

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Epics are used in planning project boards to group related stories javascript
Projects
None yet
Development

No branches or pull requests

1 participant