[Chandler-dev] Testing the RC

[Philippe Bossut]

Hi,

I received some questions privately about how to go about testing and I 
thought the answers could be interesting to everyone. So, here's some of 
those questions and answers, in no particular order:

- Should I write new tests? No, you're not expected to write new tests. 
The objective is to make sure we go through the whole set of tests at 
least once using a Desktop RC and Cosmo 0.7. Note that now that Hub is 
upgraded to the latest and greatest Cosmo 0.7 RC, this makes testing 
interop that much easier.

- Should I overwrite the old status (e.g. some previous "passed version 
xyz")? No, QA would like to keep that for archive. I have to say that, 
for some tables, it makes adding new status a little iffy. Try to use 
common sense (for instance, if "status" and "version" are in 2 different 
columns, just add the new version in the version cell and modify the 
status cell only if the status is different). May be ask Aparna if 
you're ready hesitating too much here.

- Should I do just mine? Not necessarily so doing "yours" is prio 1. You 
can team up with someone else, help out others when done, etc... You're 
considered the reporter though on the plan assigned to you so if you 
have problems going through it, please contact me or Aparna and we'll 
work out a solution.

- How should I log bugs? Some started to title the bugs with "RCx - 
TCxxxx : " as a prefix. This is good as it helps Bug Council and QA to 
pick up on those bugs faster.

Don't hesitate to ask me or Aparna or anyone in the QA team if you have 
question. Your help going through those plans is *very much* appreciated.

Good testing! :)

Cheers,
- Philippe