What is your plan for being a better developer next year? What's the technique that will repay your efforts many fold? Testing - automated test to be specific. There are all types of automated testing. The agile mind set thinks of testing first, not in a reactive manner, but as a preventative and design effort.
"For three years, The Container Store has been using application performance management (APM) technology from AppDynamics to locate bugs in the website, target them immediately and fix them.From CNBC's article: Don't let software bugs ruin Christmas by Ari Levy
Sometimes there's a slowdown in a particular region. Other times it's from a certain database and often from a single line of code. Just this year, the Container Store upped its contract with AppDynamics, buying more software so the company can test new features before deploying them and minimize the number of live fixes necessary.
"We said we want to be more proactive instead of reactive," said A.J. Azzarello, a quality assurance engineer at The Container Store in Dallas. "We can catch errors and slow response times in test prior to production so they never impact our customers."
You might enjoy watching David Evans presentation Turning Tests into (Living) Documentation. In this 20 min. video he should be able to teach you some very important concepts of BDD.
One Artifact: 3 roles - Specification, Test, Documentation; resulting in more value, and requiring collective ownership.
Charictistic of a good artifact: Title - just a few words that you would use to search in google; Rules - the business rules written in their vernacular using SME's terms; Examples - testable cases illustrated via rules, explicit real world values (but only relevant data), and don't forget the counter-examples (edge cases).
An Introduction to Specification by Example by David Evans (2 hrs Prezi slide show).
Comments