On Wed, Jan 16, 2013 at 3:25 PM, Quim Gil qgil@wikimedia.org wrote:
All the better if there is certain correlation between testing and bugs activities, but no problem if there is none.
I'm glad you mentioned this, it's something I'd like to bring up with
Andre and Valerie. Note that much of the backlog for automated tests is the result of fixed BZ tickets http://www.mediawiki.org/wiki/Qa/test_backlog. Fixed bugs are great candidates for regression tests because a) what broke once is more likely to break again and b) an issue fixed may indicate more issues in nearby areas of the feature. Our UploadWizard test is a great example of a single test catching multiple issues in the same area over time.
So a mechanism by which fixed browser bugs become entered in the automated browser test backlog would be a fine thing.
Compared to the current situation, this wheel looks powerful and at the
same time relatively easy to set up. There will plenty of things to improve and fine tune, but probably none of them will require to stop the wheel.
What do you think?
How would this affect the notion of Groups? http://www.mediawiki.org/wiki/Groups/Proposals