8:30 AM - 9:30 AM Breakfast & Registration

9:30 AM - Opening Remarks

9:40 AM - Jason Lengstorf // IBM “But Testing Sucks!: How IBM is building a testing- and quality-driven culture despite internal resistance.”

How can we create a performance-, quality-, and test-driven culture when the company has years of bad habits to break? Is it even possible? In this talk, learn how IBM has been steering its massive engineering team away from deep-seated resistance to writing tests — or collecting code quality metrics of any kind — through a combination of automation, human psychology, socialization, and education.

10:45 AM - Aaron Abramov // Facebook “Establishing testing patterns with software design principles.”

Lack of clarity about testing React applications leads engineers to write low-quality tests that don’t catch bugs, break unnecessarily, and are hard to write; therefore, we need established patterns to write tests for single page applications, just as there are established patterns to write single page applications.

11:50 AM - Ryan Marsh // Cucumber Ltd. “BDD with cucumber.js”

Hundreds of teams are benefitting from BDD (Behavior Driven Development). This brief talk will familiarize you with what BDD is and isn’t so you can decide if it’s right for your team.

12:15 PM - Lunch

1:15 PM - Gleb Bahmutov & Brian Mann // Cypress “I see your point, but… .”

These two speakers work together making awesome testing tools, yet they often disagree on how to produce high quality software. In this presentation they will respectfully argue about: test-driven development vs end to end tests / stubs and mocks / cross-browser testing / code and data coverage / picking the right test framework / snapshot testing / legacy browser environment support / crash reporting and performance monitoring / earning living by writing OSS testing tools

2:20 PM - Jessica Jordan // Simplabs “Testing against time in JavaScript applications.”

As our apps become more complex, we might stumble into testing errors stemming from asynchronous and time-dependent behaviour. This talk will characterize several roadblocks in testing which are affected by time. With an example Ember.js application, we will explore how Ember's rich testing API, newest JavaScript features and community libraries, will help us writing legible and reliable tests and how we can make those tests turn green even as time passes by.

2:45 PM - Rotem Mizrachi-Meidan // Wix


3:05 PM - Mary Snow // Codesmith “Testing React Applications.”

React continues to grow in popularity, especially with the release of React 16. Developers who love using React may be at a loss of how to test their React applications. In this talk we will explore how to use Enzyme and JSDOM to test your modern React applications. We will dive into Enzyme testing and explore how to test both the DOM and virtual DOM by using Enzyme's core methods: shallow, render and mount.

3:25 PM - Break

3:45 PM - Justin Searls // Test Double “Please don’t mock me: mocking 101.”


4:50 PM - Kent C. Dodds // PayPal “Write tests. Not too many. Mostly integration.”

Automated tests are an important part of raising your confidence when releasing software. They can speed you up or slow you down depending on how you write them and which form of testing you focus your test writing on. In this talk, we’ll cover the value of automated testing and where your efforts should be focused to strike the best balance of confidence and effort.

5:15 PM - Trent Willis // Netflix “What's Next for Testing JavaScript?”

In this talk, we’ll explore some of the next "big" things for testing JavaScript applications. These ideas will include parallelization and distribution of test suites, easier and more robust “acceptance” testing, environment-agnostic (or “isomorphic”) testing, and automation of “edges”, such as layout, performance, accessibility, and security. We’ll talk about how and where some of these ideas are already coming into play, drawing examples from various Open Source projects and actual companies. The future for testing is probably closer than you realize.

5:35 PM - Closing Remarks

6:00 PM - After Party


* Schedule is subject to change