Hi Mechtilde,
Mechtilde wrote:
Hello
If I read the mails from Sophie and Thosten I ask me, what should we
test from 3rd of August to 16th of August.
As French also German is a stable language.
As I wrote to Sophie. I cannot tell you or decide, what the L10N teams
have to do. My opinion is to minimize the testing on L10N related issues
for stable languages and check the new translation by testing new
features.
What can we tell to the national communities to test the developer
builds eg to find release critical bugs or to exclude them.
Work with the developer snapshots is one point. Then you will find many
problems, which you do not find at testing. ;-)
I think the tests at this time are a good possibility to find also bugs
in the functionallity.
The time of the sanity tests is too late.
I don't think so.
Do we need the specifications to test functionallity?
When a specification for the feature exists, than also a test case
specification exist (not for all, but in most cases). See the 2.3
feature list.
I think it is very important to test the functionallity also on
different plattforms.
You are right, it is important to check some functionality on different
platforms. But it doesn't make sense for all of it. For example I do not
know any issue in Numbering on Writer, which occur only on one platform.
But it make sense to check Impress in presentation mode on different
platform, because of different window handling of the systems.
Thorsten Ziehm schrieb:
Hi Sophie,
For general functionality tests it should be
enough, when one run the test case - because most feature are not
language depended.
What do you mean here? Should we do TCM-Test or not?
Yes.
Translation is here a different part. Checking the
translation in new features, does not need test cases for functionality.
It is only needed to know, where the changes were done in UI.
Where we get this information compressed for testing?
The Office is too complex. I cannot tell you, where changes were made.
This is a big problem, but I do not know how this can be solved.
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
