For those interested in doing testing for Inkscape (including our new
Win32 testers), here's some tips!
First, keep an eye out for any requests from the Release Wardens (Jon
Cruz and Aaron Spike), or anyone working on patches for your
platform/distro. Hopefully they can pop in with some more specific
directions for testing on those platforms.
Second, please make sure to test installation and startup of 0.44pre2
and any additional pre-releases. I think most of you are already doing
this. Our goal should be to have installation to your platform work as
good and smoothly as any other professional application for your
Third, go through the bug tracker looking for bugs with subject lines
mentioning your platform (i.e. "[Win32]", "[OSX]", etc. See if you can
replicate the bug, and if so, add a comment to the bug indicating you
can or cannot do so. This is helpful on several counts. First, it
verifies the bug is still not fixed. Second, it indicates you will be
able to test out fixes that others come up with. And third, it shows
the scope of the issue; if no one other than the reporter is seeing the
issue, it might end up being some local quirk on their system, whereas
if a lot of people can replicate it, then that will mean it's a more
important thing to fix.
Fourth, at least a couple users ought to go through all the items in the
Release Notes, and check that they work according to how the Release
Notes say they do. This takes some time (especially this release), but
has a nifty side effect: You gain much wider expertise in the program
than you would normally (I've found this particularly valuable when
helping users post-release, since I'm at least briefly acquainted with
all the new functionality we're advertising.) It's worth it to have at
least one user from each platform do this, because sometimes there are
features which are broken only on one platform; the sooner these can be
identified, the better chance they have of getting fixed.
Fifth, select one feature from the Release Notes, and really bang HARD
on it. Play with ALL the options, settings, etc. the feature allows.
Try putting in invalid data (where strings are to be input, try with no
string, or paste in a huge amount of text, or try some non-ASCII text.
You get the idea.) Try using the feature in unusual (even crazy) ways,
or in combination with other new features (each new feature may have
been tested well, but it's possible no one has tested them together
before.) Look for and report a) crashes/lockups, b) document
corruption, c) warning messages printed to the console, d) extremely
bad, unexpected behavior. Repeat for other features as time permits.
Since there's several Win32 testers now, it'd be sensible to report here
what feature(s) you plan to bang on, so others can avoid duplicating