Hello,
I smashed up some marketing stuff for contest and been asking around who
is willing to be part of this. Anyone who have more english skills than
me (native Finnish speaking person) should now pop up in and sjape this
fingelska to normal english
I know that RJ has been beating this drum for a while but I wanted to
reinforce the message that everyone should at least try to write a test
at some point. Learning how to use the testing framework in Mixxx has
been incredibly valuable for getting the bugs and regressions out of the
master sync
I can only second that. I made the same experience when writing my
extension to support multiply folders in the library.
Can we also have jenkins build and run the test-suite automatically on
every push to the master branch? That way it would be easier to detect
accidental regressions.
best Max
On Wed, 2013-11-27 at 20:26 +0200, Tuukka Pasanen wrote:
Can we also have jenkins build and run the test-suite automatically on
every push to the master branch? That way it would be easier to detect
accidental regressions.
Hello,
We are using buildbot and it's much more simpler to setup
Typically you'd want to run the test suite against every potential push to
master. And then periodically on master to catch anything that comes in as
a result of merges etc.
I haven't looked at the test suite yet. Will it only run under linux? That
would seem like a supremely sub-optimal solution
Hi Gavin,
The test suite is cross platform (we use gtest/gmock). You can build it
with scons test=1.
Switching away from Jenkins would be a lot of work. We have Windows, Mac
and Linux buildbots building every commit. Running the test suite on every
build is definitely feasible. Last time I
