Mochawesome reporting

[thekiiingbob]

Summary

Use the cypress module to configure cypress and run tests programatically
Integrate mochawesome reports (pretty HTML reports, with integrated screenshots)

To run, just do npm run test, afterwards you should have a mochawesome-report directory. If you open up mochawesome.html in your browser, you can view the report.

Ticket Link

JIRA

[saturninoabril]

This is great!

Could you please check once again the generated link for screenshot? It's broken on me when I ran it. There were / that's missing in the link.

[saturninoabril]

Please change filename to e2e/run_tests.js

[thekiiingbob]

This is great!

Could you please check once again the generated link for screenshot? It's broken on me when I ran it. There were / that's missing in the link.

Ah! Good catch! I was stripping out / from the final filename, I just needed to strip it from the parent names.

[thekiiingbob]

@saturninoabril @prapti Everything should be up to date now!

[prapti]

Should I be looking for the mochawesome-report folder inside e2e/results?
I am however, getting the following error while trying to run the test. Am I missing anything?

Error: Command failed: /bin/sh -c npm run test:ci
at makeError (/Users/prapti/go/src/github.com/mattermost/mattermost-webapp/e2e/node_modules/start-server-and-test/node_modules/execa/index.js:174:9)
at /Users/prapti/go/src/github.com/mattermost/mattermost-webapp/e2e/node_modules/start-server-and-test/node_modules/execa/index.js:278:16
at processTicksAndRejections (internal/process/task_queues.js:85:5) {
code: 1,
stdout: null,
stderr: null,
failed: true,
signal: null,
cmd: '/bin/sh -c npm run test:ci',
timedOut: false,
killed: false
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ test: start-test start:webhook 3000 test:ci
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

[saturninoabril]

Looks good to me, except for non-blocking comments/suggestion.

Probably will not affect others in general, especially those who's not running the full test in local but when they do then run style check (npm run check), too many errors will come out that's hard to pinpoint that it's from the generated app.js of mochawesome report. I suggest to add --ignore-pattern e2e/results to check script of main package.json.

[saturninoabril]

Let's clean this up with the only folders to ignore.

[thekiiingbob]

@saturninoabril Pushed up changes to remove those unneeded ignores. Added .eslintignore file to handle ignoring e2e/results in linting.