Opened 5 years ago

Last modified 3 years ago

#6008 enhancement new

Use pyunit's todo functionality when available (i.e. Python > 2.6)

Reported by: Itamar Turner-Trauring Owned by:
Priority: normal Milestone:
Component: trial Keywords:
Cc: Thijs Triemstra Branch:


On Python 2.7 and 3.3, Python's unittest supports todos. When trial has a test marked as todo, it should use that support if possible so that non-trial runners can still deal with todos.

Python 3.3 needs this since otherwise expected failures are treated as real failures.

Change History (4)

comment:1 Changed 5 years ago by Thijs Triemstra

Cc: Thijs Triemstra added
Component: coretrial

comment:2 Changed 3 years ago by Adi Roiban

Do we want to use todos ?

As understood from mainlinglist discussions todo tests should not be commited.

I suggest to close this ticket and stop using todos :)

just fix the code, or file a ticket if something is not fixed yet.

comment:3 Changed 3 years ago by Jean-Paul Calderone

"trial" and "Twisted's test suite" are different things. A decision not to have tests marked as "todo" in Twisted's test suite is not a decision not to support the "todo" feature at all in trial.

comment:4 Changed 3 years ago by Adi Roiban

True. My bad. Sorry for the noise. Thanks for the info.

Note: See TracTickets for help on using tickets.