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

Set up javascript, vue and UI testing #123

Open
Tracked by #120
MrNaif2018 opened this issue Oct 3, 2021 · 0 comments
Open
Tracked by #120

Set up javascript, vue and UI testing #123

MrNaif2018 opened this issue Oct 3, 2021 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@MrNaif2018
Copy link
Member

Currently we only run eslint linting by yarn lint:
https://github.com/bitcartcc/bitcart-admin/blob/6a3e10391ef22dead01e0b9a65a2dba393ccdc4c/package.json#L12
To get to 1.0 release, we need a stable test suite to test that UI doesn't break without checking it manually (for example when upgrading one image input library it got broken and got into release, so I had to fix it later manually)
I am not an expert in javascript apps (and vue apps) testing, so any help welcome
We need a few categories of tests set up:

  1. Unit tests. I heard that jest is often used for this. We may test some utility functions and so on. For code coverage codecov is to be used of course.
  2. Integration tests: something that may be tested on a real API. This could either use our demo merchants api instance (https://api.bitcartcc.com), or better, it would start the most recent changes from bitcart master repo in docker
  3. End to end tests and snapshot testing. This type of testing is the most important one. Something like selenium could be used, or better-suiting libraries for that in js world. It would test that UI works as expected.
    This would then be added to our CI. If you need help in adding it, you can just implement the tests and I can add that to CI.
    First of all we need to scaffold the initial infrastructure for that, then add those test types and start adding new tests. This issue can yield a lot of pull requests because there are a lot of tests to add or set up.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant