beat.editor issueshttps://gitlab.idiap.ch/beat/beat.editor/-/issues2018-09-21T19:19:04Zhttps://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/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/38fix database creation test2018-08-09T18:04:41ZJaden DIEFENBAUGHfix database creation testJS & Python Testing