Unit Tests

[Evgeniy Ivanov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andreas Pakulat wrote:
> 
> So I'd like to ask what you all think about the following guidelines:
> 
> 1. If you find a bug and fix it or work on a bugfix for a reported bug,
> write a unit-test for it first.

It's great. I did so during SoC. Many teams do development in such way.

> 2. If there's infrastructure missing to create such unit-tests, lets
> discuss how we can create that infrastructure
> 3. It would be nice if everybody could spare an hour or two of
> development time every other week - or once a month or something and use
> it for test-writing.

4. What about running tests before committing?

> With that I think we might be able to increase the test coverage of our
> code-base quite a bit. Note that not only unit-tests on individual
> classes are important, integration tests could also be useful.

As for me, I will write integration and ui tests for VCS (mostly DVCS)
part after 20 September, when I have some spare time.

- --
Cheers, Evgeniy.
Key fingerprint: F316 B5A1 F6D2 054F CD18 B74A 9540 0ABB 1FE5 67A3

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkjLqHYACgkQlUAKux/lZ6PjAACfYd/OXuRiN/0nAl1w7/HDZvaj
kf4AoKSzq3jYHwDndr5Bkh+QiE2abLtx
=NF6b
-----END PGP SIGNATURE-----