# test-automation Published articles for test-automation. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Honoring #IconsOfQuality: Pricilla Bilavendran DevFeed: [Honoring #IconsOfQuality: Pricilla Bilavendran]() Original publisher: [Read original article]() Author: Rajrupa Roychowdhury Published: 2026-09-16T08:21:09Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Testing](), [Test automation](), [Artificial Intelligence](), [Playwright](), [Postman](), [Amazon Machine Learning]() Tags: [ai](), [api-testing](), [community](), [icons-of-quality](), [playwright](), [postman](), [quality](), [test-automation](), [testing]() ### AI overview BrowserStack profiles Pricilla Bilavendran, a quality engineering and API testing leader, and discusses her views on AI-assisted quality engineering, human curiosity, critical thinking, and the continuing importance of testers' judgment. ### Source excerpt To celebrate the relentless passion and invaluable contributions of leaders in software quality, BrowserStack is proud to honour Icons of Quality. ## Honoring #IconsOfQuality: Gaurav Singh DevFeed: [Honoring #IconsOfQuality: Gaurav Singh]() Original publisher: [Read original article]() Author: Rajrupa Roychowdhury Published: 2026-09-15T11:29:38Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Software Testing](), [Test automation](), [Microsoft](), [Microsoft Teams](), [CI/CD](), [Meta](), [Artificial Intelligence]() Tags: [ai-agents](), [ci-cd](), [icons-of-quality](), [microsoft](), [microsoft-teams](), [quality](), [software-testing](), [test-automation]() ### AI overview BrowserStack profiles Gaurav Singh, a Senior Software Engineer at Microsoft, as an Icon of Quality. The article highlights his work on scalable engineering systems, testing infrastructure, CI/CD pipelines, developer productivity, mentorship, and the role of determinism and feedback loops in automated testing. ### Source excerpt To celebrate the relentless passion and invaluable contributions of leaders in software quality, BrowserStack is proud to honour Icons of Quality. ## Introducing bun, a new package manager and JavaScript runtime environment DevFeed: [Introducing bun, a new package manager and JavaScript runtime environment]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-06T01:58:25Z Content type: article Language: en Sources: [T.J. Maher]() Topics: [Bun](), [Package manager](), [JavaScript](), [Playwright](), [Node.js]() Tags: [bun](), [bun-create-playwright](), [getting-started](), [installation](), [javascript](), [node-js](), [playwright](), [test-automation](), [typescript]() ### AI overview This article examines Bun as a JavaScript package manager and runtime, including its use with Playwright projects. It explains how Bun compares with npm, Yarn, and pnpm, and discusses its integrated tooling and claimed performance advantages. ### Source excerpt New job? New toolset to explore! In this post I'll be investigating a new JavaScript package manager and runtime environment called bun.sh. You may have noticed on Playwright.Dev's Getting Started / Installation section there are three different ways to install a ui or api test automation framework with the latest version of Playwright: npm init playwright@latest yarn create playwright pnpm create playwright For this blog post I'll be investigating a fourth way, the new toolset they just started using at work, bun.sh. bun create playwright What is npm, yarn, pnpm, and bun? These are called package managers. What is a package? Developing a project, you don't have to figure out how to code everything yourself. You can include in your projects outside libraries, or "packages" of code from from the public JavaScript registry npmjs.com. The problem is that these packages then need to be downloaded, installed, managed, and updated whenever they are updated. JavaScript projects can use a package manager, such as bun, to help this process. When putting together a Playwright automation framework based around JavaScript and TypeScript, Playwright uses the Node.js JavaScript runtime environment, to run its test runner, execute automation scripts, and manage its browser instances.(See Nodejs.org / About ) There is a division of labor: Node.js runs these internal functions like running tests. NPM, Yarn, PNPM, and now Bun handle the packages. Why are there so many package managers? Each has its own specialization. The original NPM is bundled already with Node.js. Yarn is a Facebook toolset that was created when NPM was found to work too slow. PNPM was created to be smaller and therefore faster. And bun was built for quick startup and installation speed, good especially if you have a CI/ CD pipeline that has a LOT of packages to install each time the tests run. NPM, released in 2010, is the Node Package Manager for Node.js, a JavaScript Runtime Environment. According to NodeJS.org ## Harness June 2026 Product Updates DevFeed: [Harness June 2026 Product Updates]() Original publisher: [Read original article]() Author: Chinmay Gaikwad Published: 2026-07-03T00:00:00Z Content type: release Language: en Sources: [Harness Blog]() Topics: [Automation](), [Artificial Intelligence](), [AI Engineering](), [Playwright](), [Test automation](), [Testing]() Tags: [2026](), [agents](), [ai](), [ai-agents](), [ai-engineering](), [automation](), [playwright](), [product-updates](), [release](), [test-automation]() ### AI overview Harness's June 2026 product updates included 62 features, including Autonomous Worker Agents, parallel DAG pipeline execution, AI Test Automation with Playwright, AI SAST, feature flag updates, and AI Engineering Insights. ### Source excerpt See everything Harness shipped in June 2026, including Autonomous Worker Agents, parallel DAG pipelines, AI Test Automation with Playwright, AI SAST, feature fl | Blog ## SQGNE Lecture is tonight! Building a React Native Mobile Automated Test Framework with T.J. Maher DevFeed: [SQGNE Lecture is tonight! Building a React Native Mobile Automated Test Framework with T.J. Maher]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-05-20T14:12:23Z Content type: article Language: en Sources: [T.J. Maher]() Topics: [Mobile Testing](), [React Native](), [Testing](), [CI/CD](), [TypeScript](), [GitHub Actions]() Tags: [ci-cd](), [github-action](), [mobile-testing](), [react-native](), [sqgne](), [test-automation](), [testing](), [typescript]() ### AI overview The article announces a Software Quality Group of New England lecture on building an automated testing framework for React Native mobile applications. It describes using Wix's Detox to address loading, animation, timing, and test flakiness issues, with examples covering refactoring, maintainability, and CI/CD testing on iOS simulators and Android emulators. ### Source excerpt Are you in Boston? Come hear me talk about Building a a React Native Mobile Automated Test Framework in tonight's Software Quality Group of New England meeting in Burlington, MA: Registration Page: https://sqgne.org/n-May-2026.html Slide Deck: https://tinyurl.com/detox-demo-sqgne Taken from the Registration page: "Building a React Native Mobile Automated Test Framework Thomas F. - T.J. - Maher, Jr. "Wednesday May 20, 2025 6:30-8:00 PM - in person (free pizza!) Register Here "Check in between 6:00 and 6:30 to network "About the Presentation. . . "Writing automated tests for a React Native mobile application is notoriously difficult. Mobile components display on the page, but are not fully loaded. Lengthy animations and slow-loading components take a while to finish. Timing issues cause your automated tests to error out giving the appearance of flaky tests. "Thomas F. - T.J. - Maher, Jr. will be sharing his experience tackling these problems using the open-source mobile testing framework, Wix's Detox, designed specifically for testing React Native applications. "Setting up a mobile test automation framework. "Vibe-coding a toy React Mobile Login page app to test against ( tinyurl.com/detox-demo ). "How to reduce timing issues and flakiness in automated tests. "Refactoring code into tests, page objects & base pages, separating out credentials and message strings for easier maintainability. "Setting up automated tests in CI / CD for iOS simulators and Android emulators with GitHub Action Workflows. "How developers can test their code before they push it into the main branch". About the Speaker. . . "A former organizer of Ministry of Testing - Boston, Thomas (T.J.) Maher is a Software Development Engineer in Test (SDET) based in the Boston/South Shore area of Massachusetts, with a decade of experience building web + mobile test automation frameworks. His recent work includes architecting a mobile automation framework from the ground up using Detox and TypeScript for a Re ## Designing a custom AI agent for repetitive QA workflows DevFeed: [Designing a custom AI agent for repetitive QA workflows]() Original publisher: [Read original article]() Author: Rimple Sharma Published: 2026-05-18T06:01:01Z Content type: tutorial Language: en Sources: [Amex GBT Technology]() Topics: [AI Agent](), [Markdown](), [Parser](), [context]() Tags: [ai](), [ai-agent](), [ai-skills](), [context](), [markdown](), [parsing](), [software-testing](), [test-automation]() ### AI overview This tutorial explains how to design a custom AI agent for repetitive QA workflows. It focuses on encoding structured instructions in Markdown, including headers, rules, variables, examples, output schemas, and executable commands, and introduces the agent's processing loop. ### Source excerpt Part 2: Markdown as agent logic and the ReAct loop in action. In Part 1, I walked through the problem, repetitive QA work that resists pure scripting and the three pillars of a useful agent: input validation, context awareness, and a decision engine. I also showed why structured instructions beat plain text. This part is about how that structure gets encoded, how the loop runs, and what the impact looked like in practice. Why agents use Markdown When writing instructions for an agent, Markdown isn't just a formatting choice, it acts as a bridge between human-readable text and machine-processable logic. It's become a common format for agent communication because both humans and machines can work with it efficiently. But what most people miss... When you write agent instructions in Markdown, you're creating a weighted logic map, as well as just writing text. A few patterns that matter: 1. Semantic headers (#, ##) act as anchors for the agent's attention. Wrapping your mandatory rules under a clear header makes it far less likely the agent will overlook them mid-task. 2. Horizontal rules ( -- -) separate identity from instructions. Without this boundary, rules from one section bleed into another and the agent loses track of what governs what. 3. Bold keywords (**NEVER**, **ALWAYS**, **MANDATORY**) tend to be treated as hard constraints. Bold is a hard constraint. Italics are treated as a soft suggestion. 4. Blockquotes (>) are useful for examples. Wrapping an example in a blockquote signals to the agent that this is a reference, not a direct command. 5. {{curly_braces}} mark dynamic variables. They tell the agent that this part of the input will be filled in at runtime -- things like {{TICKET_ID}} or {{DATASET_NAME}} -- so it never substitutes a generic placeholder into a production file. 6. Fenced code blocks define output schemas. If you want the agent to always respond in a specific format, put that format in a code block. It treats it as a contract. 7. Inline code signa ## Designing a custom AI agent for repetitive QA workflows DevFeed: [Designing a custom AI agent for repetitive QA workflows]() Original publisher: [Read original article]() Author: Rimple Sharma Published: 2026-05-13T09:34:47Z Content type: tutorial Language: en Sources: [Amex GBT Technology]() Topics: [AI Agent](), [Automation](), [test](), [test data](), [configuration](), [pull-requests](), [consistency]() Tags: [ai-agent](), [ai-skills](), [automation](), [configuration](), [consistency](), [pull-requests](), [qa](), [software-testing](), [test-automation](), [test-data]() ### AI overview This article defines a repetitive QA workflow involving configuration updates, test-data additions, mapping checks, coverage validation, and pull requests. It argues that the main bottleneck is contextual decision-making and cross-file validation, which motivates designing a custom AI agent. ### Source excerpt Part 1: Core problem definition, three pillars of an effective agent & why structured instructions matter.Source: AI generated image Engineers on QA teams spend a disproportionate share of their time on work that follows a consistent pattern: updating configurations, modifying test artifacts, executing focused validations, and managing pull requests. The tasks are well-defined but the repetition adds up fast. Individually, none of this is complicated. But taken together, these tasks are: Repetitive Error-prone Hard to repeat reliably During my time in automation, I kept running into the same problem. Every release brought the same requirements. New datasets had to be added so the test suite could cover the scenarios tied to them. It was never a one-time effort. The same work had to be repeated across different combinations, every single time. The process typically looked like this: 1. Updating multiple configuration files. 2. Adding the corresponding test data. 3. Making sure everything was mapped correctly. 4. Validating coverage and consistency. 5. Committing the changes and raising a PR. Each step on its own was straightforward. But strung together and repeated across releases, it consumed a meaningful chunk of time that could have gone elsewhere. Problem breakdownFig 2.0 Pain of manual repetitive process (Source: AI generated image) Each step is straightforward. But together, context switching between files, making manual edits, double checking mappings, it added up to 30 to 60 minutes per release cycle in our case. Miss one mapping, introduce a typo, and the build breaks. It wasn't hard work, just repetitive. And that's exactly the kind of work that makes test suites brittle over time. Even with automation in place, every iteration still required someone to identify what had changed, figure out which files were affected, and make sure everything stayed consistent across the board. The framework we had was solid. Scripts handled the heavy lifting well. But there ## Reducing Failure-Analysis Work for Flaky End-to-End Test Suites DevFeed: [Reducing Failure-Analysis Work for Flaky End-to-End Test Suites]() Original publisher: [Read original article]() Author: Giuseppe Donati Web Test Automation Engineer Not a stereotypical Italian guy; Except Published: 2026-04-15T00:00:00Z Content type: opinion Language: en Sources: [Trivago]() Topics: [Testing](), [Test automation](), [ci](), [Selenium](), [GitHub](), [Latency](), [Server-side rendering](), [Microservice]() Tags: [artificial-intelligence](), [ci](), [github](), [integration](), [latency](), [quality-assurance](), [selenium](), [server](), [server-side-rendering](), [test-automation](), [tests]() ### AI overview The article describes the investigation burden caused by flaky end-to-end tests in trivago's Continuous Integration pipeline. Its extended suite has scenario-level success above 99% but workflow-level success of 20%, requiring frequent analysis of failures caused by flakiness, changing live data, preview-environment latency, and feature churn. ### Source excerpt Does 99.8% represent a good success rate in end-to-end test automation of a web application? What about 99.9%? Maybe yes, but when you have a test suite that has up to 1,000 scenarios, it means ... ## From a long list to a clear signal: baseline-driven accessibility reporting DevFeed: [From a long list to a clear signal: baseline-driven accessibility reporting]() Original publisher: [Read original article]() Author: Benjamin Bischoff Test Automation Engineer; Author; Speaker; Magician Github Profile Linkedin Profile Published: 2026-03-13T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [digital accessibility](), [Accessibility](), [axe-core](), [Test automation](), [Automation](), [Selenium](), [Testing](), [Extension]() Tags: [accessibility](), [accessibility-testing](), [automation](), [axe-core](), [eaa](), [european-accessibility-act](), [frontend](), [quality-assurance](), [selenium](), [test-automation](), [testing]() ### AI overview The article describes a baseline-driven approach to accessibility reporting. It extends an in-house test automation framework so new test runs can be compared with a snapshot of known issues on the main branch, helping teams distinguish regressions from existing technical debt and track changes more clearly. ### Source excerpt The output of most automated accessibility tests is a long list of violations. This format, while comprehensive, makes it difficult to distinguish new issues introduced in a feature branch from ... ## How I'm Using Agents for Development - January 2026 DevFeed: [How I'm Using Agents for Development - January 2026]() Original publisher: [Read original article]() Author: Sam Edwards Published: 2026-01-07T16:23:40Z Content type: opinion Language: en Sources: [Handstand Sam]() Topics: [Development](), [Claude](), [IntelliJ IDEA](), [ide](), [context window](), [Compose](), [GUI](), [YAML](), [Test automation]() Tags: [agents](), [claude](), [code](), [compose](), [context-window](), [development](), [gui](), [ide](), [idea](), [intellij](), [intellij-idea](), [junit](), [review](), [test-automation](), [updates](), [yaml]() ### AI overview A developer describes using agents with IntelliJ IDEA, Firebender, and Claude Sonnet 4.5 across Trailblaze projects. The article explains a Research, Plan, Implement workflow, including incremental commits, progress handoffs when the context window fills, refactoring, UI test automation, and building a Compose-based YAML editor. ### Source excerpt I'm currently sitting here with Intellij IDEA IDE open with 3 workspaces (different clones of the Trailblaze project). In each one of them I'm using Firebender with the Claude Sonnet 4.5 model. As I'm writing this I just toggled back over to IDE and made sure all my agents are still running. I've been hesitant [...] ## Maestro's Architecture for Simplifying Mobile Test Automation DevFeed: [Maestro's Architecture for Simplifying Mobile Test Automation]() Original publisher: [Read original article]() Author: Leland Takamine Published: 2025-09-25T00:00:00Z Content type: article Language: en Sources: [mobile.dev - Medium]() Topics: [Mobile](), [Testing](), [Test automation](), [YAML](), [Accessibility](), [Open Source](), [Command-line interface](), [Android]() Tags: [accessibility](), [adb](), [android](), [flutter](), [ionic](), [maestro](), [mobile](), [mobile-test-automation](), [open-source](), [react-native](), [test-automation](), [yaml]() ### AI overview The article explains Maestro's architecture for mobile test automation. It describes one-line installation without separate dependencies, drivers, or SDKs; a Kotlin implementation of the ADB protocol called dadb; self-installing mobile drivers; and support for native, React Native, Flutter, and Ionic applications through the device accessibility layer. ### Source excerpt Discover how Maestro is revolutionizing mobile test automation with zero setup, universal compatibility, and human-readable YAML syntax. ## Google Maps UI Test Automation with Maestro - Full Tutorial DevFeed: [Google Maps UI Test Automation with Maestro - Full Tutorial]() Original publisher: [Read original article]() Author: Leland Takamine Published: 2025-07-01T16:23:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [Testing](), [Test automation](), [Google Maps](), [Automation](), [YAML](), [Tutorial](), [Mobile]() Tags: [automation](), [cli](), [google-maps](), [maestro](), [maps](), [open-source](), [test-automation](), [tutorial](), [ui-testing](), [yaml]() ### AI overview A step-by-step tutorial for automating a Google Maps UI test with the open-source Maestro framework. It covers installing the Maestro CLI, launching the app with clearState, tapping, typing, swiping, scrolling until an element is visible, validating with regex, and running a complete YAML flow. ### Source excerpt Discover step-by-step automated Google Maps UI testing with Maestro: complete YAML guide to tap, input, swipe, scroll commands and fast assertions. ## Tailor-made browser extensions for increased testing efficiency DevFeed: [Tailor-made browser extensions for increased testing efficiency]() Original publisher: [Read original article]() Author: Raymond Saba I'm an SDET who enjoys building test automation; Finding Ways Published: 2025-04-23T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Testing](), [Browser Extension](), [Extension](), [Development]() Tags: [browser](), [development](), [extensions](), [quality-assurance](), [reverse-engineering](), [test-automation](), [testing]() ### AI overview The article describes how trivago's QA team used custom browser extensions to support exploratory testing, reduce cumbersome testing processes, and save time. It discusses an extension created through reverse engineering to inspect Google Tag Manager data-layer values and another that identified the version of the trivago website being viewed. ### Source excerpt When doing exploratory testing on a web application, the nature of activities involves discovering things and not repeating the same patterns. However, there might be aspects that could be impro... ## The Testing Pyramid DevFeed: [The Testing Pyramid]() Original publisher: [Read original article]() Author: Nelson Djalo Published: 2024-08-05T16:01:01Z Content type: tutorial Language: en Sources: [Amigoscode Newsletter]() Topics: [Testing](), [Java](), [Test automation](), [Development](), [Programming]() Tags: [development](), [java](), [junit](), [selenium](), [test-automation](), [testing]() ### AI overview A guide to the testing pyramid for Java applications, explaining the roles of unit, integration, end-to-end, and UI tests. It also introduces Java testing frameworks including JUnit, TestNG, and Selenium. ### Source excerpt Layered Testing for Robust Software Development ## QA Meetup - 2nd Edition: Presentations and Recap DevFeed: [QA Meetup - 2nd Edition: Presentations and Recap]() Original publisher: [Read original article]() Author: Saurav Sharma QA Lead; Loves APIs; Databases; All Things Backend; Cricket fanatic Linkedin profile Published: 2024-05-21T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Testing](), [Test automation](), [Open Source]() Tags: [engineering-culture](), [meetup](), [open-source](), [qa](), [quality-assurance](), [recap](), [release](), [test-automation]() ### AI overview A recap of trivago's second QA Meetup, held on April 25, 2024, with more than 65 attendees. The article summarizes three presentations covering a custom test reporting solution, quality coaching, and QA ownership of the app release process, along with the event's discussions and social activities. ### Source excerpt The 2nd edition of the qa Meetup was held at the trivago campus on April 25th, 2024 with over 65 attendees and was a huge success. ## Testing with Accessibility Scanner DevFeed: [Testing with Accessibility Scanner]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2024-02-16T03:38:54.088000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [Testing](), [Android](), [App](), [Google Play](), [Flutter](), [React Native](), [PWA]() Tags: [accessibility](), [accessibility-testing](), [android](), [flutter](), [google-play](), [pwa](), [react-native](), [test-automation](), [testing]() ### AI overview This tutorial explains how to use Accessibility Scanner for semi-automated accessibility testing of Android apps. The tool can identify issues involving content labels, touch target size, clickable items, and text and image contrast, but it cannot detect every accessibility problem, so manual testing remains necessary. It can be used with native Android apps, Flutter and React Native apps, and PWAs. ### Source excerpt When I talk about accessibility with Android developers, I often hear that some easy-to-use tests should automatically catch every possible accessibility issue. And I get it. That would make the whole topic of accessibility so much easier and straightforward. But the truth is that automated testing only catches some things. Studies suggest that the maximum percentage of caught accessibility issues is 40-50%. Deque, the company that develops the aXe accessibility tool, claims that the number is 57% in their study of automated accessibility tools. These studies have been performed with websites, but based on my experience, I have no reason to believe that the number would be higher on Android. So manual testing is always needed. But for that 40-57% (or whatever the exact number is on Android accessibility testing), there are some tools to use. One of them is Accessibility Scanner, and in this blog post, I'll discuss how to test your app with it. Let's start with what it is. What Is Accessibility Scanner Accessibility Scanner is a helpful tool for semi-automated accessibility testing. It's an app which can catch issues from the following categories: Content labels Touch target size Clickable items Text and image contrast It also suggests how to fix some of its findings and provides more info about the issues. However, it does not find every possible accessibility issue and thus does not guarantee the accessibility of your app. Manual testing is still needed. I keep saying this because I've seen these claims so many times that "Well, our test automation didn't find any accessibility issues, so our app is accessible". One great thing is that you can use Accessibility Scanner with any Android app - it can be a native Android app or built with cross-platform technologies such as Flutter or React Native. Or it can even be a PWA - Progressive Web App. Using Accessibility Scanner Installation To use the Accessibility Scanner, you must first download it from Google Play: Acces ## End-to-end tests retry strategies DevFeed: [End-to-end tests retry strategies]() Original publisher: [Read original article]() Author: Giuseppe Donati Web Test Automation Engineer Not a stereotypical Italian guy; Except Published: 2023-09-27T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Testing](), [Test automation](), [GitHub Actions](), [CI/CD](), [Continuous Deployment (CD)](), [Front end](), [web applications]() Tags: [continuous-deployment](), [core](), [feature](), [frontend](), [github-actions](), [pull-requests](), [quality-assurance](), [test-automation](), [tests]() ### AI overview This article describes how trivago's frontend QA team uses different end-to-end test retry strategies in GitHub Actions. It explains unconditional retries for core tests, filtered retries for specific failure causes in extended tests, and manual retries for a subset of scenarios, balancing stable results, pull-request confidence, and feedback speed. ### Source excerpt Why should you retry all tests on failure? Why not? This article will not go into details, listing pros and cons of each approach. There are already enough ## QA meetup: Presentations Summary DevFeed: [QA meetup: Presentations Summary]() Original publisher: [Read original article]() Author: Saurav Sharma QA Lead; Loves APIs; Databases; All Things Backend; Cricket fanatic Linkedin profile Published: 2023-08-02T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Testing](), [Robot Framework](), [Test automation](), [observability](), [API](), [Mainframe](), [API Economy]() Tags: [api-testing](), [engineering-culture](), [events](), [open-source](), [qa](), [quality-assurance](), [test-automation](), [testing]() ### AI overview A summary of trivago's QA meetup held on June 22, 2023, covering presentations on Robot Framework, mainframe test modernization, observability, API testing, and the Karate framework, followed by networking among attendees. ### Source excerpt Meetups are one of our favourite events at trivago. They give us the opportunity to learn, share knowledge & experience, as well as network with fellow professionals and enthusiasts in the i... ## How we improved reporting and monitoring of test automation results DevFeed: [How we improved reporting and monitoring of test automation results]() Original publisher: [Read original article]() Author: Giuseppe Donati Web Test Automation Engineer Not a stereotypical Italian guy; Except Published: 2023-02-15T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Testing](), [Test automation](), [GitHub Actions](), [Selenium](), [CI/CD](), [Cloud](), [Kafka](), [elasticsearch](), [kibana](), [logstash](), [Grafana](), [Cucumber]() Tags: [article](), [elasticsearch](), [frontend](), [gcp](), [github-actions](), [grafana](), [kafka](), [kibana](), [logstash](), [monitoring](), [quality-assurance](), [selenium](), [test-automation]() ### AI overview The article describes trivago's updated system for executing, reporting, and monitoring Selenium-based end-to-end tests. It covers GitHub Actions workflows, custom runners on Google Cloud, cloud report storage, Kafka and Logstash processing, Elasticsearch and Kibana visualization, and Grafana and Slack alerting. ### Source excerpt Over the last few years, we completely refactored what was described in our previous article about how we use the ELK sta... ## The Cyclic Nature Of In-House Tooling DevFeed: [The Cyclic Nature Of In-House Tooling]() Original publisher: [Read original article]() Author: Doximity Published: 2022-09-28T17:00:00Z Content type: opinion Language: en Sources: [Doximity]() Topics: [Tooling](), [CI/CD](), [Testing](), [Automation]() Tags: [automation](), [ci-cd](), [test-automation](), [tooling](), [workflows]() ### AI overview The article explains how Doximity's Infrastructure Automation team treats internal developers as customers and its tooling and services as products. It presents a product-lifecycle approach to discovering needs, prioritizing requests, and improving developer productivity and production deployment processes. ### Source excerpt Joseph M. Juran popularized the concept of considering members of an organization who are stakeholders concerning another individual or group's products or services to be internal customers. In contrast, and as suggested by the name, external customers are those whose relationship to the organization is not through employment but by purchasing the organization's products or services. While a company's focus primarily lies on the external, teams within the organization must often focus on both. In this article, we'll discuss the marketing initiatives surrounding the release of an internal product. At Doximity, we have various developers focused on many products and services. On the Infrastructure Automation team, we aim to design tooling and workflows that directly assist our internal customers, with the downstream effect benefiting those who are external. Our team's core mission is to build, maintain, and support test tools and frameworks, CI infrastructure and pipelines, and all test automation processes. Our overall goal is to make developers more productive while simplifying the process of deploying to production. While the utilities and services managed by our team are not directly customer-facing, their impact helps reduce friction in the creation of products that are. Being an infrastructure team spanning support across R&D, we're divided between our web, mobile, and data business units, myself aligned with the latter. Therefore, data engineers and scientists are my primary internal customers, with CI/CD users as a whole being my secondary. How do I determine where my developer time is best spent to support them? How can I generate new ideas that benefit my customers? How should I prioritize the myriad of requests sent my way? Suppose I do consider the employees I support to be internal customers. In that case, I should also treat the utilities and services I create and manage as products that adhere to a product life cycle of sorts. This cycle emulates proced ## Best Principles for Successful Test Automation (API and UI) DevFeed: [Best Principles for Successful Test Automation (API and UI)]() Original publisher: [Read original article]() Published: 2022-06-14T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Testing](), [Test automation](), [API](), [ui](), [maintenance]() Tags: [api](), [maintenance](), [software-testing](), [standards](), [test-automation](), [testing](), [ui](), [workshop](), [workshop-learning-programming]() ### AI overview This workshop presents principles for successful API and UI test automation. It covers software testing stages from definition through maintenance and discusses using ISTQB standards to work efficiently within project scope and deadlines. ### Source excerpt Aligning our testing activities with ISTQB standards helps us to perform efficiently and cope with project scope and deadlines. In this workshop we will go over software testing stages starting from definition to maintenance. ## Android Architecture: Runtime Centric Thinking DevFeed: [Android Architecture: Runtime Centric Thinking]() Original publisher: [Read original article]() Author: SystemDotRun Published: 2021-11-08T00:00:00Z Content type: opinion Language: en Sources: [SystemDotRun]() Topics: [Android](), [Testing](), [Test automation]() Tags: [android](), [android-architecture](), [architecture](), [blog-post](), [complexity](), [production](), [test-automation]() ### AI overview This blog post presents a high-level overview of a runtime-centric architecture for Android applications. Drawing on the author's experience using it in two production projects, it discusses Android component lifecycles, instantiation, test automation, threading, fragments, and ways to reduce run, build, and test-time complexity. ### Source excerpt For at least 7 years I have been playing with "alternative" Android architectures in a professional context. This blog post is a brief overview to an architecture I have been using for the last two production projects for which I was Android Lead and outlines a high level introduction to a production-level runtime-centric application. I will note at the start I am not attempting to persuade anyone to use this approach over any other, but rather: Understand my own thoughts better through writing Share something which has worked well for me which others may find interesting I imagine it may raise more questions than it answers, and if so please leave a comment and I can expand any concepts if desired. Motivation My original motivation to think about alternative Android architectures was due to me often feeling there were personally unexplored and advantageous ways to structure certain types of applications on an OS like Android, which has a number of idiosyncrasies including application component lifecycles, application component instantiation, difficulty in test automation and so on. In the 12 years I have been a professional Android developer I have seen some common examples of where complexity has been layered on top of some of these areas in the aim of making them easier to deal with on a day to day basis when often an arguably simpler divergent approach has been overlooked. For some quick fire examples I would include here: Test time OS level faking frameworks vs OS abstraction at build time Complex lifecycle aware asynchronous view-level listeners as opposed to rendering immutable states Complex 3rd party dependencies utilised for threading purposes as opposed to thread abstraction Fragments vs thin views cough I found that there were often common solutions to common problems but which often came with an additional baggage of increased run / build / test time complexity. Instead of thinking in terms of surface level solutions my mind kept wondering back to think ## \[Перевод\] Три паттерна для улучшения работы с автотестами DevFeed: [\[Перевод\] Три паттерна для улучшения работы с автотестами]() Original publisher: [Read original article]() Author: laechoppe (Badoo) Published: 2021-05-20T17:18:27Z Content type: article Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [iOS](), [Wiki]() Tags: [badoo](), [ios](), [patterns](), [qa](), [software-testing](), [tag-23c525fe15c9](), [tag-e932065bc8da](), [tag-e95ee8b94dca](), [test-automation]() ### AI overview This article describes three process patterns for improving automated testing in mobile application development. Drawing on experience at Badoo and Bumble, it explains how automation supported weekly releases and how teams addressed recurring collaboration and knowledge-sharing difficulties. ### Source excerpt Меня зовут Владислав Романенко, я старший iOS QA Engineer в Badoo и Bumble. Несколько лет назад мы начали активнее использовать автотесты в процессе разработки, но столкнулись с несколькими трудностями на этом пути. Логичный вопрос: почему мы занялись автоматизацией тестирования? Ответ кроется в еженедельном выпуске новых версий наших мобильных приложений. QA отделу приходится тестировать новые фичи, их интеграцию в приложение и заниматься регрессионным тестированием. За неделю нужно проводить как минимум одно комплексное регрессионное тестирование, что довольно утомительно. Все эти трудности мы преодолели с помощью автоматизации, которая помогла нам выпускать новые версии быстрее и без потери качества. Подробнее об автоматизации мобильного тестирования -- в докладе наших коллег. Сложности в разработке часто решаются с помощью паттернов -- обобщённых решений для часто возникающих проблем в заданном контексте. То же и с автоматизацией тестирования, есть даже удобное wiki-описание. В этой статье мы поговорим о паттернах процессов (Process Patterns). Они помогают организовать и улучшить процесс автоматизации тестирования. Без дальнейших предисловий перейдём к трудностям, с которыми мы боролись, и рекомендациям по их преодолению с помощью тех самых паттернов. Замечу, что это не единственные проблемы, которые у нас были и есть. Но в рамках данной статьи я решил остановится именно на приведенных ниже пунктах. Читать дальше ## Interview for BrowserStack's Breakpoint 2020 Conference DevFeed: [Interview for BrowserStack's Breakpoint 2020 Conference]() Original publisher: [Read original article]() Author: Matthias Endler Published: 2020-07-03T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Testing](), [Test automation](), [Continuous Delivery (CD)](), [Cucumber](), [Open Source]() Tags: [bdd](), [conference](), [continuous-delivery](), [engineering-culture](), [interview](), [open-source](), [qa](), [release-engineering](), [test-automation](), [testing]() ### AI overview This article announces Benjamin Bischoff's BrowserStack interview and talk for the virtual Breakpoint 2020 testing summit. It introduces his work in test automation at trivago and describes the company's technical and procedural changes toward more efficient continuous delivery. ### Source excerpt After 15 years as a game/application developer and trainer, Benjamin decided to make test automation his career. He's currently a Test Automation Engineer in trivago's core QA team. Benj... [Next page]()