Explore >> Select a destination
|
You are here 
|
tyrrrz.me | ||
| | | | |
nikoheikkila.fi
|
|
| | | | | How can we improve the developer experience in writing tedious browser-based tests? | |
| | | | |
www.jamesshore.com
|
|
| | | | | ||
| | | | |
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 | |
| | | | |
blog.martinig.ch
|
|
| | | Informations and opinions about software architecture, developers on call, holacracy, Scrum, continuous testing, product management, saying thank you, tech leadership, customer journey maps, code reviews, code sharing, good bugs, android testing and open source project management. | ||
