Rafaella Braconi wrote:
Hi Alex,


Hi Rafaella,


for the l10n versions, we (Globalization) do perform TCM l10n testing. All results are very transparent and you can see them here: http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_report.cgi?tcm_config=newooo&action=report_list&project_id=23

Yes, I know about this, since I have already done TCM testing before with the francophone n-l group and I knew that you could see the various test cases and results. I have never doubted that the results were available, but my question was more geared to the fact that for languages tested internally by Sun, why do volunteer n-l qa groups do sanity release tests which basically check whether the l10n stuff is correct when that has been done already internally ?


As for the Sanity Check tests, if these are insufficient you are very welcome to contribute to put together a better set of sanity check test cases that better serve your or other purposes. This is also why we migrated to this new TCM, because it give us all the possibility to create test scenarios to be able to sufficiently test the various versions based on time and resources.


Well, the full test case scenario that comes with the automated test tool is fairly complete (although obviously can not cover every circumstance) and of course it takes a long time to carry them out. One thing that is missing is testing of functionality of the Base module. There are some Base case scenarii available in the sanity release tests, but these do not even appear to follow those minimum tests put up by QA from the dba project. It is such inter-project inconsistencies which cause me to ask these questions in the first place. I'm all for creating new test cases, but it would appear to me that some of them already exist elsewhere (we might have had this discussion before ;-))

Anyway, I shall give it a think and see what I can come up with.

Alex

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to