.. -*- coding: utf-8 -*-

Ticket #19766 Old and closed branch are still included in report view
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.000
:state: rejected

Comments ::

  On 2010/01/20 10:44 - sthenault wrote :
  this is the user's responsibility to cleanup no more desired execution reports.

Ticket #20419 Add Quantitative data in test report
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:state: open

This might be an entity with the following signature: QuantitativeValue(key,
value, type, result_value_of<CheckResult, CheckExecution, ...>)

Ticket #19767 Checker Result summary
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:state: open

We currently only have two level of data about a Checker execution : The result
and the full log.We May add a small summary text to improve reports usability
(grade for Pylint, number of successful test for pyunit etc)

Ticket #20006 Enhance log coloring
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.250
:state: resolved

Ticket #22646 [pyunit] Skipped test should issue a warning level message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.200
:state: open

Skipped notification of pyunit are in DEBUG level message for now. They should
be promoted to WARNING level (or at least INFO)

Ticket #19768 More meaninfull checker names in report
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:state: open

Comments ::

  On 2010/05/11 07:57 - sthenault wrote :
  what do you propose?

Ticket #19162 unreadable logs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 1.000
:state: resolved

currently it's hard to read preprocessors/logs file. The most notable pb is that
often the information that help to find why something failed is in a separated
DEBUG message above the ERROR message.

IMO:

* ERROR messages due to command failures should hold the debug information *
when a message do not apply to a particular path in the source, use the path
information to hold the command name * (moved to #20006) to colorize logs
according to severity * (moved to #20005)each checker should be responsible to
tell why it failed (and add this information to the failure notification mail)

Comments ::

  On 2009/12/03 14:43 - sthenault wrote :
  1.5.0 includes most of this but:
  
  * stylesheet should be completed
  * last item still to implemented
  * each checker messages handling should be reviewed

Ticket #19728 apycot bot state
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.100
:state: resolved

The apycot bot state view must show all tests running, including tests running
on another instance that the current one.

For now, this view show only this instance tests and one can think the bot is
not doing anything whereas he is busy.

Ticket #20406 rss feed notification of status changes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 1.500
:state: resolved

Ticket #20293 when displaying messages, exclude debug
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 1.000
:state: resolved

for example on http://www.cubicweb.org/testexecution/678486?tab=pyunit only the
failures could be displayed with a top-right menu to print a menu with the
option "filter", similarly to what is done for the tickets of a project in
cubicweb-forge.

Ticket #19763 Add report view to forge startup page (if apycot is available)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:state: open

Ticket #19765 Execution may have no branch
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.300
:state: resolved

Branch value is not enforced and TestExecution may have not branch data.
Moreover old TestExecution may lack this data too. TestExecution with branch
None cripple most report view.

Ticket #20289 Add a performance checker
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:state: open

For a reliable performance check, (.i.e. comparable to previous runs) we should
have only the performance check running. Also, we should store someway the
performances and add a nice view.

Comments ::

  On 2010/02/11 09:37 - pydavid wrote :
  We should split this ticket

Ticket #19798 Filter branch by branch in reports view
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 1.000
:state: resolved

Ticket #2803 enhance top apycot report
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.500
:state: open

pour le rapport contest ajouter une colonne avec: une flèche verte vers le haut
si le projet vient de gagner des places. une flèche rouge vers le bas si le
projet vient d'en perdre, un signe "= X jour(s)" si le projet n'a pas changé de
rang depuis X jour(s).

Comments ::

  On 2008/12/23 14:31 - sthenault wrote :
  faudrait commencer par faire revivre ce rapport...