elexis-eu
Set up (minimal) testing for core functionalities
We should have automated tests for core functionalities (to deal with things like #132 #147 https://github.com/elexis-eu/lexonomy/commit/0e0d68b8dd106e7539617a9be8bd0419fc0f784e#r34259618 - and avoid regressions on them). These functionalities are (or will be) split between Python and Node.js - until, eventually (#128), Node.js will be dropped and the only JS will be in interface/browser/client parts.
If we go forward with this, we should find/agree on one test suite per environment
- [ ] Python
- [ ] Browser/Client-JS (maybe later...)
- [ ] Node.js (likely never...)
@gareins @jan-niestadt @michmech @mjakubicek @rambousek
I would wait with this until we drop NodeJS, which should be quite soon (Adam Rambousek is working on that).
ok. out of personal preference, i would have started with python anyway. we don't have testing baked into bottle (like flask) but they give some pointers:
- http://bottlepy.org/docs/dev/recipes.html#functional-testing-bottle-applications
- https://docs.python.org/3/library/unittest.html