9-9:45 AM(EDT)

Joe Colantonio (Host) - Pre-show warm up to make sure everything is working before conferences starts.

10-10:50 AM(EDT)

Ryan Yackel (QASymphony) - Making the Move to Behavior Driven Development (BDD)

Properly implemented Behavior Driven Development (BDD) helps to drive increased automation, achieve quicker development cycles, facilitate better collaboration between departments, and reduce siloed communication. Additionally, BDD is an ideal counterpart to continuous integration/delivery by solving testing bottlenecks. Despite the benefit, BDD is under-adopted. Studies find that between 10% and 25% of development organizations have implemented or are experimenting with a BDD process. Ryan will discuss how BDD moves testing up front to avoid rushed end-of-cycle testing and how automation is included from the start to achieve automation coverage.  Ryan will get practical with a real-world working example showing a BDD example in a continuous integration workflow using Jira, Github, Jenkins, and Cucumber. Ryan will also share a successful framework for evaluating your readiness for BDD, considering any potential roadblocks, and making a seamless transition.

Gáspár Nagy - Creator  of SpecFlow &  Author of the book “BDD Books: Discovery – Explore behavior using Examples

Ryan Yackel can't make the LIVE Q&A so Gaspar will be answering any question you might have on BDD.

11-11:50 AM(EDT)

Ali Khalid - The Recall, Becoming Technical and Averting Disaster

A story of how a testing team took responsibility for quality of a new game changer product, learned more about the product’s architecture and worked towards becoming more technical. It illustrates the importance and how to implement white box testing, features of the application testers should focus more attention on and how to create business value.

+ Introduction to the safety critical product’s industry
+ Testers, technology and the “Out of scope” mantra
+ The recall
+ A revolutionary product and we’re still “out of scope”
+ Testers becoming technical
+ The covert POC and building a case
+ From black box to white box
+ Testing unchartered waters becomes worth the effort
+ Averting imminent critical issues and the competitive advantage is secure
+ Moral of the story and the resulting vision

12:30-1:20 PM(EDT)

Jason Arbon - Testers Don't Test Anymore

Jason was chatting with some other test nerd friends recently, and he bought up the idea that "Testers Don't Test Anymore" (alt title "Rise of the Software Verifier"). It stirred a lot of discussion and resulted in mostly surprised agreement. Jason is old enough to have seen the transition from testing to verification, and want to get more discussion around this idea and what to do about it in the field of testing.

9-9:45 AM(EDT)

Joe Colantonio (Host) - Pre-show warm up to make sure everything is working before conferences starts.

10-10:50 AM(EDT)

Andy Dobbels (Mailosaur) - End-to-end testing with Webdriver, Selenium and Mailosaur

In this session we will be discussing what end to end testing is and how you can create a suite of end to end tests. We will be using Webdriver.io to run Selenium based tests and Mailosaur to automate email testing.

11-11:50 AM(EDT)

Justin Ison  - Automated Exploratory Testing

In todays Agile world the time to market is becoming increasingly shorter. There is a constant desire to release new features to keep ahead of competition. Because of this we have a shorter amount of time to do exploratory and manual testing. Especially, when you have to account for all the different combinations of OS’s, languages, orientations, and resolutions your mobile app supports.

Jason's goal was to know more about my application for every new build. By using Automated Exploratory testing I could do so more efficiently.
Specifically, I wanted to know:

- Elements which had accessibility labels and which didn’t.
- How my designs looked for every resolution and orientation we supported by taking a screenshot.
- Capture any logs errors and record them.
- Detect language or locale issues.
- Capture performance metrics for benchmarking and detecting trends.
- The ability to replay a test after a code fix.

12:30-1:20 PM(EDT)

Chad Capson - How to Pick and Implement A TestCase Management System

You came into work, someone broke the test case spreadsheet, management wants another test report, the new hire started today, and another round of regression starts in 30 minutes. Well, we can't solve all of this in one speaking session, but there is something we can solve: making test case management and reporting in your life easier.

The normal tool of choice for TestCase Management for many small teams is Microsoft Excel. It is an easy tool to use and get started with. It only takes a few columns to get started: TestCase number, Description, and a place to enter a test result. Things start easy and as long as there are only a few people performing tests, excel remains a decent tool. But as the test cases grow in size, the team expands, and more reports are needed by management to determine the quality of software going into production, there has to be an easier way. And that's when Microsoft Excel just doesn't cut it anymore. Reports are hard, training is hard, someone is always "adjusting" the spreadsheet, and there's always more work to do. The numbers just aren't trending in a good way and management wants a solution.

But how can we manage the test cases we already have? Or grow the test cases as new requirements come down? Team collaboration too? And we haven't even started thinking of automating the work yet. Where do we start the process of picking a test case system, where do we look, should we do Open Source or pick a vendor? It can be a daunting task to undertake and the risk of picking the wrong system at the beginning of a team's growth is enough to worry any management team. And QA, being very risk averse, definitely doesn't like the uncertainty.

So, let's demystify how to get a good system selected, reduce the uncertainty of the system selection, define what we need and when we'll need it, build an argument with good information to present to management and get the system purchased and implemented. Let's go, be awesome, and implement the system that let's us test all the things!

1:30-2:20 PM(EDT)

Swasti Sharma - Importance of Feature Flags in Agile World

How you can leverage  A/B testing framework for releasing code with high quality when the time for testing is not enough? Swasti will demonstrate how to know when you software is ready to release.