Skip to content
This repository has been archived by the owner on Mar 16, 2022. It is now read-only.

Create POC for automated visual testing #12

Open
3 of 5 tasks
coenkoopmans opened this issue Nov 26, 2019 · 0 comments
Open
3 of 5 tasks

Create POC for automated visual testing #12

coenkoopmans opened this issue Nov 26, 2019 · 0 comments
Assignees
Labels
prio:high Priority: High type:feature Type: Feature (new distinct functionality)

Comments

@coenkoopmans
Copy link
Contributor

coenkoopmans commented Nov 26, 2019

Description

Research the possibilities for automated visual testing, build a proof of concept, and supply a pull request. Ideally, this solution should conform to the following:

  • Able to run with a package.json script (similar to npm run test) so we can use it with Travis CI.
  • Have some option to automate internet explorer 11 testing, as this is important to the corporate market. (Suggestion: connect to BrowserStack with a webhook via Travis)
  • Compare supplied screenshots of desired output with screenshots that the tool makes on-the-fly to assess the correctness of the result.

Acceptance criteria

  • Research best tool to do automated visual testing with and post a small report of research results as a comment on this issue
  • Test with a simple component, such as button, and prove it works -- both a passing and a failing test
  • Make a package.json command like npm run test or similar to run the test.
  • Add to the Travis YML file and make sure on every build the test gets run on all components
  • Let Travis do an Internet Explorer 11 test on certain conditions -- at least on merges to develop and master, but preferably on every build.
@coenkoopmans coenkoopmans added type:feature Type: Feature (new distinct functionality) prio:high Priority: High labels Nov 26, 2019
@coenkoopmans coenkoopmans added this to the Automated testing milestone Nov 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
prio:high Priority: High type:feature Type: Feature (new distinct functionality)
Projects
None yet
Development

No branches or pull requests

2 participants