Edgewall Software
Modify

Opened 11 years ago

Last modified 11 years ago

#819 new defect

Bitten doesn't report anything to master in case of unittest results parsing error

Reported by: mikhael@… Owned by:
Priority: minor Milestone: 0.7
Component: Build slave Version: dev
Keywords: Cc: tony@…
Operating System: Linux

Description

We are using Bitten result for a "Build" (Success/Failure?) to determine, if we can deploy the application.

In case of parsing exception for unittest XML file, "test" step is completely missing from "Build Status" page and also doesn't affect the result. The worse case, that we a getting "Success" when tests are not passed correctly.

I'm attaching the patch that always report status of unittest and report failure in case of parsing error.

Not sure, if it is complete or conforms with the roadmap. If yes, could you please include it into upstream? Our build recipe is looks like:

<build xmlns:python="http://bitten.edgewall.org/tools/python"
       xmlns:svn="http://bitten.edgewall.org/tools/svn"
       xmlns:sh="http://bitten.edgewall.org/tools/sh"
       xmlns:php="http://bitten.edgewall.org/tools/php">
  <step id="checkout" description="Checkout source from repository">
    <svn:checkout url="svn://example.com/"
        path="${path}" revision="${revision}"
        username="bitten-slave" password="*****" />
  </step>
  <step id="build" description="Compile any extension modules">
    <python:distutils command="build"/>
  </step>
  <step id="test" description="Run unit tests">
    <python:distutils command="unittest" options="
    --xml-output test-results.xml
    --coverage-summary test-coverage.txt
    --coverage-dir coverage
    --coverage-method coverage" />
    <python:unittest file="test-results.xml"/>
    <python:coverage summary="test-coverage.txt"
        coverdir="coverage"
        include="*" exclude="*/test/*" />
  </step>
</build>

Attachments (1)

report_always.patch (1.1 KB) - added by mikhael@… 11 years ago.

Download all attachments as: .zip

Change History (2)

Changed 11 years ago by mikhael@…

comment:1 Changed 11 years ago by Tony Meyer <tony@…>

  • Cc tony@… added

Add Comment

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.