> Is there an assumption that, before the patch is committed, that the
> tests in the plan will be implemented and passed?
> Are these to be
> automated tests, with the goal that we'll end up with automated
> regression tests for all features?
1. I think we should have a requirement to have all tests that could be
automated be automated and implemented as JUnit tests.
Some tests cannot be automated and may require manual testing or testing
on a large scale, which developers may not have access to.
2. Therefore, we may have to commit before the entire test plan is completed.
But the plan should be developed.
Konstantin
Doug Cutting wrote:
Nigel Daley wrote:
I propose that before we commit issues marked as "New Feature", they
must have:
1. a design doc attachment
2. a test plan attachment
(Templates to be provided for both)
Clarifying test expectations is a good idea in principle. I gather that
what you're after in (1) is an enumeration of new functionality and in
(2) corresponding tests. That sounds reasonable for large new features,
but might be overkill for small features, no?
I'd like to see the templates and some examples. Documents would
preferably be in some open format, like HTML or plain text.
Is there an assumption that, before the patch is committed, that the
tests in the plan will be implemented and passed? Are these to be
automated tests, with the goal that we'll end up with automated
regression tests for all features?
Doug
