CI to Stable - procedures and testing

Owned by Klaas Andries de Graaf
Last updated: Dec 18, 2016 by Abi James
1 min read

Try to have bug-fixes on stable.slidewiki.org in ˜2 weeks

Only front-end fixes (slidewiki-platform) - more safe


Check → are fixes stand-alone (i.e. they do not have dependencies on new work in services/in data model/ on other fixes)?

Integrate in Agile proces/sprints

→ see New sprint design


Testing

We have testing tasks (used during last update of testing)

Automate!

→ Unit testing!

→ e.g. firefox selenium (automated test scripts in browser) - headless browser for server? → should be available on Travis - https://docs.travis-ci.com/user/gui-and-headless-browsers/

→ Automatic Accessibility testing (Abi James -automatted OS Accessibility tool poss options...  https://github.com/pa11y/pa11y built to work with Travis but needs testing; aXe from Deque labs https://github.com/dequelabs good tests but may need some work to integrate into TravisCI but already integrated with some other testing environments)



Abi James Benjamin Wulff Ali Khalili Roy Meissner Kurt Junghanns Huw Fryer