Move Bugs windmill tests to BugsWindmillLayer
Bug #430699 reported by
Björn Tillenius
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Deryck Hodge |
Bug Description
Bug 429348 makes it possible to run Windmill tests with bin/test. For this to work, all the Windmill tests have to be in a layer that extends BaseWindmillLayer.
Related branches
lp://qastaging/~deryck/launchpad/windmill-tests-for-malone
- Eleanor Berger (community): Approve (code)
-
Diff: 1932 lines (+874/-877)10 files modifiedlib/lp/bugs/windmill/tests/test_bug_also_affects_new_upstream.py (+49/-37)
lib/lp/bugs/windmill/tests/test_bug_inline_subscriber.py (+235/-248)
lib/lp/bugs/windmill/tests/test_bug_me_too.py (+98/-90)
lib/lp/bugs/windmill/tests/test_bug_privacy_settings.py (+142/-123)
lib/lp/bugs/windmill/tests/test_bug_tags_entry.py (+7/-5)
lib/lp/bugs/windmill/tests/test_bugs/__init__.py (+0/-85)
lib/lp/bugs/windmill/tests/test_filebug_dupe_finder.py (+106/-96)
lib/lp/bugs/windmill/tests/test_filebug_extra_options.py (+44/-28)
lib/lp/bugs/windmill/tests/test_mark_duplicate.py (+10/-5)
lib/lp/bugs/windmill/tests/test_official_bug_tags_management.py (+183/-160)
Changed in malone: | |
importance: | Undecided → High |
milestone: | none → 3.1.10 |
Changed in malone: | |
milestone: | 3.1.10 → none |
Changed in malone: | |
assignee: | nobody → Deryck Hodge (deryck) |
Changed in malone: | |
status: | Triaged → In Progress |
milestone: | none → 3.1.10 |
Changed in malone: | |
milestone: | 3.1.10 → 3.1.11 |
Changed in malone: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
On Sat, Oct 03, 2009 at 12:45:38AM -0000, Deryck Hodge wrote:
> ** Changed in: malone
> Milestone: 3.1.10 => None
To reiterate the previous mail; this bug should definitely be fixed for
3.1.10. Test failures should get really high priority. Unless you have
critical bugs to fix, you should get these test failures fixed as
soon as possible. More importantly, if this isn't fixed before the
upgrade of YUI, we might end up breaking Bugs without knowing about it.
The upgrade of YUI should ideally happen before the LAZR-JS sprint, so
please get this bug fixed this week.
This is also blocking me from landing a LAZR-JS branch of mine. I guess
I could land it anyway, but ideally I want to make sure I don't break
anything.
-- /launchpad. net/~bjornt
Björn Tillenius | https:/