# Selenium Published articles for Selenium. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Maestro vs Appium: The Benchmark DevFeed: [Maestro vs Appium: The Benchmark]() Original publisher: [Read original article]() Author: Manu Armani Published: 2026-08-17T10:00:00Z Content type: comparison Language: en Sources: [mobile.dev - Medium]() Topics: [Benchmark](), [Mobile](), [cross-platform](), [AI Agent](), [Command-line interface](), [YAML](), [Selenium]() Tags: [agent](), [ai](), [ai-coding](), [android](), [appium](), [benchmark](), [claude](), [claude-code](), [cli](), [cost](), [cross-platform](), [ios](), [javascript](), [maestro](), [maintenance](), [mcp](), [python](), [selenium](), [vs]() ### AI overview A comparison of Maestro and Appium for mobile UI testing across setup, syntax, waits, flakiness, platform coverage, AI agent support, and maintenance cost. Maestro uses declarative YAML flows with built-in waits and retries, while Appium uses code-based tests and a driver architecture covering more platforms. The article also describes MCP-based device control and cases where Appium is the better fit. ### Source excerpt A side-by-side comparison of Maestro and Appium across setup, syntax, waits, flakiness, cross-platform coverage, AI agent support, and maintenance cost. ## BrowserStack Newsletter July 2026 DevFeed: [BrowserStack Newsletter July 2026]() Original publisher: [Read original article]() Author: Devanshi Jain Published: 2026-08-05T10:02:29Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Testing](), [Test automation](), [Artificial Intelligence](), [Playwright](), [Selenium](), [Cypress](), [ide](), [Application Performance Management (APM)](), [dashboards](), [Extension](), [Emulator](), [simulator]() Tags: [2026](), [agentic-ai](), [automation](), [automation-testing](), [cursor](), [cypress](), [features](), [ide](), [newsletter](), [product](), [selenium](), [testing]() ### AI overview BrowserStack's July 2026 newsletter announces Test Companion, an agentic AI feature for IDE-based test automation, and BrowserStack Load Testing, which combines backend load generation, real-browser performance, and APM metrics. It also highlights updates for certificates, screenshots, emulators, simulators, mobile browsers, Chrome extensions, audio logs, and diagnostic data. ### Source excerpt Read what's new at BrowserStack in July 2026 - New launches, product features, and more! ## Breakpoint 2026 Speaker Spotlight: Andrew Knight DevFeed: [Breakpoint 2026 Speaker Spotlight: Andrew Knight]() Original publisher: [Read original article]() Author: Shweta Chhillar Published: 2026-05-08T10:14:54Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Testing](), [Software Testing](), [Artificial Intelligence](), [Behavior-driven development](), [Automation](), [Selenium](), [Playwright](), [MCP Server](), [Open Source]() Tags: [2026](), [ai](), [automation](), [breakpoint](), [breakpoint-spotlight](), [browser](), [enterprise](), [mcp](), [mcp-server](), [open-source](), [qa](), [quality-engineering](), [selenium](), [software](), [software-testing](), [test-coverage](), [testing](), [webdriver]() ### AI overview This speaker spotlight discusses how Andrew Knight combines open-source advocacy with enterprise software testing. It focuses on AI-powered test generation, behavior-driven development, context engineering, human oversight, and tools such as Selenium WebDriver, Playwright AI tooling, CLI skills, and an MCP server. ### Source excerpt Explore how Andrew Knight is using AI, behavior-driven development, and context engineering to reshape enterprise software testing at BrowserStack Breakpoint 2026. This speaker spotlight dives into AI-powered QA, test automation, and the future of modern quality engineering. ## 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 ... ## Case Study: How Eneco Upgraded from Manual QA to Automated Testing with Maestro DevFeed: [Case Study: How Eneco Upgraded from Manual QA to Automated Testing with Maestro]() Original publisher: [Read original article]() Author: Jake Krupski Published: 2025-04-09T00:00:00Z Content type: article Language: en Sources: [mobile.dev - Medium]() Topics: [Testing](), [Automation](), [Mobile](), [Selenium]() Tags: [appium](), [automated](), [automation](), [automation-tools](), [case-study](), [maestro](), [mobile](), [open-source](), [qa](), [selenium](), [testing]() ### AI overview A case study of Eneco's transition from manual QA to automated testing across its mobile app and web portal. The team evaluated Appium, Tosca, and Maestro, with Maestro selected for its reported speed, reliability, simpler learning curve, and integration fit. The article also describes internal adoption after demonstrations to QA teams and company leadership. ### Source excerpt At Mobile.dev, we love hearing stories from teams putting Maestro to work in the real world - and Randy Sie and his team at Eneco have a story that's representative of what many... ## New Chainguard Images November 2024: Bun, CockroachDB, Open Liberty DevFeed: [New Chainguard Images November 2024: Bun, CockroachDB, Open Liberty]() Original publisher: [Read original article]() Published: 2024-12-18T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [Bun](), [CockroachDB](), [open liberty]() Tags: [bun](), [chainguard-images](), [cockroachdb](), [container-images](), [open-liberty](), [selenium](), [zero-cves]() ### AI overview Chainguard announces 70 container images built in November 2024, including images for Open Liberty, CockroachDB, and Bun. The article describes the new images and their stated runtime, database, and JavaScript-tooling use cases. ### Source excerpt Check out the new zero-CVE Chainguard Images built in November 2024, including offerings for Bun, CockroachDB, Open Liberty, Selenium, and more. ## Cutting over-provisioning with KEDA: cron, external triggers, and a Selenium Grid queue DevFeed: [Cutting over-provisioning with KEDA: cron, external triggers, and a Selenium Grid queue]() Original publisher: [Read original article]() Published: 2024-09-04T00:00:00Z Content type: article Language: en Sources: [Andika Ahmad Ramadhan -- Blog]() Topics: [autoscaling](), [Kubernetes](), [Selenium](), [Testing](), [HashiCorp Vault](), [migration](), [Prometheus]() Tags: [autoscaling](), [cost](), [hashicorp-vault](), [kubernetes](), [migration](), [prometheus](), [selenium](), [testing]() ### AI overview An experience report on using KEDA cron and external scalers to reduce idle Kubernetes capacity. It describes scaling workloads by schedules, queue depth, and Prometheus queries, including a Selenium Grid whose browser nodes scale with queued test sessions. The article also discusses migration from VMs to Kubernetes and a Vault-related operator bug discovered in production. ### Source excerpt How I used KEDA cron scalers, external triggers, and Selenium Grid queue scalers to stop paying for idle replicas in production. ## 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 ## New Chainguard Images for Selenium, Gotenberg and more DevFeed: [New Chainguard Images for Selenium, Gotenberg and more]() Original publisher: [Read original article]() Published: 2024-03-11T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [Selenium](), [releases](), [container images](), [Security & compliance, Cloud security]() Tags: [argocd](), [chainguard-images](), [container-images](), [container-security](), [cve](), [gotenberg](), [security](), [selenium](), [sigstore]() ### AI overview Chainguard describes new Chainguard Images released in February, highlighting a minimal, CVE-free Selenium container image and additional images such as Gotenberg. The article explains Chainguard's approach to rebuilding open source packages and propagating updates. ### Source excerpt Unlock the latest Chainguard Images for Selenium, Gotenberg, and more, boosting your cloud security with zero-CVE, minimal container solutions. ## Updating to .NET 8, updating to IHostBuilder, and running Playwright Tests within NUnit headless or headed on any OS DevFeed: [Updating to .NET 8, updating to IHostBuilder, and running Playwright Tests within NUnit headless or headed on any OS]() Original publisher: [Read original article]() Author: Scott Hanselman Published: 2024-03-07T01:12:13Z Content type: tutorial Language: en Sources: [Scott Hanselman]() Topics: [Playwright](), [.NET](), [Testing](), [Browser Automation](), [Integration testing](), [ASP.NET](), [Selenium](), [GitHub Actions]() Tags: [asp-net](), [automation-testing](), [browser](), [ci-cd](), [debug](), [devops](), [dotnetcore](), [integration](), [linux](), [net](), [playwright](), [selenium](), [testing](), [tests](), [unit-testing](), [visual-studio](), [vs-code](), [web](), [windows]() ### AI overview A tutorial on updating a .NET application to .NET 8 and running Playwright browser tests through NUnit. It explains the transition from IWebHostBuilder to IHostBuilder and describes cross-platform, headless or headed testing across local systems, containers, and CI environments. ### Source excerpt I've been doing not just Unit Testing for my sites but full on Integration Testing and Browser Automation Testing as early as 2007 with Selenium. Lately, however, I've been using the faster and generally more compatible Playwright. It has one API and can test on Windows, Linux, Mac, locally, in a container (headless), in my CI/CD pipeline, on Azure DevOps, or in GitHub Actions. For me, it's that last moment of truth to make sure that the site runs completely from end to end. I can write those Playwright tests in something like TypeScript, and I could launch them with node, but I like running end unit tests and using that test runner and test harness as my jumping off point for my .NET applications. I'm used to right clicking and "run unit tests" or even better, right click and "debug unit tests" in Visual Studio or VS Code. This gets me the benefit of all of the assertions of a full unit testing framework, and all the benefits of using something like Playwright to automate my browser. In 2018 I was using WebApplicationFactory and some tricky hacks to basically spin up ASP.NET within .NET (at the time) Core 2.1 within the unit tests and then launching Selenium. This was kind of janky and would require to manually start a separate process and manage its life cycle. However, I kept on with this hack for a number of years basically trying to get the Kestrel Web Server to spin up inside of my unit tests. I've recently upgraded my main site and podcast site to .NET 8. Keep in mind that I've been moving my websites forward from early early versions of .NET to the most recent versions. The blog is happily running on Linux in a container on .NET 8, but its original code started in 2002 on .NET 1.1. Now that I'm on .NET 8, I scandalously discovered (as my unit tests stopped working) that the rest of the world had moved from IWebHostBuilder to IHostBuilder five version of .NET ago. Gulp. Say what you will, but the backward compatibility is impressive. As such my code for Progr ## How BRYTER Achieved Increased Developer Experience, Ownership, Product Quality, and Engineering Effectiveness through Continuous Deployments DevFeed: [How BRYTER Achieved Increased Developer Experience, Ownership, Product Quality, and Engineering Effectiveness through Continuous Deployments]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-09-22T08:00:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [Deployment](), [Developer experience](), [Testing](), [Selenium](), [TypeScript]() Tags: [case-study](), [case-study-continuous-deployment-developer-experience-developer-productivity-leadership-practic](), [deployment](), [deployments](), [developer-experience](), [ownership](), [qa](), [quality](), [resilience](), [selenium](), [typescript]() ### AI overview This case study describes how BRYTER addressed a monolithic deployment process in which deployments occurred twice weekly and were managed by QA. The resulting lack of visibility, ownership, and understanding affected engineering teams, testing, and resilience. BRYTER began moving toward continuous deployments and created a dedicated Developer Experience Team. ### Source excerpt How BRYTER Achieved Increased Developer Experience, Ownership, Product Quality, and Engineering Effectiveness through Continuous Deployments BRYTER, a German LegalTech scale-up, faced challenges with its monolithic deployment process and limited understanding of the deployment process within its engineering teams. Deployments occurred only twice a week and were managed by the QA team, leading to a lack of visibility and ownership among the other teams. ## Retry flaky tests with dotnet test and PowerShell DevFeed: [Retry flaky tests with dotnet test and PowerShell]() Original publisher: [Read original article]() Author: {"twitter"=\>"hlaueriksson"} Published: 2023-03-26T19:00:00Z Content type: tutorial Language: en Sources: [Henrik Lau Eriksson]() Topics: [PowerShell](), [.NET](), [Command-line interface](), [Smoke Tests](), [Playwright](), [Selenium]() Tags: [c-sharp](), [cli](), [configuration](), [dotnet](), [flaky](), [jenkins](), [mstest](), [nunit](), [playwright](), [powershell](), [retry](), [selenium](), [test](), [testing](), [unit-tests](), [xunit]() ### AI overview This tutorial presents a PowerShell script that uses dotnet test and TRX result files to track failed tests, retry them, report the final result, and allow a configured percentage of failures. It demonstrates the script with NUnit, MSTest, and xUnit. ### Source excerpt Introducing test.ps1, a script for running flaky tests - Keeps track of failing tests and retries them - Notifies the test framework of the current retry iteration - Makes it possible to accept a certain percentage of failing tests - Outputs the test result in a coherent way ## 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... ## Focus Week Case Study: Bringing E2E Tests into the CI Pipeline DevFeed: [Focus Week Case Study: Bringing E2E Tests into the CI Pipeline]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2021-12-25T12:34:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [CI/CD Pipeline](), [Selenium](), [test](), [AWS Lambda]() Tags: [aws-lambda](), [case-study](), [case-study-collaboration-culture-ensemble-programming-team-programming-developer-productivity](), [ci-cd](), [e2e](), [selenium](), [tests]() ### AI overview This case study describes BRYTER's effort to bring Selenium-based end-to-end tests into its CI/CD pipeline. The tests were previously maintained by QA in a separate repository and run manually, with problems including slowness and flakiness. The team identified stabilization, parallel execution using AWS Lambda, closer alignment with production code, and CI/CD integration as key areas of work. ### Source excerpt Focus Week Case Study: Bringing E2E Tests into the CI Pipeline In my last article, I wrote about focus weeks and how my team is currently doing them at BRYTER. Today, I want to share a case study of our latest focus week. ## Windows Container on K8s Clusters DevFeed: [Windows Container on K8s Clusters]() Original publisher: [Read original article]() Author: Sebastián Gómez Published: 2021-12-03T09:27:27Z Content type: tutorial Language: en Sources: [Blog - Container Solutions]() Topics: [Kubernetes](), [Containers](), [Windows](), [.NET Framework](), [Amazon EKS](), [Docker](), [Selenium](), [Tool](), [PowerShell](), [Package manager](), [Spring Boot](), [Java]() Tags: [build](), [containers](), [docker](), [java](), [kubernetes](), [net-framework](), [nuget](), [powershell](), [selenium](), [spring-boot](), [windows]() ### AI overview This article describes a cloud migration scenario involving Windows containers and a .NET Framework 4.8 UI-testing application that uses Selenium to start a browser. It also discusses bringing Docker images into a managed Kubernetes cluster on Amazon EKS, alongside existing React/Redux and Java Spring Boot applications. ### Source excerpt I recently came across a fun and interesting challenge. In the latest project I joined, a team wanted to do a "lift & shift to the cloud". As a Cloud Native engineer I've seen this pattern fairly often, although it never means quite the same thing. ## Автоматизация тестирования мобильных приложений. Часть 2: предусловия, верификация элементов и независимость шагов DevFeed: [Автоматизация тестирования мобильных приложений. Часть 2: предусловия, верификация элементов и независимость шагов]() Original publisher: [Read original article]() Author: barman\_mo (Badoo) Published: 2021-03-16T14:17:18Z Content type: tutorial Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [Mobile](), [Selenium]() Tags: [automation](), [mobile](), [qa](), [selenium](), [tag-23c525fe15c9]() ### AI overview The second part of an article about mobile application test automation practices at Badoo and Bumble. It discusses verifying element state changes, configuring test preconditions, developing steps for simple and complex actions, and verifying optional elements, with a focus on making tests faster and more stable. ### Source excerpt Меня зовут Дмитрий Макаренко, я Mobile QA Engineer в Badoo и Bumble: занимаюсь тестированием новой функциональности в наших приложениях вручную и покрытием её автотестами. За последние два года подход к автоматизации тестирования в нашей компании сильно изменился. Количество людей, активно вовлечённых в разработку тестов, увеличилось с десяти до 40 человек. А любая новая функциональность в приложениях теперь обязательно должна быть покрыта тестами до релиза. В таких условиях нам очень важно разрабатывать тесты настолько быстро, насколько это возможно. И делать их при этом стабильными -- чтобы поддержка не отнимала у нас много времени. Мы решили поделиться практиками, которые помогают нам ускорять разработку тестов и повышать их стабильность. В первой части статьи мы рассказали о роли автоматизации в наших процессах, деталях фреймворка и подробно разобрали три практики, которые мы применяем при создании автотестов. Во второй части будем разбираться с верификацией изменения состояния элементов, настройкой предусловий тестов, разработкой шагов для простых и сложных действий, а также с верификацией необязательных элементов (которую обязательно нужно делать :)). Читать далее ## API для QA: тестируем фичи без доступа к коду DevFeed: [API для QA: тестируем фичи без доступа к коду]() Original publisher: [Read original article]() Author: SergeyRyabko (Badoo) Published: 2020-11-19T13:56:20Z Content type: article Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [API](), [Selenium]() Tags: [api](), [badoo](), [php](), [qa](), [selenium]() ### AI overview The article introduces Badoo's QAAPI, a tool intended to let engineers and automated tests influence application parameters without changing source code. It describes the testing problem in staging and production environments, including time-dependent features, and states requirements such as simplicity, broad test support, safety, and documentation. ### Source excerpt Многие фичи приложения невозможно быстро протестировать, не меняя исходный код. Представьте типичную задачу, с которой может столкнуться каждый разработчик: через три дня после регистрации пользователю нужно предложить купить премиум-доступ к продукту со скидкой. Чтобы проверить, работает ли это промо, нужно зарегистрировать тестового пользователя и подождать три дня до появления заветного окошка. Очевидно, что разработчик не будет столько ждать. Он просто сменит в коде значение константы, которая задаёт временной интервал, с трёх дней на 20 секунд -- и получит результат почти мгновенно. Допустим, данные для промопредложения отдаёт сервер, а отрисовывается оно на клиенте. Если серверный тестировщик работает в среде, которая допускает манипуляции с кодом, он тоже быстро справится с задачей. Но как только она окажется там, где возможность менять код отсутствует (стейджинг, продакшен), возникнет проблема. Читать далее ## Access Selenium Test Screenshots on failed GitLab Pipeline Steps DevFeed: [Access Selenium Test Screenshots on failed GitLab Pipeline Steps]() Original publisher: [Read original article]() Published: 2020-10-14T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [GitLab](), [Selenium](), [Docker]() Tags: [chrome](), [ci](), [docker](), [docker-image](), [gitlab](), [node](), [pipeline](), [screenshots](), [selenium](), [test](), [tooling]() ### AI overview This tutorial explains how to configure GitLab pipeline artifacts to retain Selenium test screenshots when a CI step fails. It also mentions a Protractor-based end-to-end setup using a Cypress Docker image with Node.js and Chrome configuration. ### Source excerpt Lorem ipsum dolor sit amet ## Rails Console and Test Mode DevFeed: [Rails Console and Test Mode]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-02-19T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [test](), [Testing]() Tags: [console](), [environment](), [factorybot](), [rails](), [selenium](), [test](), [testing]() ### AI overview This short tutorial shows how to launch the Rails console in test mode with RAILS_ENV=test rails c. This lets developers inspect the test environment and work directly with FactoryBot to experiment with test factories. ### Source excerpt This one is a short one but a good one. One really useful trick is to launch Rails console in test mode: ❯ RAILS_ENV=test rails c Running via Spring preloader in process 41705 Loading test environment (Rails 6.0.2.1) irb: warn: can't alias context from irb_context. You can check the Rails environment this way: 2.7.0 :001 > Rails.env "test" The benefit to this is that you can work directly with FactoryBot and experiment with factories: 2.7.0 :002 > project = FactoryBot.create(:project, name: "Scott's Project") FactoryBot is installed via Gemfile and locked into test environment only (which is why you need to launch Rails console in test mode): group :test do # Adds support for Capybara system testing and selenium driver gem "capybara", ">= 2.15" gem "selenium-webdriver" # Easy installation and use of web drivers to run system tests with browsers gem "webdrivers" gem 'factory_bot_rails' #gem 'database_cleaner' # gem 'shoulda' # gem 'shoulda-matchers' end ## Challenging the Testing Pyramid DevFeed: [Challenging the Testing Pyramid]() Original publisher: [Read original article]() Published: 2019-07-16T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Testing](), [Cypress](), [Selenium](), [Tooling](), [Web Development]() Tags: [automated](), [cypress](), [e2e-testing](), [javascript](), [selenium](), [testing](), [web-development]() ### AI overview An introduction to automated UI and end-to-end testing with Cypress. The article discusses testing costs and benefits, contrasts manual and automated testing, and places UI testing in the context of the testing pyramid and testing trophy. ### Source excerpt Lorem ipsum dolor sit amet ## Introducing fluentXPath DevFeed: [Introducing fluentXPath]() Original publisher: [Read original article]() Published: 2019-01-22T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Selenium](), [Library](), [Java]() Tags: [alternatives](), [build](), [concatenation](), [dependencies](), [gradle](), [groovy](), [java](), [kotlin](), [library](), [selenium](), [syntax](), [tests](), [writing]() ### AI overview The article introduces fluentXPath, a Java library for building XPath expressions with fluent syntax instead of string concatenation. It explains that the library is only syntactic sugar, does not validate XPath expressions, and may be unnecessary in languages with string interpolation. ### Source excerpt Some time ago I've started working on updating automated tests written in selenium with java. After working a bit with it I've noticed that from time to time constructing XPath expression can get ugly. We are writing our tests in pure java and "ugliness" usually comes from string concatenation when some extra parameters must be taken into account. I've decided to write something that might help a bit with building XPaths without string concatenation. Read more ## What to do when Firefox crashes under test automation with Selenium DevFeed: [What to do when Firefox crashes under test automation with Selenium]() Original publisher: [Read original article]() Author: Henrik Skupin Published: 2018-05-30T15:04:10Z Content type: tutorial Language: en Sources: [Mozilla Automation]() Topics: [Selenium](), [Test automation](), [Firefox](), [Testing]() Tags: [automation](), [bug](), [crash](), [firefox](), [geckodriver](), [mozilla](), [selenium](), [software](), [test-automation]() ### AI overview This tutorial explains how Firefox crashes can occur during Selenium-based website tests using geckodriver. It describes crash reporter support, the removal of minidump files with temporary profiles, and the planned MINIDUMP_SAVE_PATH mechanism for preserving crash data. ### Source excerpt If you have the task to create automated tests for websites you will most likely make use of Selenium when it comes to testing UI interactions. To execute the tests for the various browsers out there each browser vendor offers a so called driver package which has to be used by Selenium to run each of the commands. In case of Firefox this will be geckodriver. Within the last months we got a couple of issues reported for geckodriver that Firefox sometimes crashes while the tests are running. This feedbackContinue readingWhat to do when Firefox crashes under test automation with Selenium ## Screenshot testing with React and Storybook DevFeed: [Screenshot testing with React and Storybook]() Original publisher: [Read original article]() Author: Jesse Pinho Published: 2018-03-19T09:18:02Z Content type: tutorial Language: en Sources: [Bleeding Edge - Medium]() Topics: [screenshot-testing](), [Storybook](), [React](), [Testing](), [styled-components](), [Selenium]() Tags: [continuous-integration](), [react](), [screenshot-testing](), [selenium](), [storybook](), [styled-components](), [testing](), [visual-regression-testing]() ### AI overview The article explains why end-to-end UI tests can miss visual regressions and explores screenshot testing with React and Storybook to check component appearance across different states. ### Source excerpt Visual regression testing for fun, profit, and peace of mind Illustration by Marta Pucci A friend of mine recently related a scary story about the lack of automated visual regression testing where he works--a huge international tech firm that you've heard of and probably use. He'd added a CSS class to an element to hide it from the user. Unbeknownst to him, and despite using BEM-style naming for CSS classes, this class name was already being used for an important checkbox in the user settings screen of his company's web app. The result? Users could no longer change the setting represented by the checkbox, because it was invisible! I asked him why that hadn't been caught by automated tests. He explained that, although they did have end-to-end tests in place that went through the UI and tested its functionality, the tests didn't catch the bug. Selenium was still able to check the original checkbox via its selector, so its visibility had no effect on the outcome of the test. The only way this could have been caught is via visual regression testing -- or, as it is sometimes called, screenshot testing. 💅 Switching to styled-components I recalled this story recently while working on a sizable project at Clue: converting all of our "native" CSS to use styled-components. The new helloclue.com website consists of dozens of components. An article page, for example, contains at least ten different React components, all of which have accompanying CSS files. Converting all of this CSS to styled-components means there's an enormous risk of bugs exactly like the one my friend experienced. So before the project began, I investigated setting up screenshot testing for the site. 📕 Enter Storybook (Note: if you're already familiar with Storybook and @storybook/react, feel free to skip to the next section.) We use Storybook when developing simple presentational components. This way, we can test them in every possible state, without having to reproduce all the logic and so forth required t [Next page]()