2025-03-05 –, RoboCon Online
The IT-landscape..., I bet by now you are familiar to the ever-increasing number of integrations and their related hassles. Pre-test configuration can be an absolute nightmare. And what about testing the API-error handling? Ever thought of stubs? Let me show you how you can easily manage those stubs in a dynamic way, straight from your RF script!
Unless you’re performing end-to-end testing, you probably don’t care much about all those integrated parts of services that surround your team’s masterpiece. They just need to function and provide the correct data.
We’ve come a long way since the monolith era. Today, it’s all about microservices and small, agile teams that need to integrate their small masterpieces. Oh, and let’s not forget the ever-growing number of external APIs from companies and services you need to connect with.
I bet you’ve encountered numerous problems related to these APIs that negatively affect your testing endeavors. Just to name a few:
- You need test data that isn’t available, or it takes another team forever to set it up
- The service isn’t available (yet) or broken due to ongoing changes
- You need to test error-handling, but you’re unable to simulate those situations
In this talk, I’ll explain how you can leverage stubs to regain control. And the best part is… you can do this directly from the Robot Framework. I will show you:
- A library (MockserverLibrary) that lets you easily manage your stubs
- How to manage requests and responses directly from your Robot Framework script
- How to handle this dynamically, gaining control while minimizing maintenance
- Insights and choices you can make regarding the stub management
- Various ways to set up and test error-handling in integrations
- Methods to verify (in)correct process flows within integrations
This session is packed with practical examples that you can apply right away.
stub, api, testdata
Describe your intended audience:Anyone involved in testing software components that connects to APIs from outside the team, where these APIs shouldn't or don't need to be part of the tests being performed.
Is this suitable for ..?:Beginner RF User, Intermediate RF User, Advanced RF User
I've been a testconsultant for over a decade and during that period I've supported companies to get a grip on the quality of there products. By combining and aligning both process and technique I strive to get the most out of the effort that people put into there quality endeavours. I'm a trainer for several QA related topics like Robot Framework, Test Automation Proces and Exploratory Testing.