#15 in Software testing books
Use arrows to jump to the previous/next product
Reddit mentions of Testing with F#
Sentiment score: 1
Reddit mentions: 1
We found 1 Reddit mentions of Testing with F#. Here are the top ones.
or
- Ingredients: edible potato starch, sugar, eggs, wheat flour, honey, maltose
- Storage methods: avoid the sunshines
- Shelf life: 270 days will be subject to packing instruction;NOTE: the date on the package is the manufacture date, instead of expire date. we guarantee what we sell are the latest product.
- weight: 210g
- taste: slight sweet with honey
Features:
Specs:
| Release date | February 2015 |
Can you give me some example business requirements you'd like to test, and I'll start writing a book on how to test them? :)
Joking, but joking seriously. I'd like to prove my mastery as an engineer, and one way I can think of doing that is to write a book with 50+ reviews averaging 4.5* or greater.
My favorite book on testing is actually for F#, not C#: Testing with F# by Michael Lundin - half the book has nothing to do with F# and is full of pragmatic advice.
I _cannot_ recommend The Art Of Unit Testing. Here is just one reason why: In the appendix, the author writes:
>A.3.8 The AutoFixture Helper API
>
>The AutoFixture helper API is not an assertion API. AutoFixture is designed to make it easier to create objects under test that you don't care about. For example, you need some number or some string. Think of it as a smart factory that can inject objects and input values into your test.
>
>I've looked at using it, and the thing I find most appealing about it is the ability to create an instance of the class under test without knowing what its constructor signature looks like, which can make my test more maintainable over time. Still, that's not enough reason for me to use it, because I can simply do that with a small factory method in my tests.
>
>Also, it scares me a bit to inject random values into my tests, because it makes me run a different test each time I run it. It also complicates my asserts, because then I have to calculate that my expected output must be based on the random injected parameters, which may lead to repeating production code logic in my tests.
This is simply horrid advice, based on a complete non-understanding of what AutoFixture does. You cannot simply isolate your constructor signature with a small factory method in your tests, because then you're just re-writing what AutoFixture does for you, in a brittle way.
Just my opinion.