In this show Matthew and Federico share their experiences working as testers in the MVC feature crew. They go over how the team works, the development lifecycle from a QA point of view, the principles that the team adopted as well as an honest assessment of what didn’t go so well.

• News
  • MVC 2 Preview 1 released
  • What's new in MVC 2 (ScottGu)
    • Ability to easily partition and group functionality across an MVC application.
    • Ability to use Data Annotation attributes to validate input.
    • Ability to use Data Annotation attributes to drive the generation of UI in the Views (ala Dynamic Data)
    • Strongly typed UI-Helpers
• Inside the MVC team
  • Lifecycle of a "feature": Idea -> Prototype -> Exploratory Testing -> Review -> Application Building -> Automation (Rinse & Repeat)
  • Challenges of testing an installer.
  • Development principles
    • QA is involved during design.
    • All feature check-ins are previously approved by Dev/Test/PM
    • All check-ins contain unit tests
    • QA drives the schedule
    • Weekly test plan.
  • What could had gone better
    • QA not working close enough with Devs.
    • A lot of non-MVC work caused a lot of distractions.
    • Big bug debt coming in from MVC 1.0
    • Ramp up time for new QA members took longer than expected.