Unit Testing Book
-
Can anyone recommend a good Unit Testing book? I haven't done much Unit Testing. I'm working in C#/WPF. Thanks
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
[Test]
public void UnitTestsArePointless()
{
Assert.True();
}Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a Domain -
[Test]
public void UnitTestsArePointless()
{
Assert.True();
}Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a DomainI agree, but it's being forced on me
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Can anyone recommend a good Unit Testing book? I haven't done much Unit Testing. I'm working in C#/WPF. Thanks
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
From the pen of the author who answered your question first: Unit Testing Succinctly by Marc Clifton[^]
-
[Test]
public void UnitTestsArePointless()
{
Assert.True();
}Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a DomainAbsolutely not, if properly done.
-
Can anyone recommend a good Unit Testing book? I haven't done much Unit Testing. I'm working in C#/WPF. Thanks
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Can anyone recommend a good Unit Testing book? I haven't done much Unit Testing. I'm working in C#/WPF. Thanks
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
"The Art of Unit Testing" by Roy Osherove. Easy to read, covers the subject comprehensively. I believe the Second Edition covers up to date mocking frameworks.
-
Can anyone recommend a good Unit Testing book? I haven't done much Unit Testing. I'm working in C#/WPF. Thanks
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
This gentleman with great C#/.NET video tips https://www.youtube.com/c/Elfocrash/videos[^] released recently Unit Test training. Check his videos and if you like his teaching, you should find a link to his website with his online trainings.
-
Can anyone recommend a good Unit Testing book? I haven't done much Unit Testing. I'm working in C#/WPF. Thanks
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
TDD = Test Driven Development[^]
<>
Please be careful when inserting links: you distorted this one so badly it looked like "hidden link" spam to the automated system. I let it through and have corrected it, but please try to make sure it doesn't happen again as some of our members are rather more "trigger happy" than I am!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
[Test]
public void UnitTestsArePointless()
{
Assert.True();
}Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a DomainSo, for end-to-end testing and feature testing, you know it will make refactoring easier and will protect against regression. But what does a unit test do? I see no immediate benefit, other than bragging rights for high code coverage. What do you think, honestly?
-
So, for end-to-end testing and feature testing, you know it will make refactoring easier and will protect against regression. But what does a unit test do? I see no immediate benefit, other than bragging rights for high code coverage. What do you think, honestly?
It allows you to have a framework to test individual components (down to method level) to ensure that they work as intended. And that means when you make a change later, you can run the same tests again and pick up any inadvertent changes you may have made. I used to do this manually: I created tester projects which allowed me to check the "black box" functionality of my class, controls, and so forth so when I used them in real projects I had a high degree of certainty that they worked, and to test my later fixes to make sure I didn't introduce a bug. I started doing this after a colleague fixed "bug A" for a client, who later found "bug B". She fixed that, and the client found "bug A" was back. Fixed ... hello "bug B"! After about 6 loops of this the client was not impressed at all ... formalized testing would have meant that the tests for both bugs would (or at least should) have been done prior to release, and the customer shouldn't have seen a problem. Units tests formalize that, make it a lot easier to regulate, monitor, and perform. Honestly, if you care about code quality I'd recommend you give them a try. Properly done, they can save a lot of grief.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Can anyone recommend a good Unit Testing book? I haven't done much Unit Testing. I'm working in C#/WPF. Thanks
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
A more funny answer Expert Excuses for Not Writing Unit Tests | Ben E. C. Boyter[^]
-
It allows you to have a framework to test individual components (down to method level) to ensure that they work as intended. And that means when you make a change later, you can run the same tests again and pick up any inadvertent changes you may have made. I used to do this manually: I created tester projects which allowed me to check the "black box" functionality of my class, controls, and so forth so when I used them in real projects I had a high degree of certainty that they worked, and to test my later fixes to make sure I didn't introduce a bug. I started doing this after a colleague fixed "bug A" for a client, who later found "bug B". She fixed that, and the client found "bug A" was back. Fixed ... hello "bug B"! After about 6 loops of this the client was not impressed at all ... formalized testing would have meant that the tests for both bugs would (or at least should) have been done prior to release, and the customer shouldn't have seen a problem. Units tests formalize that, make it a lot easier to regulate, monitor, and perform. Honestly, if you care about code quality I'd recommend you give them a try. Properly done, they can save a lot of grief.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
