SEP #81: Extend test_run to export in a xUnit format

Sylvestre Ledru sylvestre.ledru at scilab-enterprises.com
Wed Jul 11 17:58:30 CEST 2012


Hi


      Abstract

This SEP details the introduction of a fourth argument for test_run.


      Rationale

Continous integration systems are becoming more and more popular. Among
the most famous software in this domain, Jenkins (formelly called
Hudson) has now become the reference.

As part of the quality effort on Scilab, Scilab Enterprises has setup an
instance of Jenkins available:

http://build.scilab.org/

In this context, it is important that the Scilab test suite could be
integrated in Jenkins in order to let Jenkins managing new test failing,
the amount of tests, etc.


This SEP proposes to introduce a fourth argument to the test_run
function. This string argument, it would define the path to an XML file
containing the result of the execution.

The selected format is called xUnit. Already normalized, it is used by
Junit, PHPUnit, and many other.

This will allow a simple integration of Scilab results into third party
applications.


      *Syntax*

status = test_run(module,test_name,options, XMLFile)


      Example Usage

status = test_run("core",[],[], TMPDIR+/"results-test-core.xml")



Thanks for the comments,
Sylvestre

-- 
Sylvestre Ledru
Operations Manager / Community Manager
-----------------------------------------------------------
Scilab Enterprises
143bis rue Yves Le Coz - 78000 Versailles, France
http://www.scilab-enterprises.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/dev/attachments/20120711/0257c272/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SEP_081_test_run_xunit.pdf
Type: application/pdf
Size: 275721 bytes
Desc: not available
URL: <https://lists.scilab.org/pipermail/dev/attachments/20120711/0257c272/attachment.pdf>


More information about the dev mailing list