# Selenium Selenium is a technology for automating web browsers, primarily for testing web applications, with tools for browser-driven automation and distributed test execution. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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: Highlights from Day 3 DevFeed: [Breakpoint 2026: Highlights from Day 3]() Original publisher: [Read original article]() Author: Shweta Chhillar Published: 2026-06-02T13:03:05Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Testing](), [AI Agent](), [Model Context Protocol](), [Test automation](), [MCP](), [LangChain](), [observability](), [Retrieval Augmented Generation (RAG)](), [Playwright](), [Cypress](), [debugging](), [Selenium]() Tags: [2026](), [agent](), [ai](), [automation](), [breakpoint](), [ci-cd](), [debugging](), [github](), [github-copilot](), [langchain](), [mcp](), [model-context-protocol](), [observability](), [qa](), [rag](), [testing](), [vscode]() ### AI overview A recap of Breakpoint 2026 Day 3 covering practical masterclasses and lightning talks on AI-driven test generation, non-deterministic testing, MCP-powered QA workflows, automated AI evaluation, and production testing practices. ### Source excerpt All sessions, masterclasses, and lightning talks from Breakpoint 2026 Day 3, covering AI agent testing, test automation with LangChain and CrewAI, MCP-powered QA workflows, Playwright network interception, non-deterministic testing, and building production-grade AI systems. ## BrowserStack Newsletter April 2026 DevFeed: [BrowserStack Newsletter April 2026]() Original publisher: [Read original article]() Author: Devanshi Jain Published: 2026-05-26T10:50:54Z Content type: article Language: en Sources: [BrowserStack Blog]() Topics: [Testing](), [Software Testing](), [Automation](), [Accessibility](), [Flutter](), [React Native](), [WebView](), [Selenium](), [Figma]() Tags: [accessibility](), [ai](), [browser](), [event](), [features](), [flutter](), [newsletter](), [product](), [react-native](), [report](), [software-testing]() ### AI overview BrowserStack's April 2026 newsletter covers Breakpoint 2026 content, a report on AI in software testing, and product updates across App Automate, Percy, Website Scanner, and Accessibility. Updates include expanded framework support, improved CI debugging and visual comparison workflows, broader authentication testing, WCAG 2.2 AA coverage, partial-page scanning, and Safari support. ### Source excerpt Read what's new at BrowserStack in April 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 ... ## 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. ## 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. ## 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. ## 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 ## 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 ## Dockerized e2e tests DevFeed: [Dockerized e2e tests]() Original publisher: [Read original article]() Published: 2018-02-15T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Docker](), [Selenium](), [Browser Automation](), [CI/CD](), [Testing](), [Travis CI](), [webDriver](), [Chrome](), [Firefox]() Tags: [browser](), [ci](), [containers](), [docker](), [firefox](), [selenium](), [testing](), [travis-ci](), [webdriver]() ### AI overview This tutorial explains how to run Selenium end-to-end tests in Docker and integrate them with CI tools such as Travis CI, GitLab CI, or Jenkins. It describes using Selenium Hub and Chrome and Firefox node containers, configuring WebdriverIO, capturing screenshots for failed tests, and organizing tests with a Page Object. ### Source excerpt In my free time, I'm trying to learn something new and best of way learning is by doing. To avoid spinning my wheels in vain I'm helping to develop some product. In the previous post, I've described what we've decided to use for the UI and pointed out that I'm going to write integration tests. Here is how I integrated selenium e2e tests with gitlab-ci/travis-ci/whatever by running them in docker. Read more ## Element interactability checks with geckodriver and Firefox 58 DevFeed: [Element interactability checks with geckodriver and Firefox 58]() Original publisher: [Read original article]() Author: Henrik Skupin Published: 2017-12-15T12:59:55Z Content type: tutorial Language: en Sources: [Mozilla Automation]() Topics: [Selenium](), [Browser Automation](), [webDriver](), [Firefox]() Tags: [automation](), [firefox](), [geckodriver](), [marionette](), [mozilla](), [selenium](), [software](), [test](), [testing](), [tests](), [webdriver]() ### AI overview Firefox 58 enables interactability checks by default for Selenium and geckodriver Element Click and Element Send Keys operations. The article explains the resulting not-interactable errors, how to report false positives, and the temporary moz:webdriverClick workaround. ### Source excerpt When you are using Selenium and geckodriver to automate your tests in Firefox you might see a behavior change with Firefox 58 when using the commands Element Click or Element Send Keys. For both commands we have enabled the interactability checks by default now. That means that if such an operation has to be performed for any kind of element it will be checked first, if a click on it or sending keys to it would work from a normal user perspective at all. If not a not-interactable error willContinue readingElement interactability checks with geckodriver and Firefox 58 ## Cucable Maven plugin for parallel execution of Cucumber scenarios DevFeed: [Cucable Maven plugin for parallel execution of Cucumber scenarios]() Original publisher: [Read original article]() Author: Benjamin Bischoff Test Automation Engineer; Author; Speaker; Magician Github Profile Linkedin Profile Published: 2017-06-30T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [Cucumber](), [Maven](), [test](), [Selenium](), [ci]() Tags: [browser](), [ci](), [frontend](), [maven](), [maven-plugin](), [open-source](), [parallel](), [plugin](), [quality-assurance](), [speed](), [test](), [user-experience]() ### AI overview Trivago describes creating Cucable, a Maven plugin that splits Cucumber scenarios into smaller chunks for parallel execution. The article explains limitations of custom runners, tag-based execution, feature-based execution, and existing plugins, particularly for scenario outlines and CI automation. ### Source excerpt Running Cucumber scenarios in parallel can be tricky, especially when a custom test runner is used. That's why we created Cucable - a Maven plugin to split test scenarios into smaller chunks that can be run at the same time. ## Page object pattern for javascript components testing DevFeed: [Page object pattern for javascript components testing]() Original publisher: [Read original article]() Published: 2017-02-23T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Testing](), [Selenium](), [Angular](), [React]() Tags: [angular](), [automated](), [implementation](), [page-object](), [react](), [refactor](), [selenium](), [tdd](), [testing](), [writing]() ### AI overview This tutorial explains how to apply the page object pattern to automated testing of JavaScript components, including Angular directives and React components. It shows how to encapsulate actions, verifications, and implementation details to make tests easier to read, maintain, and refactor. ### Source excerpt Page object pattern is common practice when writing automated tests using selenium. It allows to gather all possible operations on the page in one place and hide page implementation details from test case. Page object pattern can be used in the same way for angular directives, react and [put framework name here] components. Read more ## Using Selenium and webdriver to interact with insecure SSL pages in Firefox DevFeed: [Using Selenium and webdriver to interact with insecure SSL pages in Firefox]() Original publisher: [Read original article]() Author: Admin Published: 2017-01-23T14:13:56Z Content type: tutorial Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Selenium](), [Browser Automation](), [SSL](), [webDriver](), [Python]() Tags: [automation](), [firefox](), [marionette](), [mozilla](), [mozqa](), [python](), [selenium](), [ssl](), [test](), [testing](), [webdriver]() ### AI overview This tutorial explains how to use Selenium and Firefox WebDriver to access pages with invalid or self-signed SSL certificates during automated tests. It describes the Firefox 52 and Selenium 3 requirements and shows how to enable insecure certificate acceptance with the acceptInsecureCerts capability. ### Source excerpt Interacting with insecure SSL pages (eg. self-signed) in an automated test written for Selenium is an important feature. Especially when tests are getting run against locally served test pages. Under those circumstances you might never get fully secured websites served to the browser instance under test. To still allow running your tests with a successful test result, Selenium can instruct the browser to ignore the validity check, which will simply browse to the specified site without bringing up the SSL error page. Since the default driver for Firefox was switchedContinue readingUsing Selenium and webdriver to interact with insecure SSL pages in Firefox ## Understanding WebDriver, Selenium, Marionette, and Browser Automation DevFeed: [Understanding WebDriver, Selenium, Marionette, and Browser Automation]() Original publisher: [Read original article]() Author: Maja Frydrychowicz Published: 2016-07-12T04:00:00Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [webDriver](), [Browser Automation](), [Selenium](), [Testing](), [Firefox](), [HTTP](), [JSON](), [Mozilla](), [JavaScript](), [Open Source]() Tags: [automation](), [browser](), [browser-ui](), [browsers](), [client-driver](), [firefox](), [foss](), [geckodriver](), [harness](), [http](), [javascript](), [json](), [marionette](), [mozilla](), [open-source](), [payload](), [request](), [responses](), [selenium](), [w3c](), [web](), [webdriver]() ### AI overview An explanatory article untangles the terminology around Marionette, Selenium, WebDriver, FirefoxDriver, and geckodriver. It explains the W3C WebDriver Specification and how its browser-agnostic protocol uses JSON over HTTP to send commands and receive responses for browser automation and testing. ### Source excerpt I define WebDriver, W3C WebDriver, Selenium, geckodriver, FirefoxDriver, Marionette harness/runner/client/driver and more. [Next page]()