Speakers 

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.

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.

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.

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.

Please don’t mock me

Confusion over test doubles starts with what to even call them. You might know them as stubs, proxies, mocks, or spies (but I call them test doubles, because a book you've probably never read declared it to be the most general term). I've spent a decade fascinated by the disconnect between why test double libraries were invented and how they are actually used by teams. What I've learned: their purpose fills a little-known but valuable niche, whereas their appeal addresses a mainstream but self-destructive impulse. If you don't leave this talk with a clearer distinction between tests that ensure safe changes versus tests that promote simple designs, I'll give you your 45 minutes back. Once that groundwork is laid, you'll better understand the characteristics that matter most in a test double library and the nuanced rules that should govern their use. I've found this clarity invaluable for producing valuable tests and maintainable code, and I think you will too.

Working Well: The Future of JavaScript Testing

One of the primary goals for testing software is to have confidence that your software works as intended, but this doesn't give much insight into the quality of the software. Is it performant? Does the design look right? Are we sending too much code? Answering these questions in an automated fashion today is hard, but that will be changing in the future. In this talk, we'll explore how recent changes in technology give us a foundation to start answering the questions posed above and so much more. We'll look at a near future where we have confidence that our software is functional and works well.

Testing Angular Components Fundamentals

In the Angular world, the most common concept that you stumble upon is components. Since components are everywhere, it is critical that you understand how to test them. In this talk, you will learn the fundamentals of how to test Angular components. By the end of the talk, you will have the confidence to start writing tests for your components.

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.

Detox: A year in. Building it, Testing with it

A year in, developing and using Detox in production taught us a lot. From designing its API, to consuming it, testing real user scenarios to advanced mocking, we learned what makes sense when E2E testing an app and what doesn’t. In this talk, we’ll discuss how Detox works and what makes it deterministic, cover some advanced use cases and methodologies, go over new features and tease the ones that are upcoming.

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.

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.