Last weekend I went to CITCON (Continuous Integration and Testing Conference) which was held in Jasper Hotel, Melbourne.
Some thoughts about what we can do with the things I heard at this conference:
Get testers and product managers involved in writing acceptation tests for stories:
- By using something like Fit and Fitnesse.
- Write test cases for stories in a human readable format and execute them automatically.
- Make the automated integration tests more accessible by improving reporting so it is easier to read what the tests are really doing.
- Separate tests “what” and fixtures “how”.
About unit tests I heard some interesting statements:
- Fast running tests are unit tests. Slow running tests are integration tests.
- If you can’t run 100 test per second you’re doing it wrong.
- Unit test don’t touch the filesystem and have stuff like databases mocked out.
A lot of projects suffer from problems with performance testing.
- not doing any
- deploy systems a production environment where load is 50 to 500 times higher then tested.
Measure test coverage to find out:
- How confident we should really feel about having automated tests.
- How we can reduce duplication of work between automated tests and QA testing.
- Measure complexity as part of the automated build to find out where refactoring would help to increase test coverage.
Record and playback on protocol level is a common practice for performance testing and reproducing production problems. I’ve been doing this kind of stuff recently
I can recommend going there next year. This conference is free.
blog comments powered by
![[Valid Atom 1.0]](images/valid-atom.png "Validate my Atom 1.0 feed")
© Eddy Pronk