“This spec is something more than devs, I tell you. It’s the monster. Devs made it, but they can’t control it.” – with apologies to Steinbeck Ahh, factory-forged random values for fields of unique constraint. How thee vex me with thine probabilistic usefulness and definite indeterminacy. Keep thyselves with ephemeral values of algorithmic parameters and [...]
Browsing Posts in Testing
Should it be assertEquals(expected, actual) or assertEquals(actual, expected)? This discussion came about because at the Chicago Code Camp, Jim Suchy from 8th light was demonstrating TDD in JavaScript by building a simple unit testing library. One of the methods he created was the typical assertEquals. In the code on github he had a signature of [...]
My colleague Jay Fields recently blogged about the value of test names. We had a little discussion about it yesterday on IM. Here’s a summary. Josh Graham I feel the test name is important for two reasons: 1) it is intentional programming – a neural pathway is established in your brain as you write the [...]
