In order to prevent bugs and release quality code to market, you also need developer testing, including test driven development (TDD). Discover what test driven development is and how it can help you write better code.
- The difference between unit testing and test driven development (TDD).
- The TDD cycle: How to get started with TDD (Red-Green-Refactor)
- Benefits of TDD
- Problems and Pitfalls of TDD
- Principles of TDD
- How TDD can be used to debug both new and legacy code
Gojko Adzic returned to illustrate how to create “Effect Maps” to manage requirements and do better Acceptance Test Planning – he will walk us through a sample problem.
He will also answer some questions we didn’t have time to answer from our webinar from a few weeks ago titled: “Effective Specifications for Agile Projects“.
1. Regulated environments/traceability
How do you sell Agile in an enterprise where audit department wants to have evidence for each change in requirements?
In a regulated industry, how do you do specs when the stories for the release are not defined at the start of the project?
What should system requirements look like when using Agile in an FDA-regulated industry? When are they “done”?
July 16, 2010 — 12-1pm PDT
This session is about how proper use of acceptance testing can avoid many problems instead of merely finding them at the end. It redefines the role of QA to one of avoiding errors and improving our system of development. Acceptance test-driven development is the process of having customers, developers and testers all talk about the requirements before any coding is done. By answering the question “how will I know I’ve done that” for each requirement, prior to it being developed, both a greater understanding of the requirement can be achieved and a better process to implement that requirement can be attained.
* Why answering questions about requirements will never get you the answers you need
* How creating test specifications increases developers understanding of requirements
* Why writing tests first speed you up in the short term while saving time in the long run.
Speaker: Alan Shalloway from Net Objectives – who’s approach of Business Driven Software Development has a proven track record with medium to large organizations. They cohesively engage business and development sides of an organization to ensure product enhancements are properly selected, sized, prioritized and then implemented. Management is also engaged as they provide the proper organizational structure for development to take place. They believe that when it comes to developing software, there is no one-size-fits all.
** Primary audience: Developers and Testers. (Also useful for: Team Leads)
Acceptance tests are a critical part of Agility Success.
Long term maintenance cost is one of the biggest issues that teams face today when implementing agile acceptance testing.
Tests that are just written and automated without any long term planning are guaranteed to cost you more than they are worth. But then again, a properly designed testing framework saves a lot of money, …