Ramona Schwering

Frontend development is about connecting with your audience and creating a memorable experience for them. And with eCommerce, it's even more important to make that connection. However, don't let the thought of a steep learning curve scare you off from eCommerce projects - You don't need to be an expert to start building with Vue.js and Shopware Frontends. Join us as we show you how to add eCommerce features to a small application and create a fun and engaging experience for your customers. Let's craft an eCommerce story together!

“It’s a trap” - a call or feeling we all might be familiar with, not only when it comes to Star Wars. It’s signalizing a sudden moment of noticing imminent danger. This situation is a nice allegory for an unpleasant realization in testing. Imagine having the best intentions when it comes to testing, but still ending up with tests failing to deliver you any value at all? Tests who are feeling like a pain to deal with?

When writing frontend tests, there are lots of pitfalls on the way. In sum, they can lead to bad maintainability, slow execution time, and - in the worst-case - tests you cannot trust. But it doesn’t have to be that way. In this session, I will talk about the common mistakes developers make, at least from my experience. And of course, on how to avoid them. Testing doesn’t need to be painful, after all.

Ramona and I will explore the realm of end-to-end testing using Cypress.io. Our discussion will cover the basics of getting started with Cypress.io and the reasons why it should be an essential tool in your daily testing toolkit.

Ramona is a software engineer with roots in quality assurance. She primarily uses this to strengthen trust in test automation and support the testers and developers alike, becoming a Google Developer Expert in Web Technologies, Women Techmaker Ambassador, and Cypress ambassador in the process.

Ramona Schwering introduces us to the idea of visual testing. When should you consider visual testing? Can you ignore pixels for testing? How do you test responsive design? What do you do when an error shows up? How does visual testing sit alongside other forms of testing?