Coding QA Podcast: Episode 51 - New Owners and Test as Dev

Coding QA Podcast

In this episode Matthew discusses his transition from QA to Developer. CodingQA is officially handed over to two other ASP.NET QA team members - Mark and Jim. We cover the latest product releases since the last episode, and we look at some examples of testers being developers.This Week's

Running time
0h17m
File size
16.00MB

Download Original File | View original post

Episode synopsis

In this episode Matthew discusses his transition from QA to Developer. CodingQA is officially handed over to two other ASP.NET QA team members - Mark and Jim. We cover the latest product releases since the last episode, and we look at some examples of testers being developers.

 

This Week's News:

  • New role
    • Matt re-joins the ASP.NET team as a developer
    • Why the switch?
  • New owners
    • Mark and Jim take over the show
    • Introduction, history and role in the team
  • Product releases
    • WebMatrix, ASP.NET MVC 3, NuGet, and the ASP.NET Sprite and Image Optimization Framework Preview 3

Testers as developers – real world examples:

  • Mark takes a developer role working on the Sprite and Image Optimization Framework
    • How did that happen?
    • Jim tests Mark’s code
    • What did Mark miss and why?
  • Jim describes his adventures playing the developer on the on the ASP.NET Web Pages templates NuGet packages
    • Mark tests Jim’s code
    • What did Jim miss and why?
  • The value of a second set of eyes
  • Thoughts on how we can further blur the lines between tester and developer

You might also like...

Comments

Contribute

Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“Theory is when you know something, but it doesn't work. Practice is when something works, but you don't know why. Programmers combine theory and practice: Nothing works and they don't know why.”