Targeting Quality 2019

NOTE: You will be added by the KWSQA to the workshop you chose during registration at https://targetingquality.ca

In today’s fast feedback world, getting our product in front of users often is incredibly important.  But how do we know our product is ready to go in front of our users.  Sure, we have 1,000’s of unit and integration tests on each of our microservices, but what happens when we put them all together.  Ensuring our expectations of how our product works when all of the pieces are together is the final piece of the puzzle to give us full confidence we are ready to release and ensure our users are having a consistent experience.

In this workshop, we will discuss the different methods we can use to give us the confidence in our product.  The main focus is on the different tools available to automate our validations.  We will spend time getting to know three open source tools, Selenium (and some of the solutions built to use with WebDriver like Protractor and Cucumber) , Cypress.io and TestCafe.  We’ll discuss best practices for each of the tools as well some ways that we can make our product more testable.  We will also look at how these tools can help share knowledge of our how our product works as well as our products codebase.  And while using these tools is a great way to know if we are ready to ship it off, we’ll look at some things you can do in production to ensure that you know of issues your customers are having prior to them even calling you.

The hope is after this workshop, you have the knowledge of all of the tools we discuss and the confidence to pick a path forward for you to build your organization’s confidence in your ability to release to production. Using one, some or all of these tools will open up a new world for areas of your product to worry about and give you more confidence that your users are having the experience they desire and you imagine them having.

Pre-requisite: Bring your laptop with the latest stable version of NPM.  Also have docker installed, selenium chrome node pulled down "docker pull selenium/standalone-chrome-debug" and vnc viewer installed https://www.realvnc.com/en/connect/download/viewer/.