Closed gidili closed 4 years ago
@rgerkin possible, this task will cover mainly the gluing between github and continous deployment so that automatically travis (or alternative) will trigger a new build of the code with the new changes and then will trigger the automated testing on top of the new code pushed in the branch. If we want to rely on travis (or alternative) builds history to keep track of these issues we can but #398 seems more something that can be achieved with google analytics. Adding this to the agenda to discuss it.
@rgerkin Yeah I don't think it's a duplicate - this one is, like @ddelpiano says, about making it possible for tests to run as part of the build, so not even implementing the actual tests, just the infrastructure work to "integrate", while #398 it's about logging user activity and errors as they occur.
Duplicate of #398?