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.
- Stack Overflow 3.9k 3.9k 11 gold badge2020 silver badges3333 bronze badges
- Information Security 749 749 44 silver badges66 bronze badges
- Software Engineering 577 577 66 silver badges1515 bronze badges
- English Language & Usage 291 291 11 silver badge44 bronze badges
- English Language Learners 221 221 11 silver badge33 bronze badges
- View network profile
Top network posts
- 68 Is a 6 digit numerical password secure enough for online banking?
- 46 What is the difference between an API and SOA
- 26 Given When Then Testing - Do I NEED a "When"?
- 19 What do you call a person who is always noisy on the Internet?
- 14 cyclomatic complexity = 1 + #if statements?
- 14 Micro-services and data replication
- 13 How do you keep your unit tests working when refactoring?
- View more network posts →