Archives for the 'TDD' Category
Why Typemock-Isolator for TDD?
There is a long discussion in the ALT.NET group about TDD and Typemock, it is very interesting and I suggest that you read the thread.
Benefits of TDD
Although the benefits of using TDD are inconclusive, here are some benefits attributed to using TDD:
Developers write more tests
Tests use the API, so developers can get early feedback on […]
Dependency Injection with TypeMock
The has been some buzz about Dependency Injection lately (here is another thread). But I want to actually show how TDD with TypeMock can lead to a DI solution, and how the tests will step by step naturally lead to the DI solution when the business features require it.
Lets start with a very simple example […]
Handling Support in Agile Teams
As Developer Testing is become mainstream and teams are looking for pragmatic solutions, we are seeing more and more Customers using TypeMock.
Support has always been a top priority here in TypeMock, our mission is to help developers write unit tests, so if they are stuck -we want to help. This has lead to some […]
Mocking Extension Methods
With Orcas and TypeMock 4.1 you can now mock Extension methods, easily.
Suppose we added a new method to int that return the Roman Number equivalent of that number:
public static class Extend
{
public static string RomanNumber(this int number)
{
// do complex logic
return romanString;
}
}
.csharpcode, .csharpcode […]
DotNetRocks Interview
I had a real fun talk with Richard and Carl on DotNetRocks. You can listen to the show here.
The highlight was a grand piano being delivered to Carl during the interview.
Although the show was mainly targeted at Dependency Injections, there are many other design issues that are not required because TypeMock is design agnostic. One is […]
Developers are seeing the value of Unit Testing
This summer has been great for TypeMock. We are showing record growth and have topped our sales and customer base. This is a sign that development groups are seeing the value of unit testing and understanding the need to isolate parts of the code to enable unit testing.
This has of course kept us all very […]
Dependency Injection - Keep your privates to yourself
Jacob Proffitt has hit the nail on the head with his “I do wish that people would admit that DI doesn’t have compelling applicability outside of Unit Testing” post, the discussion continues with Nate Kohari response post and Jacobs counter post. Oren has also joined in with two posts.
Here a some ideas for you to think about.
DI […]
A New Trick
I have read this post Interaction based testing using TypeMock.
This code:
Mock clientMock = MockManager.Mock(typeof (Client));
clientMock.Strict = true;
Client client = new Client();
Is exactly the same as this code:
MockObject<Client> clientMock = MockManager.MockObject<Client>();
Client client = clientMock.Object;
I prefer the latter, the main reason being that using MockObject ensures that the Object is the one being mocked.
Here is an […]
Good Programming is about Balance
This post hits the nail on its head: When good programming practices are just too good.
What struck me … is the ridiculous amount of code required to implement simple things.
I love this paragraph
We all love rules - with them, you don’t have to think much, you just apply what the smart guys think is the […]
Design vs. Process
Oren Eini has posted Tools vs. Design about the Really Simple Dialog post.
It is NOT the design that will give you the freedom to expand and build extendable and maintainable systems. It is impossible to see the future and to implement the best design, that is what YAGNI is about. It is the process that will allow us […]
Subscribe!
RSS 2.0