Backlog of removed tests

Registered by Leo Arias on 2014-06-28

List of tests removed during the utopic cycle, and tasks related to reenable them.

Whiteboard

Sometimes we will have to either remove tests or be blocked for a long time. When this happens, QA should be involved in the discussion of what to do, arguing for a test-driven solution.

If we agree to remove the test*, a bug must be reported, triaged, critical, with a person assigned to it, and linked to this blueprint.

The bugs must be tagged qa-removed-test: http://ur1.ca/hmhkr

QA should check the status of the opened bugs regularly.

* If it's possible, prefer to change the test to expect the failure. This way, as soon as the underlying issue is fixed, it will block future landings until it's reenabled.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.