Ramona Schwering

Quality assurance engineer


Main focus: Automated testing

Twitter handle: @leichteckig

Languages: German, English, Dutch

City: Münster

Country: Germany

Topics: unit testing, test driven development, testing, frontend development, agile software development, javascript, web development, quality assurance, ui/ux development

Services: Talk, Workshop management, Consulting, Coaching, Interview

  Willing to travel for an event.

  Willing to talk for nonprofit.

Personal note:

My passion is test automation in the frontend area - and I want to make life as easy as possible for the testers. I want to achieve that they can concentrate on the truly important things - to be able to explore a product and its improvement potentials without being too tied to the concept - and without being bound to checklists. I would like to share my way to get there and especially my learnings from it with you.

Bio:

After my training as an application developer, I have now been working in quality assurance at shopware AG for almost 5 years. So I have both views of the product - that of a tester and that of a developer. I use this mainly to strengthen the trust in test automation and to keep the testers' backs free. The automation in the end-to-end area of shopware was written by me and I continue to drive it forward.

Examples of previous talks / appearances:

It's a (Testing) Trap! - Common Testing Pitfalls and How to Solve Them

“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.

This talk is in: English
Flaky tests - Fighting nightmares

A test can also be such a liar: Unreliable tests are living nightmares for anyone who writes automated tests or just pays attention to their results. Sometimes they pass, sometimes they don't, and therefore do not give a valid statement about the state of the software. In the worst case, they can damage the credibility of the entire test suite. It doesn't matter whether you write unit, integration or end-to-end tests, you can encounter them in any way you can think of.

I've spent hours and hours on such tests, and I want to share my journey and the lessons learned from them: So that together we can avoid or even get rid of these nightmares.

This talk is in: English
Avoiding Common Testing Pitfalls with Ramona Schwering

There are so many traps one can fall into when creating automated tests. In this episode, Ramona Schwering, a software developer with a passion for testing, shares her tips to help you avoid some of the most common testing traps. Discover strategies to prevent slow tests, painful-to-maintain-and-debug tests, and tests that have no value. Stop wasting valuable time debugging and maintaining flaky tests. Listen up!

This talk is in: English
DE Symfony meet Cypress - E2E Tests für Symfony Entwickler:innen

Ramona Schwering zeigt, wie einfach es ist mit Cypress.io End to End Tests zu erstellen und so Anwendungen zu prüfen.

This talk is in: German
Writing unit tests with Jest (Developer Tutorial)

You should always write a unit test for any function change. It guarantees that your written code works and that a third party developer does not destroy the functionality with his code in the future.

Having good test coverage means we can be confident that we can deploy stable software without requiring additional manual testing.

We use Jest as our test framework. It is a solid foundation and is used by many developers. This small video will show you how to write those unit tests for the administration in Shopware 6, on the component test level.

This talk is in: English
A matter of trust – test

Our daily work at Shopware, but also at agencies, ends up in the hands of people who trust us not only to have done our best, but also that it works. It is our job to instill this trust. Fortunately, we developers have a way to ensure something like that: Testing! Let's discover in this talk how we approach automated testing in Shopware, how far we have come on this journey, and what we have gained so far.

This talk is in: English
E2E testing as it should be - Introduction to Cypress

When it comes to UI testing, some developers tend to be reluctant a lot. Are those tests slow, flaky, hard to write and maintain?

Cypress.io (or Cypress for short) is currently getting a lot of attention when it comes to end-to-end testing. Especially in JavaScript environments Cypress.io seems to be slowly gaining acceptance. It does a lot of things right and is preferable to selenium-based approaches in my opinion.

In my session, I want to introduce Cypress to you and explore its possibilities by writing first tests for the SymfonyWorld website (or any other if I need more test cases) - so that we can overcome those concerns together.

This talk is in: English
Devtalks: ep 36 - Ramona Schwering - TDD Frontend

Ramona arbeitet als Quality Assurance bei shopware

Wir unterhalten uns mit Ramona über Test Driven Development im Frontend.

This talk is in: German