Jump to: navigation, search


205 bytes removed, 11:08, 23 July 2006
point3, use a separate, dedicated profile
# Take a guess when the bug might have broken -- any guess will do for a start, so just use your instincts.
# Download and install a build from that date from or from if you need to go back even further. I recommend installing the build in a directory named something like Firefox-03-11-06 so that you can go back to it during this test.
# Run the test build. Either make sure you have no other Firefox windows openUse a separate dedicated profile, or that you have MOZ_NO_REMOTE=1. If you don't, you will actually be running the version of Firefox already in memory. This mistake is common. To ensure you are running the build you think that you are, go to Help without any extensions installed and start with -> Aboutprofilemanager.
# Test the build and write down the results. It's common to get confused since you are testing for the absence of a bug, so good notes are important. If the bug occurs, then you know you will have to search back further in time. Otherwise you will need to search forward in time. The optimal algorithm is to test the date exactly between the last known date when the bug didn't occur and the last known date when the bug did occur. Keep dividing by two and you'll find the day.
# In the end, make sure that the bug is marked with the keyword "regression", and add a very clear comment something like: "March 19, 2006 trunk: works, March 20, 2006 trunk: broken". When you have found a regression window within a day, then the actual hour the product was built becomes important. You can give this information with the [ build ID]. Another option is to look at the time when the "firefox.exe" or "thunderbird.exe" was last modified. Then take a larger margin (by the hour) of that time.

Navigation menu