[off/2] question about TDD & benchmarking

[Alexander Belchenko]

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

My question something unrelated to bzr itself but it related to the style of bzr
development.

First at all, I want to say 'big thanks' to Martin and others who steadily force
bzr.dev community to use TDD for patches. I see how it helps in providing health
and grow bzr codebase. Now, I'm also try to apply in my daily job elements of
TDD where it possible and useful. And it's produce fantastic results!

I have my personal public project IntelHex (recently I register it on launchpad:
http://launchpad.net/products/intelhex/). It have somewhat little user base,
despite sometimes I receive patches for resolving some issues. I have test suite
for my library and I try to use TDD as well.

Recently I receive patch with performance improvements on large files. Because
bzr use benchmarking for testing such performance improvements, I'd like to add
benchmark test for checking incoming patch.

Can someone give me a hints how to best do this? I'm not study yet benchmark
subsystem of bzr.dev, I'd like to understand basic rules for writing benchmark
tests.

Alexander

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFZsYAzYr338mxwCURAmBhAJ9PT7e6mhuPCw2zLwf6VZDR6nnN3wCfYyH0
cazk60AdmIXGxn0nBdZ95Ok=
=ajsZ
-----END PGP SIGNATURE-----