# marionette Published articles for marionette. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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 ## 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 ## Marionette, Act II: Harnessing automation to test the browser DevFeed: [Marionette, Act II: Harnessing automation to test the browser]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-08-22T00:00:00Z Content type: tutorial Language: en Sources: [Mozilla Automation]() Topics: [Browser Automation](), [Testing](), [Firefox](), [Mozilla](), [Python](), [API]() Tags: [api](), [automation](), [browser](), [firefox](), [marionette](), [mozilla](), [python](), [test]() ### AI overview This article explains the Marionette test harness, a testing framework for running automated tests on Mozilla browsers using the Marionette automation tools. It describes how browser automation supports testing instead of manual checks, with a Python API controlling the Gecko browser engine. ### Source excerpt Welcome back to my post series on the Marionette project! In Act I, we looked into Marionette's automation framework for Gecko, the engine behind the Firefox browser. Here in Act II, we'll take a look at a complementary side of the Marionette project: the testing framework that helps us run tests using our Marionette-animated browser, aka the Marionette test harness. If - like me at the start of my Outreachy internship - you're clueless about test harnesses, or the Marionette harness in particular, and want to fix that, you're in the right place! Wait, what's Marionette again? Quick recap from Act I: Marionette refers to a suite of tools for automated testing of Mozilla browsers. In that post, we saw how the Marionette automation framework lets us control the Gecko browser engine (our "puppet"), thanks to a server component built into Gecko (the puppet's "strings") and a client component (a "handle" for the puppeteer) that gives us a simple Python API to talk to the server and thus control the browser. But why do we need to automate the browser in the first place? What good does it do us? Well, one thing it's great for is testing. Indulge me in a brief return to my puppet metaphor from last time, won't you? If the automation side of Marionette gives us strings and a handle that turn the browser into our puppet, the testing side of Marionette gives that puppet a reason for being, by letting it perform: it sets up a stage for the puppet to dance on, tell it to carry out a given performance, write a review of that performance, and tear down the stage again. OK, OK, metaphor-indulgence over; let's get real. Wait, why do we need automated browser testing again? As Firefox1 contributors, we don't want to have to manually open up Firefox, click around, and check that everything works every time we change a line of code. We're developers, we're lazy! Clueless via POPSUGAR But we can't not do it, because then we might not realize that we've broken the entire internet (or, yo ## Outreachy Internship Update: Learning Mozilla's Development Process and Refactoring Marionette's Python Test Runner DevFeed: [Outreachy Internship Update: Learning Mozilla's Development Process and Refactoring Marionette's Python Test Runner]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-08-02T00:00:00Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [Development](), [Mozilla](), [Testing](), [Python](), [Refactoring](), [Test-driven development](), [Pytest](), [Firefox]() Tags: [development-process](), [firefox](), [internship](), [marionette](), [mozilla](), [mozreview](), [outreachy](), [pytest](), [python](), [refactoring](), [test](), [testing](), [treeherder]() ### AI overview An Outreachy intern reflects on the first part of an internship with Mozilla, describing the process of learning Mozilla's development tools and workflows. The article also outlines work on test-driven refactoring of Marionette's Python test runner and previews a follow-up post about its test runner and harness. ### Source excerpt It feels like yesterday that I started my Outreachy internship, but it was actually over 2 months ago! For the last couple of weeks I've been on Outreachy hiatus because of EuroPython, moving from Saarbrücken to Berlin, and my mentor being on vacation. Now I'm back, with 6 weeks left in my internship! So it seems like a good moment to check in and reflect on how things have been going so far, and what's in store for the rest of my time as an Outreachyee. What have I been up to? Learning how to do the work In the rather involved application process for Outreachy, I already had to spend quite a bit of time figuring out the process for making even the tiniest contribution to the Mozilla codebase. But obviously one can't learn everything there is to know about a project within a couple of weeks, so a good chunk of my Outreachy time so far was spent on getting better acquainted with: The tools I've already written about my learning experiences with Mercurial, but there were a lot of other components of the Mozilla development process that I had to learn about (and am still learning about), such as Bugzilla, MozReview, Treeherder, Try, Mach... Then, since the project I'm working focuses on testing, I had to grok things like Pytest and Mock. Since most everything I'm doing is in Python, I've also been picking up useful Python tidbits here and there. The project My internship project, "Test-driven refactoring of Marionette's Python test runner", relates to a component of the Marionette project, which encompasses a lot of moving parts. Even figuring out what Marionette is, what components it comprises, how these interrelate, and which of them I need to know about, was a non-trivial task. That's why I'm writing a couple of posts about the project itself - one down, one to go - to crystallize what I've learned and hopefully make it a little easier for other people to get through the what-even-is-it steps that I've been going through. This post is a sort of "intermission", so sta ## 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. ## Marionette, Act I: We've got Firefox on a string DevFeed: [Marionette, Act I: We've got Firefox on a string]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-07-08T00:00:00Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Testing](), [browser](), [Server](), [client](), [Refactoring](), [Python](), [Mozilla]() Tags: [automated](), [browser](), [components](), [firefox](), [forms](), [harness](), [marionette](), [mozilla](), [python](), [refactoring](), [server](), [test](), [testing]() ### AI overview This first article in a two-part series introduces Marionette and explains how its server and client components automatically control Firefox for browser testing. It covers testing Firefox's interface and web content, including links, forms, and video, and previews a later discussion of the Marionette test harness and runner. ### Source excerpt As you may already know, I'm spending my summer interning with Mozilla's Enginering Productivity team through the Outreachy program. Specifically, the project I'm working on is called Test-driven Refactoring of Marionette's Python Test Runner. But what exactly does that mean? What is Marionette, and what does it have to do with testing? In this two-part series, I'd like to share a bit of what I've learned about the Marionette project, and how its various components help us test Firefox by allowing us to automatically control the browser from within. Today, in Act I, I'll give an overview of how the Marionette server and client make the browser our puppet. Later on, in Act II, I'll describe how the Marionette test harness and runner make automated testing a breeze, and let you in on the work I'm doing on the Marionette test runner for my internship. And since we're talking about puppets, you can bet there's going to be a hell of a lot of Being John Malkovich references. Consider yourself warned! How do you test a browser? On the one hand, you probably want to make sure that the browser's interface, or chrome, is working as expected; that users can, say, open and close tabs and windows, type into the search bar, change preferences and so on. But you probably also want to test how the browser displays the actual web pages, or content, that you're trying to, well, browse; that users can do things like click on links, interact with forms, or play video clips from their favorite movies. Because let's be honest, that's like 96% of the point of the internet right there, no? These two parts, chrome and content, are the main things the browser has to get right. So how do you test them? Well, you could launch the browser application, type "Being John Malkovich" into the search bar and hit enter, check that a page of search results appears, click on a YouTube link and check that it takes you to a new page and starts playing a video, type "I ❤ Charlie Kaufman and Spike Jonze" i ## Warming up to Mercurial DevFeed: [Warming up to Mercurial]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-06-03T00:00:00Z Content type: tutorial Language: en Sources: [Mozilla Automation]() Topics: [Mercury](), [Git](), [Firefox](), [Mozilla](), [Testing]() Tags: [firefox](), [git](), [graph](), [install](), [marionette](), [mozilla](), [repo](), [testing](), [version-control]() ### AI overview A developer documents learning Mercurial after working primarily with Git, explaining basic repository operations and terminology while contributing to Mozilla's Marionette project for Firefox. The article highlights similarities between Mercurial and Git and describes differences involving logs, graphs, changesets, revisions, and identifiers. ### Source excerpt When it comes to version control, I'm a Git girl. I had to use Subversion a little bit for a project in grad school (not distributed == not so fun). But I had never touched Mercurial until I decided to contribute to Mozilla's Marionette, a testing tool for Firefox, for my Outreachy application. Mercurial is the main version control system for Firefox and Marionette development,1 so this gave me a great opportunity to start learning my way around the hg. Turns out it's really close to Git, though there are some subtle differences that can be a little tricky. This post documents the basics and the trip-ups I discovered. Although there's plenty of other info out there, I hope some of this might be helpful for others (especially other Gitters) using Mercurial or contributing to Mozilla code for the first time. Ready to heat things up? Let's do this! Getting my bearings on Planet Mercury OK, so I've been working through the Firefox Onramp to install Mercurial (via the bootstrap script) and clone the mozilla-central repository, i.e. the source code for Firefox. This is just like Git; all I have to do is: $ hg clone (Incidentally, I like to pronounce the hg command "hug", e.g. "hug clone". Warm fuzzies!) Cool, I've set foot on a new planet! ...But where am I? What's going on? Just like in Git, I can find out about the repo's history with hg log. Adding some flags make this even more readable: I like to --limit the number of changesets (change-whats? more on that later) displayed to a small number, and show the --graph to see how changes are related. For example: $ hg log --graph --limit 5 or, for short: $ hg log -Gl5 This outputs something like: @ changeset: 300339:e27fe24a746f |\ tag: tip | ~ fxtree: central | parent: 300125:718e392bad42 | parent: 300338:8b89d98ce322 | user: Carsten "Tomcat" Book | date: Fri Jun 03 12:00:06 2016 +0200 | summary: merge mozilla-inbound to mozilla-central a=merge | o changeset: 300338:8b89d98ce322 | user: Jean-Yves A ## Firefox-ui-tests - Platform Operations Project of the Month DevFeed: [Firefox-ui-tests - Platform Operations Project of the Month]() Original publisher: [Read original article]() Author: Admin Published: 2016-06-02T09:18:23Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Testing](), [ci](), [Puppeteer](), [Automation](), [Mozilla](), [Jenkins]() Tags: [automation](), [browser](), [ci](), [continuous-integration](), [firefox](), [jenkins](), [marionette](), [mozilla](), [mozmill](), [taskcluster](), [testing](), [tests](), [treeherder]() ### AI overview This article presents firefox-ui-tests as a Mozilla project for integration testing of Firefox's user interface. The tests use the Marionette automation framework and Firefox Puppeteer's page object model, run across Firefox code-check and release workflows, and include localized-build and update testing. The project's work includes improving result visibility, test placement, stability, and coverage. ### Source excerpt Hello from Platforms Operations! Once a month we highlight one of our projects to help the Mozilla community discover a useful tool or an interesting contribution opportunity. This month's project is firefox-ui-tests! What are firefox-ui-tests? Firefox UI tests are a test suite for integration tests which are based on the Marionette automation framework and are majorly used for user interface centric testing of Firefox. The difference to pure Marionette tests is, that Firefox UI tests are interacting with the chrome scope (browser interface) and not content scope (websites) by default.Continue readingFirefox-ui-tests - Platform Operations Project of the Month ## Review of Firefox desktop automation work - Q1 2016 DevFeed: [Review of Firefox desktop automation work - Q1 2016]() Original publisher: [Read original article]() Author: Admin Published: 2016-03-31T14:10:13Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Automation](), [Puppeteer](), [Mozilla](), [GitHub]() Tags: [automation](), [build-system](), [ci](), [debug](), [files](), [firefox](), [github](), [linux](), [marionette](), [mozilla](), [mozqa](), [qa](), [reports](), [testing](), [tests](), [ui]() ### AI overview A Q1 2016 review of Firefox desktop automation work describes Mozharness and Build System changes, a Firefox UI test task in Taskcluster, and the move of Firefox UI tests and their harness to mozilla-central. ### Source excerpt Today is the last day of Q1 2016 which means time to review what I have done during all those last weeks. When I checked my status reports it's kinda lot, so I will shorten it a bit and only talk about the really important changes. Build System / Mozharness After I had to dig into mozharness to get support for Firefox UI Tests during last quarter I have seen that more work had to be done to fully support tests which utilize Nightly or Release builds of Firefox. TheContinue readingReview of Firefox desktop automation work - Q1 2016 ## Firefox Desktop automation goals Q1 2016 DevFeed: [Firefox Desktop automation goals Q1 2016]() Original publisher: [Read original article]() Author: Admin Published: 2016-02-02T16:39:20Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Automation](), [Testing](), [ci](), [FIRST]() Tags: [automation](), [ci](), [continuous-integration](), [firefox](), [marionette](), [mozilla](), [mozmill](), [qa](), [testing](), [treeherder]() ### AI overview The article outlines Firefox desktop automation goals for Q1 2016, including running firefox-ui-tests in TaskCluster, continuing mozmill-ci coverage within infrastructure limits, reporting results in Treeherder, and documenting the testing systems to support higher-tier sheriffing. ### Source excerpt As promised in my last blog posts I don't want to only blog about the goals from last quarters, but also about planned work and what's currently in progress. So this post will be the first one which will shed some light into my active work. First lets get started with my goals for this quarter. Execute firefox-ui-tests in TaskCluster Now that our tests are located in mozilla-central, mozilla-aurora, and mozilla-beta we want to see them run on a check-in basis including try. Usually you will setup Buildbot jobs toContinue readingFirefox Desktop automation goals Q1 2016 ## Review of automation work - Q4 2015 DevFeed: [Review of automation work - Q4 2015]() Original publisher: [Read original article]() Author: Admin Published: 2016-01-08T22:25:58Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Automation](), [Firefox](), [Mozilla](), [Puppeteer](), [GitHub](), [Refactoring](), [bug]() Tags: [automation](), [bug](), [ci](), [code](), [continuous-integration](), [firefox](), [github](), [jenkins](), [marionette](), [misc](), [mozilla](), [mozmill](), [mozqa](), [refactoring](), [script](), [tests](), [treeherder]() ### AI overview A Q4 2015 review of work to move Firefox UI tests into mozilla-central, run them with mozharness in mozmill-ci, fix failures and regressions, split the repository into packages, and improve related test tooling. ### Source excerpt The last quarter of 2015 is gone and its time to reflect what happened in Q4. In the following you will find a full overview again for the whole quarter. It will be the last time that I will do that. From now on I will post in shorter intervals to specific topics instead of covering everything. This was actually a wish from our latest automation survey which I want to implement now. I hope you will like it. So during the last quarter my focus was completely on gettingContinue readingReview of automation work - Q4 2015 ## Firefox Automation report - Q3 2015 DevFeed: [Firefox Automation report - Q3 2015]() Original publisher: [Read original article]() Author: Admin Published: 2015-10-20T19:42:37Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Automation](), [Firefox](), [Jenkins](), [Refactoring](), [Puppeteer](), [ci](), [modules]() Tags: [automation](), [blog](), [ci](), [continuous-integration](), [firefox](), [jenkins](), [marionette](), [modules](), [mozilla](), [mozmill](), [refactoring](), [report](), [software](), [taskcluster](), [test](), [treeherder]() ### AI overview A Q3 2015 Firefox Automation report describes work on mozharness scripts for firefox-ui-tests, including improved configurability, crash-report handling, and support for Jenkins and release-testing workflows. It also covers Mozmill-CI updates, test-job refactoring, fixes for update tests affected by Release Engineering changes, and rewritten Pulse-message handling. ### Source excerpt It's time for another Firefox Automation report! It's incredible how fast a quarter passes by without that I have time to write reports more often. Hopefully it will change soon - news will be posted in a follow-up blog post. Ok, so what happened last quarter for our projects. Mozharness One of my deliverables in Q3 was to create mozharness scripts for our various tests in the firefox-ui-tests repository, so that our custom runner scripts can be replaced. This gives us a way more stable system and additional features likeContinue readingFirefox Automation report - Q3 2015