I’ll make this cut and dry: I suggest a standardized testing schema. details: There should be a database of listing a test, and the result of the test. something like below:
blender version| test | tester | result | notes
blender 2.70 |render|user_1 |crash | system specs and file used
there should be one for each little thing you do in blender and a sample file to download and test with.
A whole site for this could be made and users would log in and do checks and sign off on the results, and suggest a test and upload a testing file (preconfigured preferably to avoid long set up times.
all a user would do is get the file and do what the note says then write the result in the site. There would be a form for this which corresponds with the test.> and if a new bug is found, a user can make a user test for someone to repeat uploading the file with instructions.
As blender grows, many non-coders or anyone who wishes to help can do testing and find bugs in a systemic way. I’m glad the bug tracker exists to file after someone accidentally runs into a bug, but as blender grows, there seems to me that some bugs lurk there undiscovered until much later. Also, with the rapid bimonthly releases, this would help find bugs in a systemic way.