Explore >> Select a destination
|
You are here 
|
eregon.me | ||
| | | | |
jamesmead.org
|
|
| | | | | Expanded notes on this major version bump of the Ruby library for mocking & stubbing | |
| | | | |
blog.jayfields.com
|
|
| | | | | You have methods you want to handle dynamically without the pain of debugging method_missing. class Decorator def initialize ( subject )... | |
| | | | |
noelrappin.com
|
|
| | | | | I just write here | |
| | | | |
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 | ||
