Open Bug 1400847 Opened 4 years ago Updated 3 years ago
[META] Migrate old console frontend tests to the new one
We have a high number of tests in the old console and we should make sure they pass with the new frontend as well. That being said, it might occurs that a test is irrelevant (because it is already tested in the new frontend or in reps, because it tests the variableView or because we do things in a different way). This bug should track this "triaging" work so we can then later file individual actionable bugs to migrate test to the new frontend. The process should be: - Open the test file - Check that it is still relevant in the new frontend context - If it is, comment these lines in head.js : http://searchfox.org/mozilla-central/rev/05c4c3bc0cfb9b0fc66bdfc8c47cac674e45f151/devtools/client/webconsole/test/head.js#298-301 , and run the test. - If it passes, put it in a list somewhere (in this bug ?) of safe tests to copy to the new frontend folder (we'll then have a bug to copy all those safe tests). - If it fails, create a bug that would say "Copy XXX_test to the new frontend folder" Let's use https://docs.google.com/spreadsheets/d/11RBIwROFsdPzEXkt94Bzk-y49KxRu08dwC6hvA-MOGA/edit#gid=0 to do the triaging work. There are filter views for irrelevant, failing and passing tests, so we can then extract those lists. At the moment I see 210 tests to triage, we could split that in buckets of 10 that people would do from time to time during the day so it's not to painful to go through. If we are 3 doing this, that mean 70 bugs each, 7 buckets. I'd say we could go over this in a week or two by doing 1 to 2 bucket a day.
Priority: -- → P2
Summary: [META] Migrate old console frontend to the new one → [META] Migrate old console frontend tests to the new one
Bugs for individual tests can be filed using https://bugzilla.mozilla.org/enter_bug.cgi?format=__default__&product=Firefox&blocked=1400847&component=Developer%20Tools%3A%20Console (set the component and block this bug)
Whiteboard: [console-html][triage] → [console-html]
You need to log in before you can comment on or make changes to this bug.