-
I guess we should use a CI service like Travis CI (or something else)
-
GitHub pages
-
There is a great way to automatize unit testing for r-packages which we could try to incorporate
an example is here:
https://github.com/burgerga/mdftracks/blob/master/.travis.yml
dlill updated
5 years ago
-
Repoet har for øyeblikket ingen tester, hvilket gjør det vanskelig å finne ut om koden faktisk vil fungere hvis Finn plutselig finner ut at de skal endre html strukturen.
Dette er et par ting som …
-
We need to set up CI tests as the commit frequency is going to increased.
Following need to be covered:
1. eslint checks
2. react compilation
3. typescript compilation
4. electron-package build…
-
setup continuous integration on windows with appveyor
https://www.appveyor.com/
This build should use conda to fetch dependencies.
-
use https://travis-ci.org to build for Linux and MacOS
use https://www.appveyor.com/ to build for Windows
-
Zaraz po napisaniu testów BE i FE, wypadałoby wdrożyć Continous Integration. Czyli ażeby po dokonaniu merge, jakiś darmowy automat puszczał testy / analizę kodu, i informował, jeśli coś jest nie tak.
…
-
In GitLab by @alexxcons on Mar 21, 2019, 09:48
- switch to github and use Tools from there (Like R.Steinhagen does)
-
Use Travis as the CI framework to check the following:
- Code conventions of code and scripts
- Integration tests