I'm a .NET coder working in Brentwood for Burrows
At the moment I'm pretty obsessed with testing - everything about it. I want to find the perfect test - how is it structured; how does it read; how does it link to business requirements; what patterns are used to make the test semantic; what considerations are there to make the test maintainable?
Until you have tested code, it doesn't work. If it is difficult to test code, at best it is unmaintainable. At worst, it is unmaintainable and it doesn't work.
That's why many of the questions I answer here are about Specflow.
In my spare time, I'm into C++ indie games development.
This user hasn’t posted yet.