Agile Testing


  • Value of testing not recognized
  • Laziness
  • Code can break when refactoring
  • Unit testing is boring – uncool
  • Legacy project – testing is such a small dent – demotivating
  • Multiple developers working on the code base breaks other person’s automated tests
  • Coverage – metrics demotivate
  • Setup for test – framework


  • Tools to make it easier to write the tests
  • Have someone review the automated tests
  • Demo how code should be used (in unit test code)
    • Aids with documentation (someone else will benefit from investment in testing)
  • Write test first – then the code
    • If interface is agreed upon; it aids TDD
  • Isolated test to module
  • Utilize module owner accountability to overcome demotivation
  • Rewards – motivation token
Explore posts in the same categories: agile, testing

One Comment on “Agile Testing”

  1. […] Lean P2P group « Agile Software Engineering Practices class in Cambridge Feb 5,6 Agile Testing […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: