Bernd Eilers wrote:
Mathias Bauer wrote:
Hi Thorsten,
[... snip ...]
And also again: let's stop this discussion (and especially allegations
obviously caused by misunderstandings) until we have got information
about what the tests cover exactly and if this is what we want.
Do you think it makes sense to break this "what do they cover?" question
down to source file level, eg. stating exactly which CXX, HXX, java
file, etc. is being covered or do you think more of a functional
coverage description.
To clearify why I am asking such question:
I am still wondering if it could be somehow possible to guess at a good
subset of thoses tests for checking only stuff that has been changed on
the CWS automatically. But (as jogi and others already mentioned a few
times) the type of which those tests are is on the level of system
testing and not on the level of unit testing. For Unit testing there
would automatically be some kind of mapping to source code level. But
well System testing is different. So if we somehow would in accompaning
tooling for applying a subset of tests want to be able to select tests (
and preselect a good choice automatically) I am wondering on to which
level we can get. Should there be only a selection based on applications
eg. writer, calc, draw, chart, ... or do we want and can we provide
more detailed selection? Could this selection be based on
names/descriptions of individual tests? Would we want to preselect eg.
all of the writer tests or can we maybe deselect some writer tests
automatically because we know they do cover areas of code which is not
touched in the CWS?
Ciao,
Mathias
Ciao,
Bernd
Ciao,
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
