Open Bug 479720 Opened 13 years ago Updated 2 years ago
Add more automated tests for private browsing mode
We have a couple of tests which were recently added to Litmus. We should check which of these tests could be converted to automated browser chrome tests now. List for "in-limus+ and not in-testsuite+": https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&component=Private+Browsing&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=in-litmus%2B&field0-1-0=flagtypes.name&type0-1-0=notequals&value0-1-0=in-testsuite%2B
I don't think that this bug blocks my mozmill test. Removing from dependency list.
No longer blocks: 479314
Assignee: nobody → ehsan.akhgari
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → Firefox 3.2a1
Ehsan, which of those test we can automate via a browser-chrome test?
Bug 461625 and bug 463177 can potentially get automated tests, I've marked them in-testsuite? and made them block this bug. The following bugs can be potentially tested by MozMill. They are all Mac-specific and happen when no browser window is open: * bug 463582 * bug 473860 * bug 479461 The following bugs can be potentially tested by MozMill if it supports tests across browser sessions. They all require Firefox to be closed and re-opened during the test: * bug 479994 * bug 467565 * bug 482334 * bug 468565 The rest of the bugs in comment 0 had in-testsuite+ as well, and were those where Litmus tests were deemed necessary as well as the automated tests by the QA team.
Whiteboard: [PB-P3] → [meta]
The last mentioned bugs look absolutely perfect to get automated by Mozmill. While checking those Litmus tests I have seen that we got some trouble with testgroup assignments. We will have to fix those first. Even most of the added Litmus tests are on the FFT level. Means we will work on those after we have finished the BFT tests. Ehsan, can we close this bug?
(In reply to comment #4) > Ehsan, can we close this bug? I (or someone else) still need to write a test for bug 463177, so I prefer to keep this open as a reminder thingy for component-wide triages, etc., because otherwise, forgetting about the in-testsuite? flag on bug 463177 is just too easy. By the way, what about the other three bugs, namely the following? * bug 463582 * bug 473860 * bug 479461 Can these also be handled by Mozmill?
No longer depends on: 461625
Yes, those can be handled. But these tests have been put into the FFT suite by Marcia or others. Means we will not be able to automate those tests in the near future.
(In reply to comment #6) > Yes, those can be handled. But these tests have been put into the FFT suite by > Marcia or others. Means we will not be able to automate those tests in the near > future. How come?
Marcia, can you please revise those tests if they are FFT or BFT? Thanks.
Severity: normal → enhancement
Target Milestone: Firefox 3.6a1 → ---
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.