Firefox:2.0.0.3/1.5.0.11:Test Plan

From MozillaWiki
Jump to: navigation, search

Please reference the Target list of Bugs to be fixed for this release -http://wiki.mozilla.org/Firefox:1.5.0.11-2.0.0.3:Test_Plan#Target_Bugs_to_Verify.

Here are the primary focus areas:

  • Sites that use Backbase
    • I have contacted the developer in the bug referenced in the list above to find out which sites we should test to verify this fix. They have hot fixed it on their side, so we will have to clarify which sites we should be testing to verify.
    • From the Backbase Developers:
      • We have just released a new version(3.3.1) of our software incorporating the hotfix. You can use the Backbase Explorer and / or starterkit applications of the 'unpatched' 3.3 version to verify the fix. This version can be downloaded at: http://download.backbase.com/Backbase_Community_Edition_3.3.zip
      • What would also be nice to test is our new version, 3.3.1 to verify if the fix didn't break our fix (or anything else, which i do not expect).

This version can be downloaded at: http://download.backbase.com/Backbase_Community_Edition_3.3.1.zip

  • Password Manager
    • mconnor to provide a more robust set of test cases to run after the PM related fix is checked in. We should run the suite in Litmus and also mine Bugzilla for any other PM test cases that could be beneficial
    • Long term goal is to have a regression suite (either automated or manual) that would be specific to PM.

Responses from Justin Dolske

Q. Is Ria's test case sufficient to verify the bug just running a fresh instance of the nightly?

A. Yes, it should be.

Q: Do we need to test scenarios where we set the passwords in an earlier version of Firefox and then move to the nightly?

A: That's actually the case that triggers the bug. If you start with a fresh profile and Firefox 2.0.0.2+, you shouldn't see the bug at all.

Q: What are the implications (if any) of the name change that was made to the signons.txt file in relation to testing this bug?

A: The change from signons.txt to signons2.txt was made in bug 360493.

The browser should migrate from the old file to the new file automatically, the first time you run a post-360493 build. Assuming that works as designed, the only footnote that comes to mind is that switching back to an older build will result in the profile containing both signons.txt and signons2.txt. [specifically, when you run the older browser you won't see any of the migrated logins, and any logins added with the older browser will not be seen by the newer browser].

Q: I assume we should test with both a new profile and an existing profile. I imagine most users are likely using existing profiles.

A: Yeah, for complete coverage the two cases [migrating an existing set of logins, and creating a new set of logins] should each be tested.

I'm writing a set of automated tests (Mochitest) as part of trunk work, but the test for this specific bug won't be integrated before 2.0.0.3 ships. If you need to do testing beyond Ria's testcase, I can expedite finishing the test for this bug and make it available to you.

Justin

  • Rendering Problems for tfoot
    • Investigate whether reftests need to be run here
    • This bug does have two test cases we should be able to run for verification
  • Automatic client certificate authentification
    • Request made in the bug to find out any specific areas we should focus on during our testing
  • Windows Vista fallout
    • Make sure nothing evil happens with Windows Vista due to the shim. We will test thoroughly, and run our Vista specific test suite in Litmus to catch any possible regressions.
Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox:2.0.0.3/1.5.0.11:Test_Plan&oldid=51374"