Two Days Developer Testing Bootcamp

The Developer Testing Bootcamp offers a comprehensive, hands-on learning experience to various tools and techniques for effectively practicing automated testing and Test Driven Development.

Over the past decade, eXtreme Programming practices like User Stories, Test-Driven Development (TDD), Refactoring, Continuous Integration and Automation have fundamentally changed software development processes and inherently how engineers work. Practitioners claim that it has helped them significantly improve their development speed, design quality and responsiveness to changing requirements. Software professionals across the board, from Internet startups to medical device companies to space research organizations, today have embraced these practices.

At the end of this training the team will be able to:

• Understand the difference between
  • white-box vs. black-box tests,
  • positive vs. negative-path testing,
  • unit vs. integration vs. behavioural test and
  • line-coverage vs. branch-coverage.
• Use various automated testing techniques and strategies to carefully test your code.
• Practice key techniques to break coupling between classes and micro-test each component independently.
• Experience the thought process and steps involved during a typical test-driven session.
• Drive the development (design and implementation) of a User Story using automated tests.
• Discover improved confidence & increase in development speed by writing tests first!
• Identify poorly designed tests by using our elaborate test smell vocabulary.

Developer Testing Core Concepts

• These concepts will help developers understand some core testing concepts like difference between
  • white-box vs. black-box tests,
  • positive vs. negative-path testing,
  • unit vs. integration vs. behavioural test
  • state vs. interaction tests and
  • line-coverage vs. branch-coverage.
• An interactive code-walk through followed by a hands-on lab.

Automated Unit Testing

• We'll cover the philosophy of developer unit testing, provide a detailed overview of xUnit framework, including how to write and organise tests, which assert methods to use, how to deal with exceptions within tests and test naming conventions.
• Different levels of testing and their qualities/attributes will be demonstrated.
• All these techniques are introduced using xUnit in the respective IDEs.
• 
An interactive demo followed by a few labs in which developers learn how to write effective test including tests where external systems or sub-systems like databases are involved.

Test Smells helps developers identify common problems in your tests.

In this workshop, students will be given a few badly written tests (one at a time.) Students will have to find the problems with each test and then fix those tests to avoid those problems.

Faking & Mocking

• Collaboration between objects lies at the heart of all object-oriented programming. Every OO pattern ultimately comes down to one object calling another. But all collaborations aren't created equal! Some collaborations are especially awkward to test, and this workshop demonstrates how to test collaborators better, and improve the way your objects work together.
• We introduce various kinds of test doubles or fakes: Stubs, Mocks, Spy & Simulators via a hands on lab.

Test-Driven Development (TDD)

• TDD is a practice for efficiently evolving useful code. While its name implies that it's mostly about testing, test-driven development is primarily about design: it keeps programmers focused on exactly what they need to build and helps them avoid over-engineering.
• We'll demonstrate the TDD Rhythm. Participants will understand how TDD simplifies evolving lean, useful, fully tested software.
• We'll give a small live demo of TDD and then Participants will get their hands dirty by using TDD on 3 different problems.
• We'll conclude by highlighting the different styles of TDD.

1 or 2 Days of Mentoring via Pair Programming with Developers on your code base

• To get your team kick-started with the learning from the workshop, we recommend, that our trainer spends a day or two, working with your team on your code base.
• Each day will be reserved for 4 pair programming sessions. During these sessions, the workshop participants will take specific examples from their projects, where they are finding it difficult to apply any of the practices learned in the workshop. The trainer will then pair with an individual to show how to resolve those challenges.
• At the end of the day, the 4 volunteers will summarize their learning by showing before and after code from their respective pairing session to the rest of the group.

Pre-Post Programming Assessment

The goal of these programming assessments is to identify real and quantifiable measures for the learning achieved through our workshop.

Objective

• Get a quick understanding of your knowledge and skill level with respect to Designing & Programming
• Establish a baseline against which the effectiveness of the workshop may be measured
• Customize our workshop based on specific areas identified in this assessment

Pre-Assessment

• Before the workshop, we'll send a problem description, your developers will spend max 4 hours and solve the problem and send us the code. We'll evaluate the code and send you detailed feedback about the code, including areas for improvement. We can send different types of problems (fresh development, cleaning up existing code and so on.)

Post-Assessment

• 2 week after the workshop, we send another problem and evaluate the solution code. A comparison between the Pre and Post Assessment should be able to clearly quantify per-participant level improvement.
• Click on the image to download the sample report...

Method of Instruction

Interactive Dialogues, Programming Exercises, Demos and Instructional Games

Transfer %

Knowledge: 50%, Skill-Building: 50%

Target Audience

• Primary: Programmers, Architects, and Designers
• Secondary: Technical Managers, Business Analysts, Testers, Technical Writers

Course Level

Beginner to Intermediate

Course Prerequisites

• Required: some understanding of OO concepts and an OO language
• Highly Recommended: basic understanding of the life-cycle of software projects

To ensure a successful workshop, we require the following facilities:

• HDMI projector (1024x768 minimum) & Projector screen
• 1 White board & Dry erase markers
• Cluster seating with 5-6 people on each table

• 1 Flip chart with the stand and marker pens for each table
• Notepad and Pen for each participant
• Ample room for students in terms of room size and set up
• For Dev trainings: at least one powerful workstation between two programmers

Java

• Latest Java JDK
• Latest Standard Eclipse OR IntelliJ Idea
• JUnit, Mockito, JBehave, FitNesse or Cucumber

C#

• Latest .Net Framework
• Latest Visual Studio
• Latest ReSharper Plugin
• Latest JetBrains Rider
• SpecFlow's Visual Studio IDE Integration or FitNesse

JavaScript

• Latest WebStorm JavaScript IDE
• Latest Chrome Browser
• Latest Jasmine Framework
• Latest Jest Framework
• Latest JsTestDriver

C/C++

• Latest Eclipse CDT OR Visual Studio
• Latest GTest
• Latest Visual Studio
• Latest CLion

Ruby

• Latest RubyMine
• Latest Cucumber

PHP

• Latest PHPStorm
• Latest PHPUnit, BeHat

Flex

• Latest Flex SDK
• Latest Flash Builder OR IntelliJ Idea