Fri, 2 April 2010
Episode 35 Code Quality for Automated Tests

In this episode Matthew and Federico talk about the quality of test code. They share what to look for when reviewing test code and their experience dealing with automated test cases written by a large team.

News

  • One year anniversary of the Coding QA podcast!!!

Test Code Quality

  • A sense of pride on the code you write.
  • Reviewing tests is more effective when done early.
  • What to look for when reviewing tests?
    • How easy it is to figure out why a test failed from the log?
    • How good is the test at catching the intended bug?
    • How resilient is the test to other changes?
    • Over verifying and under verifying.
    • Does it align to .NET coding guidelines?
  • Common excuses by testers
    • I don't have time.
    • I don't understand what is the value.
    • Test code is not the same as product code.
  • Test engineers produce code, as professionals we must strive for the best code.

 

Direct download: CodingQAEpisode35.mp3
Category: podcasts -- posted at: 2:21 AM
Comments[2]
    :DDD Sorry, for no feedback...

    I like your show and i loved James Bach-s interview. So yes please continue to do these podcasts.

    When i\'m coming into the office the first thing i\'m doing is to check for an update.

    And i\'m an automation expert so this episode is particularly interesting. :)

    posted by: Hannibal on Fri, 4/2 03:12 AM EDT

    Congratulation on completing one year Matt and Federico!! Please keep the podcasts coming.
    Matt, it is not just your mother downloading the podcast, multiple people from my company have listened to at least one podcast, including both our QA and Dev. I know I comeback every week and listen to you guys.
    Keep up the great work gentlemen.

    posted by: aea414 on Thu, 4/8 10:41 AM EDT


    Post your comment:

    Name

    E-mail (will not be published)

    website

    Your Comment


    Please do not click submit more than once