Jim Holmes
Father. Husband. Geek. Veteran. Around 25 years IT experience. Co-author of “Windows Developer Power Tools.” Coffee Roaster. MVP for C#. Chief Cat Herder of the CodeMash Conference. Diabetic. Runner. Liked 5th grade so much he did it twice. One-time setter, middle blocker, and weakside hitter. Blogger (http://FrazzledDad.com). Evangelist for Telerik’s Test Studio, an awesome set of tools to help teams deliver better software. Big fan of naps.
Website URL: http://FrazzledDad.com
Functional Testing from Acceptance Criteria to Zip Files
This session lays out the fundamentals of working with automated functional testing. We’ll start with discussing how important clear acceptance criteria are, then do practical implementations of functional tests dealing with common situations such as input validation, AJAX delays, and yes, downloading Zip files.
This session focuses primarily on automating web tests, but we’ll also cover common issues with WPF automation too. Demos and labs will be in C# using Selenium, but we’ll also discuss Watir, MS Web Test, and Telerik’s Test Studio. We'll briefly cover acceptance tools like Fitness and Cucumber, and how they can bring great value to your process, too.
You’ll leave this session having learned how to deal with functional testing from A to Z. You’ll also learn critical factors for success in keeping your tests running quickly, and avoiding brittle tests that break frequently.
Introduction to Unit Testing
Unit testing can save you time, money, and frustration by helping you create a safety net around your software to guarantee its stability and quality. This introductory session sets aside any testing methodologies such as Test or Behavioral Driven Development and instead focuses on the fundamentals of what unit tests are, how to write them, and some differences between the most popular unit test frameworks. You’ll also learn about organizing tests, creating test hierarchies, and heading off painful or brittle tests. We’ll also show you how to isolate dependencies using stubs, fakes, and mocks. You’ll leave this session with an understanding of how to get started writing unit tests.