Testing

[y0hami]

Checklist for testing

Key: ⛔️ = Blocked 🌀 = Upcoming ⚡️ = Started ✔️ = Complete

• [ ] Create pages for all components containing all variations 🌀
• [ ] Setup Nightwatch with custom CSS style checks (as discussed in discord) 🌀
• [ ] Setup mocha to test JS (will probably need to change a lot of JS to make this work therefore may happen at later stage)
• [x] Request Open Source access to BrowserStack (Accepted as OS project and now have full access to BrowserStack) ✔️
• [x] Set up linter (eslint) ✔️
• [ ] Setup Travis-CI to run the tests 🌀
• [ ] Setup Travis-CI to build and deploy ⚡️
• [ ] Setup coveralls to show coverage (only when JS is done)

[romaninsh]

Another tool to consider: https://github.com/BBC-News/wraith See also: http://webdriver.io/guide/services/visual-regression.html https://percy.io (TBC) https://www.chromaticqa.com (OK to sponsor)

See also: https://docs.percy.io/docs/travis-ci

[y0hami]

Thanks, I will look into these.

[lubber-de]

I also came across https://codecov.io which seems to integrate seamlessly into gihub (for auto creates PR comments for code coverage) Free for open source

[mvorisek]

Eslint can be added and tested in CI easily, example from atk4/ui repo setup:

https://github.com/atk4/ui/blob/a1a8a2812a1332732d87667a2ff2a7cd780b81ef/js/.eslintrc.js https://github.com/atk4/ui/blob/a1a8a2812a1332732d87667a2ff2a7cd780b81ef/js/package.json#L11 https://github.com/atk4/ui/blob/a1a8a2812a1332732d87667a2ff2a7cd780b81ef/.github/workflows/test-unit.yml#L308