Comments on: A sign of team maturity

By: bogardj

bogardj — Wed, 22 Apr 2009 12:33:29 +0000

@Fen

Nah, I’m celebrating that we don’t celebrate. TOTALLY different

By: Fen

Fen — Wed, 22 Apr 2009 08:35:08 +0000

“And no one is asking to throw a party. In past teams, we would mark milestones, “500 tests, hooray!!”

Erm, thats exactly what you are doing writing posts like this!

By: JJ

JJ — Sat, 18 Apr 2009 13:45:23 +0000

I would like to know how an integration test and how a UI/accpetance test typically looks like in your team? How do you setup, cleanup those tests? Do you use mocks or stubs for those tests? What’s the execution time of your testsuite?

Could you post something about that?

By: bogardj

bogardj — Wed, 15 Apr 2009 03:32:23 +0000

@Tim

What coverage does 2384 unit tests represent and what kind of freedom does it give you?

No idea the coverage. Something like 95-99% on our core domain, maybe 80% on the rest? As far as freedom goes, we have a lot of confidence that we won’t break anything, but we’re looking at adding more integration tests (slow, higher-level) that enable bigger refactorings where we’re not afraid to throw away tests.

Are you integration tests automated? If so, when do they run? If not, when do you run them?

Yes, all the time, locally and on the server.

Howare you doing UI/acceptance tests? Manual? Automated (WatiN/WatiR/etc? Mix?

WatiN, w/ gallio, automated in a cascaded build. A report is generated that the QA guys care about from the results. Devs write the tests, with some fluenty domain-specific interface on top of WatiN.

By: Tim Barcz

Tim Barcz — Tue, 14 Apr 2009 21:02:57 +0000

This is cool….some questions:

What coverage does 2384 unit tests represent and what kind of freedom does it give you?

Are you integration tests automated? If so, when do they run? If not, when do you run them?

Howare you doing UI/acceptance tests? Manual? Automated (WatiN/WatiR/etc? Mix?

By: bogardj

bogardj — Fri, 10 Apr 2009 12:33:13 +0000

@peiklk

Sorry, think I miscommunicated there. The sign of maturity was not the # of tests, but rather no one felt the need to celebrate a certain milestone.

By: bogardj

bogardj — Fri, 10 Apr 2009 11:36:20 +0000

@chadmyers

And you only coded with your thumbs too, right?

@Cohen

Ahhhh….none. We’re using Gallio for our acceptance/UI tests. It allows for parallel execution + test steps for readable reports.

By: peiklk

peiklk — Fri, 10 Apr 2009 03:38:13 +0000

This is only a sign of maturity if you’ve bought into TDD. A quality product is the sign of maturity, not the method that got you there.

By: chadmyers

chadmyers — Thu, 09 Apr 2009 23:06:27 +0000

ONLY 2,384 tests? Back in my day, we had 2,000 tests on the FIRST DAY and that was coding uphill, both ways in the snow.

We had black and amber 8″ CRT monitors and stored our tests on 8 1/2″ floppy disks!

By: Cohen

Cohen — Thu, 09 Apr 2009 23:00:59 +0000

Very nice…
are there any nBehave scenario’s in there?