Calligra/autobuild: Difference between revisions

From KDE Community Wiki
 
(8 intermediate revisions by 2 users not shown)
Line 19: Line 19:


http://my.cdash.org/index.php?project=Calligra
http://my.cdash.org/index.php?project=Calligra
CDash can eat files like:
http://cyrille.diwi.org/tmp/calligra/Test.xml
The scripts used for running the autobuild are available here:
http://quickgit.kde.org/?p=scratch%2Fberger%2Fcalligra-buildbot.git&a=summary


== Unittests ==
== Unittests ==
Usage: make test
Outputdirectory: ${BUILD_DIR}/Testing/Temporary/
Files:
* CTestCheckpoint.txt 
* CTestCostData.txt 
* LastTest.log: full log including debug output
* LastTestsFailed.log: list of tests that failed




== Benchmarks ==
== Benchmarks ==
Usage: make benchmark
Output: only on stdout, no files
For running benchmarks, see:
http://labs.qt.nokia.com/2009/11/05/analyzing-benchmark-results-with-bm/
Results:
http://benchmarks.calligra-suite.org/
The benchmarks are run nightly, only the benchmarks that are in the directory listed in the following script are runned:
http://quickgit.kde.org/?p=scratch%2Fberger%2Fcalligra-buildbot.git&a=blob&f=run-benchmarks.sh


== CSTester ==
== CSTester ==
Line 36: Line 69:


== validateODF.py ==
== validateODF.py ==
== OfficeShots ==
Install the factory for officeshots so officeshots can always run against the latest calligra.
http://www.officeshots.org/
http://code.officeshots.org/trac/officeshots

Latest revision as of 12:29, 8 February 2011

Autobuild

The goal of the autobuilder is to build Calligra continuously and run tests after Calligra has built. There are four kinds of tests currently:

  • unittests (written using the QTest framework)
  • benchmarks (also written using the QTest framework)
  • roundtrip testing of the kofficetests document repository using massTester (TO BE MIGRATED)
  • rendering testing of the kofficetests repository using CSTester (TODO)

Nightly packages for Linux can be delivered using the OpenSUSE build service (TODO)

Builds are run on:

cruncher1.kogmbh.net

a machine donated by KO GmbH. This machine is in certain cases also available to Calligra developers who want to test the behaviour of code on a machine with 12 cores (6 real with hyperthreading)

Results are available on:

http://my.cdash.org/index.php?project=Calligra

CDash can eat files like:

http://cyrille.diwi.org/tmp/calligra/Test.xml

The scripts used for running the autobuild are available here:

http://quickgit.kde.org/?p=scratch%2Fberger%2Fcalligra-buildbot.git&a=summary

Unittests

Usage: make test Outputdirectory: ${BUILD_DIR}/Testing/Temporary/ Files:

  • CTestCheckpoint.txt
  • CTestCostData.txt
  • LastTest.log: full log including debug output
  • LastTestsFailed.log: list of tests that failed


Benchmarks

Usage: make benchmark Output: only on stdout, no files


For running benchmarks, see:

http://labs.qt.nokia.com/2009/11/05/analyzing-benchmark-results-with-bm/

Results:

http://benchmarks.calligra-suite.org/

The benchmarks are run nightly, only the benchmarks that are in the directory listed in the following script are runned:

http://quickgit.kde.org/?p=scratch%2Fberger%2Fcalligra-buildbot.git&a=blob&f=run-benchmarks.sh

CSTester

check_koffice_install.sh

check_msword_import.sh

massTester.pl

profileOfficeFileLoading.py

validateODF.py

OfficeShots

Install the factory for officeshots so officeshots can always run against the latest calligra.

http://www.officeshots.org/ http://code.officeshots.org/trac/officeshots