Appium Interceptor ,Automation Trends, Playwright and More TGNS107
8 Dec 2025 · 10 min
JoeBot covers test automation news including Puppeteer's WebDriver BiDi support for Firefox, Playwright for API contract testing, and a new Appium Interceptor Plugin for mobile API mocking. His 2024 trends highlight AI/ML integration, shift-left testing, and observability, plus PayPal's actor-model architecture handling high throughput on minimal VMs.
Chapters
What are some of the top test Automation trends for 2024? How do you do contract testing using Playwright? And have you seen the video on how you can easily learn to build, train, test and deploy machine learning models? Find out in this episode of the Test Guild News show for the week of January 7th. So grab your favorite cup of coffee or tea and let's do this before we get into it. If you haven't already, please make sure to subscribe to the Test Guild LinkedIn newsletter that I'll have a link for down below to never miss another episode. First up, we have Puppeteer who has announced a new capability and this announcement is how they've extended its capabilities to Firefox utilizing the new WebDriver bidi protocol. WebDriver bidi is a fusion of the best features from WebDriver Classic and Chrome DevTools protocol, allowing bidirectional communication for more efficient and capable browser automation. And this development promises a granular control and efficient automation experience. And progress has been made in Puppeteer's implementation, which enables a bunch of different features like logging network events and forbes submissions through WebDriver bidi. And they also say that Puppeteer's integration with WebDriver bidi is still in progress. And while features like cookie access, network request interception are still under standardization, the current state demonstrates the protocol's growing functionality and reliability. You can find the links for this in the comment down below. Want to know the four difficulty levels of creating test data? Well, I found a LinkedIn article that's going to help you with this. So this LinkedIn article by Ivan goes over or likens data generation for testing to difficulty setting in a video game, and it's a fun way to learn more about different test data approaches you could be using. So one level is the hell level and that equates to manual data entry. It's deemed the most challenging and also the least recommended, suitable only for really quick one off situations with restricted access. Also, nightmare level involves automating data entry through ui, which while better than manual input, is slow and often unreliable. And I really like number three, which I think should be the normal mode and he calls it the normal level and that's seen as a more balanced approach which advocates for using APIs for data generation. And this method is significantly faster and more effective than the UI approach for sure, bypassing the need of a heavy UI framework. And for those unfamiliar with coding tools like Postman that can also facilitate this process. And lastly, he goes over the easy level, suggesting direct database inserts, but data generation. However, this approach comes with caveats like potential complexities in the database structure and access restrictions, but he advises using the API method if these issues arise when you try to do the easy level thank you Ivan for this fun, readable article that gets us to think more about how we can approach test data in 2024. So so this next resource is all about how to do API contract testing using Playwright. This approach by Andre goes over a novel way to really ensure that front end applications interact correctly with third party APIs. So contract testing, traditionally used for verifying interactions between microservices, is now being applied to client server architectures, with the front end acting as either a consumer or provider of various APIs. And this method is really useful with third party APIs that cannot be directly accessed during tests. And Playwright comes into play by allowing the simulation of API interactions at the network level. And I really liked how this article highlights a practical example of using a cryptocurrency app that demonstrates how Playwright can interact and intercept the test API requests made by the front end. And this process involves checking the request contract against predefined schemas, ensuring the front end makes specific requests in the correct format. And this approach to contract testing on the front end not only streamlines the testing process, but it also ensures a high degree of accuracy and reliability in your software development of your application. So another cool feature of how you can leverage Playwright for other types of testing, and you can find that link in that comment down below. Also, as it is the first new show of the new year, I want to share with you my annual Top automation trends for 2024. So so I just released this. It goes over the top 12 automation testing trends that you need to know in the new year. So this year one of the key takeaways is the increased integration of AI machine learning into automation testing, promising more effective, efficient and accurate results. Also, a significant shift is seen in testing practices with the focus on catching bugs earlier in the development cycle and the rise of testing directly in production environments and how to handle real world user at scale. And and this article goes over how to do that and what my top trends are that I definitely think you need to know. And I'm curious to know if you're seeing the same thing. So I'd love to know your thoughts after you read this article, what you think, what I missed, what I may have been spot on, or if something I'm completely wrong, let me know in the comments down below. So seeing how AI has only going to grow more in 2024. It's not a silver bullet, but I think as a tester you need to know more about it. You need to know how you can build it, get your hands dirty a little bit on a simple example and how you can test it. So I found a great resource that teaches you how to how to do this. And this is by Josly who just dropped a new video that goes over how to build, train and deploy a machine learning model using an Azure Free account. So the video goes over creating a workspace in Azure Machine Learning Studio, how to upload and validate a data set for training. I think he goes there setting up a compute cluster for machine learning. There's an example on automating the machine learning algorithm using Azure and as I mentioned really critical it goes over how to test and deploy the machine learning model as a real time endpoint. I also just learned of a new Appium plugin that you should know about as well, and this is by SAI and it's called the Appium Interceptor Plugin. And SAI has just released this in its first beta version and this is a real cool tool because it's designed to make mobile automation easier by introducing the ability to intercept and mock API responses. So utilizing the MIT M proxy, a well known tool in the field of network monitoring, the plugin operates by starting a proxy server for each Appium session and this server then redirects altnetwork traffic from the device through the proxy, allowing for detailed monitoring and manipulation of API responses. Really cool technique and the plugin, while powerful, is also user friendly with mocking capabilities that are disabled by default to ensure ease of use. Users can also enable this feature by setting the Appium intercept capability to true when interacting with a new Appium session, and this flexibility makes the tool adaptable to a wide range of testing scenarios. So all you developers and testers in the mobile app space really are encouraged to try this out. And also SAI is looking for feedback from you in the community to further redefine and enhance this capability. So definitely give it a try and let SAI what your thoughts are and you can find the link to this in the comment down below. So I love looking for real world stories on how people succeed with making their applications not only functional, correct, but also perform it. So here's an article that goes over how PayPal actually did this and so this is A Story of PayPal System Design Evolution and this article goes into detail on how PayPal started, how the system started, and how it faced explosive growth, and how it quickly reached a million transactions per day, but soon encountered the limitations of Moore's Law as single thread performance gains slowed down. And it also goes over how the traditional approach of scaling up with newer hardware became inadequate, leading into PayPal to adopt horizontal scaling over 1,000 virtual machines, and how this solution, though, introduced new challenges such as increased latency, costly network maintenance, complex infrastructure, and insufficient CPU usage. And it goes over how it solved all these issues using an actor model and and this model enabled PayPal to handle a billion daily transactions on just eight virtual machines, which is mind blowing. So if you haven't checked out the Okta model, this article goes over into detail of what it is so one of the trends on my top 12 trends for 2024 was on observability. So this next article goes over a little more in detail. Open Telemetry and Observability so last year I talked to a lot of people and many people talked about opentelemetry, how it made a lot of different achievements and stable releases of three core signals, tracing metrics and logging. And this development represents a big step in realizing OpenTelemetry's vision as a standard framework for collecting observability data. So this article highlights some key highlights from the year, including the widespread adoption of opentelemetry specifications for metrics and integration of distributed tracing and leading load testing tools like Grafana K6 and Artillery IO. And these achievements have enabled more detailed analysis and performance optimizations during load testing, which is critical. And also highlights the growing trend towards expanding the use of observability tools into development and testing phases, which is critical. If you haven't checked out observability As a tester, 2024 is the year that you definitely need to learn more for sure. All right, for links of everything value we covered in this news episode, head on over to the links in that comment down below. And if you haven't already, I highly recommend you subscrib subscribe to the Test Guild LinkedIn News show newsletter, which we'll have a link for down below as well. And once again, I'm Joe. My mission is to help you succeed in creating end to end full stack pipeline automation awesomeness. As always, test everything and keep the good Cheers.
More from JoeBot
Automation Testing Podcast 2026: New Schedule, Events, Discounts with Joe Colantonio
Automation Guild Kickoff, AWS Nova, Karate v2, and AI Testing Reality and more TGNS177