Add direct tests for all the Bug(Task|Subscription|Etc.) handlers
Bug #253241 reported by
Graham Binns
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Invalid
|
Low
|
Gavin Panella | ||
Bug Description
At the moment the event handlers for events relating to bug activity are untested, except indirectly. It would be nice to have a set of unit tests that we could easily extend for new event handlers (in the same way as we do for new BugTrackers in database/
| Changed in malone: | |
| status: | New → Confirmed |
| Changed in malone: | |
| importance: | Undecided → High |
| milestone: | none → 2.2.3 |
| status: | Confirmed → Triaged |
| Changed in malone: | |
| assignee: | nobody → allenap |
| status: | Triaged → In Progress |
| Changed in malone: | |
| status: | In Progress → Triaged |
Revision history for this message
| Björn Tillenius (bjornt) wrote | #1 |
| Changed in malone: | |
| importance: | High → Low |
| tags: | removed: story-refactor-activity-log-api |
Revision history for this message
| Björn Tillenius (bjornt) wrote | #2 |
| Changed in malone: | |
| milestone: | 2.2.3 → none |
| status: | Triaged → Invalid |
To post a comment you must log in.
We have something like this in TestBugChanges. When everything related to bug activity is tested in this class (or a similar one), we can mark this bug as fixed. It's not something we have to do this cycle, though.