in

Ative at Work

Agile software development
All Tags » test (RSS)

Browse by Tags

  • Good Project, Bad Project

    The secret to writing good automated tests is to be a good software designer. It sounds trivial - but the sad fact is that more often than not the attempt to implement test automation falls due to poor software design where people are struggling with strong dependencies where you cannot test a single...
    Posted to Ative at Work (Weblog) by Martin Jul on 08-11-2010
  • The TDD Controversy - JAOO 2007

    TDD will ruin your architecture! When Jim Coplien said this in his presentation about Scrum and Architecture at the JAOO 2007 conference he really got people's attention. His statement sparked one of the most passionate debates at the conference. On Roy Osherove 's initiative we did an open-space...
    Posted to Ative at Work (Weblog) by Martin Jul on 09-28-2007
  • Iterative Development Gone Wrong - The Mini-Waterfall Anti-Pattern

    One of the frequent mistakes in transitioning to agile development is to implement iterative development by doing consecutive "mini-waterfalls". No matter how iterative it might be, if you are relying on the "W"-word, you are still doing something wrong. When we postpone testing and...
    Posted to Ative at Work (Weblog) by Martin Jul on 03-18-2007
  • Going Agile - Setting a Minimal Professional Standard

    Many agile processes are just that: Processes. However, one of the keys to success that is often overlooked is the technical project infrastructure, and the discipline and craftsmanship required by the team. While agile is lightweight it also sets the entry level for professional standards higher than...
    Posted to Ative at Work (Weblog) by Martin Jul on 12-10-2006
  • Great Quote on Testing

    While I was paging through the great Uncle Bob presentation " The Prime Directive: Don't Be Blocked " I noticed a great quote on testing from Kent Beck: "You only need to test the things you want to work."
    Posted to Ative at Work (Weblog) by Martin Jul on 11-19-2006
  • Saved by the ITimestampProvider

    If you are doing any kind of timestamping on your data, testability requires you to get the timestamps from a mockable provider, rather than using unpredictable and thus untestable values from the system. For this purpose we usually inject an ITimestampProvider with methods to get the UTC time into any...
    Posted to Ative at Work (Weblog) by Martin Jul on 11-14-2006
Page 1 of 1 (6 items)
© Ative Consulting ApS