Leveraging the UI / Avoiding the UI

Hi everyone,

We're delighted to be pairing with NI Dev conference for our next meetup!

Thanks to ASOS for their support in hosting and supplying of refreshments.

Additionally, for those attending on the night, you'll have the opportunity to win a ticket to https://automation.eurostarsoftwaretesting.com/ taking place in Berlin in November!

Talks:
Speaker: Hugh McCamphill
Shining a light on web performance: Automated lighthouse reporting with WebdriverIO
Lighthouse is a tool available in Chrome to provide insights into your web application covering areas such as performance and accessibility.

It’s trivial to run an audit on any webpage, but typically this will be done on an ad-hoc basis, but what if you want to test a page behind authentication or test performance as part of a user journey? And do so reusing your existing automated tests?

Well, now you can.

Come to this talk to learn how you can leverage your existing WebdriverIO-based tests, and with minimal extra work generate lighthouse reports that cover user journeys, page navigations as well as page loads, in both mobile and desktop views.

To set the scene, we’ll cover reasons why a focus on improving your scores in the lighthouse audit matters, plus an overview of the type of information it provides.

Join me in this talk to learn about the insights that Lighthouse can provide, how to include Lighthouse audits as part of your automated WebdriverIO tests, and how you can incorporate the audits in your CI/CD pipeline.

Speaker: Jordan Colgan
Avoiding the UI: Why and how with acceptance test driven development
How do you mostly test your systems? Do you have automation that replicates user interaction? That makes sense, of course you want to test the software the same way it will be used.

“As far as the customer is concerned, the interface is the product” - Jef Raskin

The idea that User Interfaces (U.I) should be our main focus is an easy assumption to form. Everyone sees and interacts with the U.I. It’s what the Product Owners reference in their acceptance criteria. The Designers spend their time trying to build the best experience through it. Developers often drive out the functionality starting from it. Quality Assurance uses it for their approval.

In this talk, we are going to explore the idea that the U.I. is not as important as we think and why we should avoid writing most automated tests through it. We’re going to learn about Acceptance Testing Driven Development (A.T.D.D.), what it is, what it’s not, and how it helps us avoid the common pitfall of treating the U.I. like it’s our most important asset.

Look forward to seeing you there