Hi, Ilyse Kazar schrieb:
As for this whole automated testing thing. Are not some tests to just be done manually and the results recorded manually? For instance, the test case that I was assigned (for base) looked like it was for localization and there were questions such as "was the wizard translated correctly". How would an automated test do that?
That's the reason why we have different ways to test. In theory, the testtool would be able to check, if a dialog is translated correctly. But it needs to know, what the correct translation would be. This definition could be wrong (or would be the same as it is used in OOo itself).
(BTW: almost all of the test cases in tcm are localization specific. But we are trying to get more localization indipendend tests in).
Also, please clue me in, I tried to find a definition of "shakedown" ... is that the same as an automated test?
The terms "shakedown" (or "Smoke-") Tests have been used for a set of manual tests, that should proof the release readiness of OOo. They were quite similar to the test cases in TCM but we never had a "portal" for those cases (and they have not been updated to OOo 2.0).
André --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
