Slidedeck from Usergroup - Testing with VS2010 - A Bugs Life

4 comments:

Juri Strumpflohner said...

Really nice presentation, like it :)

Question: If you're writing integration tests, say you'd like to test whether your DB connection works or that your DAO retrieves some object appropriately (for verifying the logic in the stored proc for instance). First, are you writing them also as automated "unit test" (although they are integration tests) within VS? I suppose so. But then, how do you organize your tests between real unit tests and integration tests which - as you mentioned - may fail of course while unit tests shouldn't ever.
I really don't like the TestView in VS, where you see all of the tests. What I'd like is to see them separately, having the possibility of grouping integration & unit test (kind of TestSuites from jUnit).

Peter Gfader said...

Thanks
We are putting Integration tests and Unit tests in different projects.
And we have a naming convention:
- name of class with Integration tests: CUD.IntegrationTests
- name of class with Unit tests: CUD.UnitTests

This is important for gated check ins, where you can decide which test you want to run on a gated checkin...

>>I really don't like the The TestView in VS, where you see all of the tests. What I'd like is to see them separately, having the possibility of grouping integration & unit test (kind of TestSuites from jUnit).

Yes me neither. But with good naming of test methods its ok...

Juri Strumpflohner said...

I was thinking of such an approach too, but I had still some hope that you're going to show some hidden VS feature ;)

So I'll go for that approach, thx a lot.

Manfred said...

Very, very nice presentation!
This test lab and the GUI testing possibilities of VS2010 seem to be really interesting and usefull.
Unfortunately at work we get only the Visual Studio 2010 Professional :-(
It would be nice to have the possibility to buy this test lab separately...

Post a Comment

Latest Posts

Popular Posts