/explore
|
You are here 
|
www.destroyallsoftware.com | ||
| | | | |
marksands.github.io
|
|
| | | | | Black and White When writing unit tests using mocks, it forces the developer into whitebox testing. As the tests are supposed to drive the design, one can ar... | |
| | | | |
www.codesimplicity.com
|
|
| | | | | Much like we gain knowledge about the behavior of the physical universe via the scientific method, we gain knowledge about the behavior of our software via a system of assertion, observation, and experimentation called "testing." There are many things one could desire to know about a software system. It seems that most often we want to know if it actually behaves like we intended it to behave. That is, we wrote some code with a particular intention in mind, does it actually do that when we run it? In a sense, testing software is the reverse of the traditional scientific | |
| | | | |
www.martinfowler.com
|
|
| | | | | Flaky tests can ruin your test suite, so you must quarantine them now. But then go on to solve their non-deterministic behavior | |
| | | | |
blog.martinig.ch
|
|
| | | Architecture is an important asset for good programming and the notion of "pattern" is here to help us apply already trusted code architecture solutions to common problems. Jason McDonald has done a wonderful job to group some of them in a document that should be useful to most software developers. Go to his blog to | ||
