¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Testdrivendevelopment
  2. Topics

[TDD] Getting back into C# testing

 

Sort of related - wrt documenting microservices, how do you feel about having a small number of (likely system) tests like this?:


On 6/09/2014 3:42 AM, "Alan Baljeu alanbaljeu@... [testdrivendevelopment]" <testdrivendevelopment@...> wrote:

?

I've been away from serious OOP programming for a while, working in Prolog, etc. ?So now I'm back, using VS2013, and starting development with a large CAD API. ?

My TDD experience has followed the old data-oriented style, testing whether a function causes the right kinds of objects to be produced, rather than testing that it invokes the right methods. ?(It makes more sense to me, that my concern is to construct the correct and very visible model, and not how that model was constructed.)

So now, given this brand-new API (which I know is well made and stable), is it a good idea to create my own classes to wrap access to the API, or is it better just to access the API directly?

Following the TDD mantra of test-first, I'm thinking about:
{
? setup the test scenario.
? do something interesting.
? check what happened.
}

I write the above in natural fashion, and then build classes and methods to match that fashion, and link those to the underlying API.

Does this all make sense? ?Shall I use the built-in test framework? ?Are there any valued innovations in the last years about software development?
?
Alan Baljeu
 

I'm in favour of tests like that.

?
Alan Baljeu

From: "Ben Biddington ben.biddington@... [testdrivendevelopment]"
To: testdrivendevelopment@...
Sent: Friday, September 5, 2014 5:54 PM
Subject: Re: [TDD] Getting back into C# testing

?
Sort of related - wrt documenting microservices, how do you feel about having a small number of (likely system) tests like this?:



On 6/09/2014 3:42 AM, "Alan Baljeu alanbaljeu@... [testdrivendevelopment]" <testdrivendevelopment@...> wrote:
?
I've been away from serious OOP programming for a while, working in Prolog, etc. ?So now I'm back, using VS2013, and starting development with a large CAD API. ?

My TDD experience has followed the old data-oriented style, testing whether a function causes the right kinds of objects to be produced, rather than testing that it invokes the right methods. ?(It makes more sense to me, that my concern is to construct the correct and very visible model, and not how that model was constructed.)

So now, given this brand-new API (which I know is well made and stable), is it a good idea to create my own classes to wrap access to the API, or is it better just to access the API directly?

Following the TDD mantra of test-first, I'm thinking about:
{
? setup the test scenario.
? do something interesting.
? check what happened.
}

I write the above in natural fashion, and then build classes and methods to match that fashion, and link those to the underlying API.

Does this all make sense? ?Shall I use the built-in test framework? ?Are there any valued innovations in the last years about software development?
?
Alan Baljeu

1 - 2 of 2