Sometimes, users will install the latest version of your software, try it out for a bit, then reinstall the earlier version. You should test that, especially if there are changes to the way the program stores information.
This is a testing approach I often forget. I saw that a developer detected a downgrade problem with a change he was working on, and that reminded me to work on remembering this particular technique.
. . . too well.
Based on what you’ve told us so far, we’re playing this track because it features pop rock qualities, repetitive melodic phrasing, prominent use of synth and many other similarities identified in the music genome project
I grabbed 6 simple testcases from bugzilla and old email, and “ported” then to jsUnit. On Firefox 1.5.0.4 on my intel mac, 5 tests pass and one fails. I included the failing test so that folks can see what the failure message looks like in jsUnit.
Yes, some of these tests are simplistic. They don’t have a lot of what I call “power”. But I can make up for lack of individual power through volume.
Feel free to run jsUnit-based tests and look at the source in this temporary home for these tests.
And look here (and in the mozilla.dev.quality newsgroup) for pointers to how-to docs and tracking bugs as I work to integrate this system into our build infrastructure.
We picked up Della from CCI HQ yesterday for our 1-week trial. If all goes well, she’ll be joining us as a permanent addition to the family.
