For the benefit of the list! https://github.com/huggle/huggle3-qt-lx/commit/5605080314444c860e942a1df36cb85f140043d1
https://travis-ci.org/huggle/huggle3-qt-lx/builds Addshore On 9 November 2013 00:33, addshorewiki <addshorew...@gmail.com> wrote: > Petr > > I'll try to setup Travis tests to run on every github commit on Monday. :) > That seems like the best solution as the repo is on github! > > Also this way you'll be able to see the status of the tests for all > branches and pull requests etc :-) > > Addshore > On 8 Nov 2013 17:22, "Petr Bena" <benap...@gmail.com> wrote: > >> to explain how QT unit testing works a bit more, it's basically >> another QT project that includes the source code from master branch >> and produces a binary file (called tst_testmain) which can be executed >> with various parameters and executes the unit tests defined in its >> source code, for example: >> >> petanb@petrbena:~/Public/huggle3-qt-lx/huggle/tests/test$ ./tst_testmain >> ********* Start testing of HuggleTest ********* >> Config: Using QTest library 4.8.6, Qt 4.8.6 >> PASS : HuggleTest::initTestCase() >> PASS : HuggleTest::testCaseWikiUserCheckIP() >> PASS : HuggleTest::cleanupTestCase() >> Totals: 3 passed, 0 failed, 0 skipped >> ********* Finished testing of HuggleTest ********* >> >> >> This thing of course can be ran by some 3rd tool (such as jenkins) >> which run it automatically when new commit arrives to repository and >> evaluates the results... >> >> On Fri, Nov 8, 2013 at 5:16 PM, Petr Bena <benap...@gmail.com> wrote: >> > Yes, I made a simple unit test suite for huggle, which uses internal >> > QT unit test system, basically what I need to do is >> > >> > * periodically pull the latest version of source code from master branch >> > * build the test suite (if build is failed submit this information) >> > * execute test suite (qt unit test system can even produce results as >> > XML, or other commonly used formats) >> > * evaluate the results and if there are any failures submit this >> > information somewhere >> > >> > the "somewhere" for submitting should be preferable shell script I can >> > write, which would send the data directly to our irc channel, so that >> > we can be notified immediately if any commit breaks any test. >> > >> > I don't really know if this is something what Jenkins can be used for, >> > but I was told by Coren that running this task on Tools project is not >> > a right thing to do. So I am basically looking for another project >> > where we could run these unit tests. (It requires g++, make and full >> > qt4 dev sdk to be installed on server where unit tests are about to be >> > ran) >> > >> > On Fri, Nov 8, 2013 at 3:40 PM, Antoine Musso <hashar+...@free.fr> >> wrote: >> >> Le 08/11/13 11:21, Petr Bena a écrit : >> >>> would anyone experienced (like hashar) be interested in setup of >> >>> jekins on wikimedia labs so that we can get a unit test environment >> >>> available to all devs for any projects, written in languages like: >> >>> >> >>> * C >> >>> * C++ >> >>> * Python >> >>> * PHP >> >> >> >> If the project is hosted on Wikimedia Gerrit installation, you can >> >> surely get jobs added on the existing installation. The jobs >> >> configuration are handled using Jenkins Job Builder and trigger by >> Zuul: >> >> >> >> integration/jenkins-jobs-builder-config.git >> >> integration/zuul-config.git >> >> >> >> Do you have any use case in mind? >> >> >> >> -- >> >> Antoine "hashar" Musso >> >> >> >> >> >> _______________________________________________ >> >> Wikitech-l mailing list >> >> Wikitech-l@lists.wikimedia.org >> >> https://lists.wikimedia.org/mailman/listinfo/wikitech-l >> >> _______________________________________________ >> Wikitech-l mailing list >> Wikitech-l@lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
