Write your custom OpenRewrite recipes & It's a (Testing) Trap! - Common Frontend


Details
Dear Java Community,
The summer holidays are almost over and we are excited to invite you to our OpenValue Meetup on 22nd of August!
In our brand-new office at “Am Wehrhahn 41, 40211 Düsseldorf” (make sure you’re coming to the right place). Join us for the “office warming party”. We’re taking care of food, (cold) refreshing drinks and two amazing talks. You’ll just have to bring yourself and your questions.
In the first talk Tim will show us how we can easily write our own recipes for OpenRewrite using different approaches.
After that Ramona will tell us about common pitfalls in Frontend testing and how they can be tackled.
Don't miss out on this and RSVP to confirm your attendance.
Agenda:
- 18:00 Walk in
- 18:30 First Talk
- 19:15 break
- 19:30 Second Talk
- 20:15 Drinks and Discussions
First Talk:
"Write your custom OpenRewrite recipes"
By Tim te Beek
OpenRewrite allows you to automate the maintenance on your code. A large collection of existing recipes allows you to upgrade, improve and secure your applications. But what if you want something beyond what’s already available out of the box?
In this live demo we’ll explore writing custom OpenRewrite recipes. That might be small additions to existing migration recipes, or larger efforts to adopt breaking changes. Walk away knowing exactly how to upgrade that internal library or framework, or how to contribute recipes that everyone can then use.
About the speaker:
Tim te Beek is a staff software engineer at Moderne, which automates software refactoring at scale. He has extensive experience contributing to and presenting on Open Source software within the Java ecosystem. Previously he worked as a consultant specializing in migration engineering and developer productivity.
Second Talk:
"It's a (Testing) Trap! - Common Frontend Testing Pitfalls and How to Solve Them"
By Ramona Schwering
“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.
About the speaker:
Ramona works as a Developer Advocate at Auth0 by Okta, is an international speaker and Cypress Ambassador with a deep passion for open source. As a software engineer with a strong background in quality assurance, Ramona brings a unique dual perspective to the table, understanding both the tester's and developer's viewpoints. This expertise is leveraged to build trust in test automation and provide support to both testers and developers. Throughout Ramona's career, these efforts have earned her recognition as a Google Developer Expert in Web Technologies, a Women Techmaker Ambassador, and a Cypress Ambassador.

Write your custom OpenRewrite recipes & It's a (Testing) Trap! - Common Frontend