----- Original Message -----
* Internal Test Suite
+ Unit Tests
- Some folks generally think that writing unit tests *after*
the actual code is written is more or less useless because
the test may match broken code. Although I understand possible
issues it's far superb to what we have now. Also considering
ABRT being still more or less rewritten to enhance it's design,
it's quite a good chance we do it the right way.
We'd like to see unit tests in framework of your choice for
both core and plugins.
+ Regression Tests
- Having wide range of regression tests in sources needs some
time, it may be a pain and it may make you feel like you are
coding tests and not developing the useful code instead.
However, in my opinion, it saves you the time you have to
invest in fixing regressions.
Also with regression tests you may slightly less fear
breakage and anger from users. You may also view it as a step
further in providing more stable code; for example code review
was a positive step in that direction.
What's your position on unit and regression tests? What's the
current situation?
I'd love to see unit and regression tests coming. When doing QE
on GCC I found it really useful and felt much more confident
when I saw no regressions were found by the test suite.
Michal