Why testing?

Rubyripper has grown quite a lot since it's first introduction. If you have followed the recent releases though, it seems like a regular thing that something is broken. That is a pity. It sure would help if the application gets some testing before a new release is made.

How to join?

Two weeks before a new release, I'll send a mail to the rubyripper release mailing list. So to join, please subscribe to this mailing list: http://groups.google.com/group/rubyripper-release (low traffic).

You will be asked to:

• get latest Git commit
• make proper bug reports when you encounter a defect. That means plenty of details so it can be reproduced.

Test scenarios

Of course you're free to test any setting you like. But some scenario's are more likely to break than others. Feel free to add more, it's a wiki after all. If you need editing rights, please contact me.

Freedb testing:

• various artist disc -> editing, undo various artist, redo various artist
• a disc with multiple hits on freedb

Rip testing:

• single file rip
• rip a second disc after the first is finished
• rip a disc that needs correction

Install testing:

• does it still install and work properly thereafter?

Output testing

• are all tracks of all codecs there?
• are all tags still correctly?
• are the files conform to the filenaming scheme?

When going into testing stage you will be informed which parts need extra attention.