User:Mjzffr: Difference between revisions
Jump to navigation
Jump to search
m (Add actions, fennec) |
m (add --artifact) |
||
| Line 4: | Line 4: | ||
* WebDriver spec python tests (wdspec) in the web-platform test suite | * WebDriver spec python tests (wdspec) in the web-platform test suite | ||
* Marionette server, implementing WebDriver "actions" command | * Marionette server, implementing WebDriver "actions" command | ||
* --artifact flag in try syntax (build scripts, mozconfigs) | |||
* unittest, pytest (e.g. stand up pytest-style tests for the Marionette Python harness) | * unittest, pytest (e.g. stand up pytest-style tests for the Marionette Python harness) | ||
* setting up a TaskCluster task ([http://www.erranderr.com/blog/taskcluster-learning.html using "legacy" task definitions]) | * setting up a TaskCluster task ([http://www.erranderr.com/blog/taskcluster-learning.html using "legacy" task definitions]) | ||
Revision as of 16:59, 23 January 2017
I'm maja_zf on IRC. Please see my Mozillians profile.
Things I've worked on/with at Mozilla:
- WebDriver spec python tests (wdspec) in the web-platform test suite
- Marionette server, implementing WebDriver "actions" command
- --artifact flag in try syntax (build scripts, mozconfigs)
- unittest, pytest (e.g. stand up pytest-style tests for the Marionette Python harness)
- setting up a TaskCluster task (using "legacy" task definitions)
- mach commands
- mentoring for Outreachy
- driving Platform_Operations/Project_of_the_Month
- improvements to marionette-harness (Marionette test runner), marionette-driver
- Fennec support in marionette harness and mozrunner
- setting up a custom harness and initial tests using Marionette/Marionette Python Test Runner (exteral-media-tests)
- Jenkins maintenance (continuous integration): mozplatformqa-jenkins and mozmill-ci
- mozharness scripts
- WebRTC Steeplechase automation (jenkinsherder)
- Data submission to Treeherder
- crash-stats API
- YouTube JS API
- One and Done (Django development)