#2059: Failing tests in tg2 trunk
------------------------+---------------------------------------------------
Reporter: faide | Owner: faide
Type: defect | Status: new
Priority: high | Milestone: 2.0b1
Component: TurboGears | Version: trunk
Severity: major | Keywords: test auth
------------------------+---------------------------------------------------
http://paste.turbogears.org/paste/17832
The recent changes in the auth API have not been repercuted in the
tests...
This close to a release (and already in a beta cycle) we should take care
to have tests always working, or at least have tickets to track failing
tests.
This is an important issue because when doing a release, the manager will
rely on tests to know if nothing is broken. And if the tests bork-out in
all directions then the release manager will be in a bad situation where
he will need to fix all the tests before being able to continue his
release work... and believe me, a release is a lot of work. And it becomes
even more work when you know you're out of beta and are releasing a final
stable version.
--
Ticket URL: <http://trac.turbogears.org/ticket/2059>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
