beat.editor issueshttps://gitlab.idiap.ch/beat/beat.editor/-/issues2018-09-13T16:58:13Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/95Add E2E tests (to the CI)2018-09-13T16:58:13ZJaden DIEFENBAUGHAdd E2E tests (to the CI)They're definitely working locally using Selenium & things, but getting it to run on the CI will be a bit of a pain since I'm halfway across the world from the network/machines. Steps:
- [ ] Clone `beat.tutorial.prefix` and use the pref...They're definitely working locally using Selenium & things, but getting it to run on the CI will be a bit of a pain since I'm halfway across the world from the network/machines. Steps:
- [ ] Clone `beat.tutorial.prefix` and use the prefix folder for the tests
- [ ] Figure out how to run the beat.editor REST server in the testing environment
- [ ] Figure out how to expose the `geckodriver` executable (different for Mac & Linux!) and add it to the $PATHJS & Python Testinghttps://gitlab.idiap.ch/beat/beat.editor/-/issues/94Add flask (& nose?) tests2018-09-21T19:19:04ZJaden DIEFENBAUGHAdd flask (& nose?) testsVia nose if possible
Also will need to mock a BEAT prefix, use beat.examplesVia nose if possible
Also will need to mock a BEAT prefix, use beat.examplesJS & Python Testinghttps://gitlab.idiap.ch/beat/beat.editor/-/issues/119Convert tutorial to tests2018-12-19T19:02:44ZJaden DIEFENBAUGHConvert tutorial to testsWould be great
Basically makes the Iris LDA, Iris Means, Iris Advanced w/ preprocessorWould be great
Basically makes the Iris LDA, Iris Means, Iris Advanced w/ preprocessorJS & Python Testinghttps://gitlab.idiap.ch/beat/beat.editor/-/issues/38fix database creation test2018-08-09T18:04:41ZJaden DIEFENBAUGHfix database creation testJS & Python Testinghttps://gitlab.idiap.ch/beat/beat.editor/-/issues/39fix tc tests with the web worker2018-12-19T19:02:44ZJaden DIEFENBAUGHfix tc tests with the web workerCurrent testing utilities don't like webworker scripts, even though my tests are running in real browsers.
The issue might be mocha or enzyme or karmaCurrent testing utilities don't like webworker scripts, even though my tests are running in real browsers.
The issue might be mocha or enzyme or karmaJS & Python Testinghttps://gitlab.idiap.ch/beat/beat.editor/-/issues/87Re-enable chrome headless testing support once chrome >55 comes out2018-12-19T19:36:13ZJaden DIEFENBAUGHRe-enable chrome headless testing support once chrome >55 comes outThere's a bug about "lost UI shared context" with chrome/chromium headless that'll probably be solved in the next version. For now just use FF for testing since I haven't ever noticed any test results differences between the two browsers.There's a bug about "lost UI shared context" with chrome/chromium headless that'll probably be solved in the next version. For now just use FF for testing since I haven't ever noticed any test results differences between the two browsers.JS & Python Testing