cdifino · cdifino · Jul 18, 2019 · Jun 4, 2019 · Jun 4, 2019 · Jun 4, 2019
diff --git a/.github/ISSUE_TEMPLATE/bug.md b/.github/ISSUE_TEMPLATE/bug.md
@@ -34,7 +34,7 @@ Issues without a reproduction project are likely to stall.
 OS: <!-- Windows 10? OSX? -->
 Selenium IDE Version:  <!-- e.g.: 3.0.3 -->
 Selenium SIDE Runner Version:  <!-- e.g.: 0.7.0
-Please note that selenium-side-runner supports Node.js 8 - 10
+Please note that selenium-side-runner supports Node.js 10 - 12
 -->
 Node version: <!-- e.g.: 10.4
 Only required if using selenium-side-runner

diff --git a/.github/ISSUE_TEMPLATE/regression.md b/.github/ISSUE_TEMPLATE/regression.md
@@ -37,7 +37,7 @@ Issues without a reproduction project are likely to stall.
 OS: <!-- Windows 10? OSX? -->
 Selenium IDE Version:  <!-- e.g.: 3.0.3 -->
 Selenium SIDE Runner Version:  <!-- e.g.: 0.7.0
-Please note that selenium-side-runner supports Node.js 8 - 10
+Please note that selenium-side-runner supports Node.js 10 - 12
 -->
 Node version: <!-- e.g.: 10.4
 Only required if using selenium-side-runner

diff --git a/.travis.yml b/.travis.yml
@@ -6,8 +6,8 @@ cache:
   directories:
     - .peru
 node_js:
+  - "12"
   - "10"
-  - "8"
 services:
   - docker
 before_install:

diff --git a/changelog.md → CHANGELOG.md b/changelog.md → CHANGELOG.md
@@ -1,5 +1,25 @@
 # Changelog
 
+## v3.12.1
+- Fix for string escaping, to handle backslashes
+
+## v3.12.0
+- Added default wait time to `wait for` commands (PR #678)
+- Added better string escaping to code export and code emitting for the command-line runner
+- Made setWindowSize optional when emitting for the runner (issue #627)
+
+## v3.11.1
+- Add the ability for new programming languages to be specified through plugins
+
+## v3.10.0
+- Code export for JavaScript (e.g., Mocha, Node 10)
+
+## v3.9.0
+- Code export for Python (e.g., pytest, Python 3)
+- Fix for frames to support `relative=parent` in the runner
+- Fix for frames to support `relative=top` in IDE playback
+- Added timestamps to log entries (PR #688)
+
 ## v3.8.1
 - Code export fixes for commands that open and switch to new windows
 - Added a suffix of "Test" to class and filenames in Java code export

diff --git a/README.md b/README.md
@@ -1,6 +1,6 @@
 <img src="packages/selenium-ide/src/icons/icon128.png" alt="logo" height="128" align="right" />
 
-# Selenium IDE &middot; [![Build Status](https://travis-ci.org/SeleniumHQ/selenium-ide.svg?branch=master)](https://travis-ci.org/SeleniumHQ/selenium-ide)
+# Selenium IDE &middot; [![Build Status](https://travis-ci.com/SeleniumHQ/selenium-ide.svg?branch=master)](https://travis-ci.com/SeleniumHQ/selenium-ide)
 
 _[WIP] An integrated development environment for Selenium scripts_
 

diff --git a/docs/introduction/code-export.md b/docs/introduction/code-export.md
@@ -21,7 +21,11 @@ This will place inline code comments in the exported file with details about the
 
 ## Supported Exports
 
-Currently, export to Java is supported. Specifically, Java for JUnit.
+Currently, export to the following languages and test frameworks is supported.
+
+- Java JUnit
+- JavaScript Mocha
+- Python pytest
 
 We intend to support all of the officially supported programming language bindings for Selenium (e.g., Java, JavaScript, C#, Python, and Ruby) in at least one testing framework for each language.
 
@@ -58,6 +62,40 @@ Here's a sample `pom.xml` to help you get started.
 </project>
 ```
 
+### JavaScript Mocha
+
+The exported code for JavaScript Mocha is built to work with Node 10, Mocha 6.1.x, and the latest version of Selenium 4.
+
+You should be able to take the exported JavaScript file and run it after installing these dependencies (e.g., with `npm install`).
+
+Here's a sample `package.json` to help you get started.
+
+```javascript
+{
+  "dependencies": {
+    "mocha": "^6.1.4",
+    "selenium-webdriver": "^4.0.0-alpha.3"
+  }
+}
+```
+
+### Python pytest
+
+The exported code for Python pytest is built to work with Python 3, pytest 4.6.x, and the latest version of Selenium 4.
+
+You should be able to take the exported JavaScript file and run it after installing these dependencies (e.g., with `pip3 install`).
+
+Here's a sample `requirements.txt` to help you get started.
+
+```
+pytest == 4.6.3
+selenium == 4.0.0a1
+```
+
+```sh
+> pip3 install -r ./requirements.txt
+```
+
 ## How To Contribute
 
 Code export was built in a modular way to help enable contributions.
@@ -72,7 +110,7 @@ First, copy an existing language package (e.g., `packages/code-export-java-junit
 
 Next, add the new package as a dependency to [the `package.json` in `code-export`](https://github.com/SeleniumHQ/selenium-ide/blob/c55c556ffc947fd3f6ee8ab317915c6f879a88dc/packages/code-export/package.json#L22).
 
-Lastly, run `yarn` from the root of the project.
+Lastly, run `yarn` from the root of the project, and then build the project using `yarn watch` (full details for getting a local build going are available [here](https://github.com/SeleniumHQ/selenium-ide/blob/v3/README.md)).
 
 ### 2. Update the locators and commands
 

diff --git a/docs/plugins/code-export.md b/docs/plugins/code-export.md
@@ -4,18 +4,41 @@ title: Code Export Plugin Support
 sidebar_label: Exporting Code
 ---
 
-The plugins API enables any Selenium IDE plugin to be export code in response to certain events (or "hooks").
+The plugins API enables any Selenium IDE plugin to export code for either:
+
+1. an existing language
+2. a new language
+
+__NOTE: If adding a new language, take a look at [@seleniumhq/side-utils](https://www.npmjs.com/package/@seleniumhq/side-utils). You can see an example of it in use in existing languages for code-export (e.g., [java-junit](https://github.com/SeleniumHQ/selenium-ide/tree/v3/packages/code-export-java-junit)).__
 
 ### Export config
 
-In your plugin manifest you'll need to specify that it exports languages, and for which ones.
+In your plugin manifest you'll need to specify that it exports languages.
+
+<u>Add to an existing language</u>
+
+To augment an existing language, use the `languages` key and specify which ones in an array.
 
 ```javascript
   "exports": {
     "languages": ["java-junit"]
   }
 ```
 
+The currently available language ids `"java-junit"`, `"javascript-mocha"`, and `"python-pytest"`.
+
+<u>Add a new language</u>
+
+To add a new language to code export, use the `vendor` key and specify your langauge in an object array.
+
+```javascript
+  "exports": {
+    "vendor": [{"your-language": "Your language"}]
+  }
+```
+
+The key is the ID which will be used in the export event. The value is the display name that will be used in the code export menu in the UI.
+
 ### Export event
 
 Selenium IDE sends the following event for each entity type, which your plugin can respond to for code export.
@@ -30,7 +53,7 @@ Selenium IDE sends the following event for each entity type, which your plugin c
 ```
 
 - `action` - `export`, indicating an action that requires code export
-- `entity`, the entity to export, can be `command` or any of [the hooks mentioned in the next section](code-export.md#hooks)
+- `entity`, the entity to export, can be `command`, any of [the hooks mentioned in the next section](code-export.md#hooks), or `vendor` if exporting a new language
 - `options` - metadata to help your plugin make more informed decisions about what to export (e.g., project, test name, suite name, etc.)
 
 ## Hooks
@@ -49,6 +72,8 @@ Code export is built around the notion of hooks, which offers entry points into
 
 ## Response
 
+### Add to an existing language
+
 To respond to an export event, call `sendResponse` along with the string you'd like to export. If there are multiple lines to your string, separate them with newline characters (e.g., `\n`).
 
 Or you can look into using the command object structure mentioned in the [code export getting started](introduction/code-export.md#2-update-the-locators-and-commands).
@@ -57,4 +82,16 @@ Or you can look into using the command object structure mentioned in the [code e
 sendResponse(`const myLibrary = require("my-library");`);
 ```
 
+### Add a new language
+
+In response to a `vendor` export event for your new language(s), your plugin needs to respond with the an object containing the keys `filename` and `body`.
+
+```javascript
+const payload = {
+  filename: 'test.js',
+  body: '// your final exported code\n// goes here\n// etc.'
+}
+sendResponse(payload)
+```
+
 
diff --git a/gh-release.js b/gh-release.js
@@ -18,7 +18,7 @@ if (!token)
 
 // fetch changelog details
 const changelog = exec(
-  `sed '1,/${tag}/d;/## v/q' ./changelog.md | sed '/^ *$/q'`,
+  `sed '1,/${tag}/d;/## v/q' ./CHANGELOG.md | sed '/^ *$/q'`,
   {
     encoding: 'utf8',
   }

diff --git a/lerna.json b/lerna.json
@@ -3,6 +3,6 @@
   "packages": [
     "packages/*"
   ],
-  "version": "3.8.1",
+  "version": "3.12.1",
   "npmClient": "yarn"
 }
diff --git a/packages/code-export-java-junit/.babelrc b/packages/code-export-java-junit/.babelrc
@@ -1,13 +1,13 @@
  {
    "presets": [
-     ["env",
+     ["@babel/preset-env",
        {
          "targets": {
            "node": "8"
          }
        }]
    ],
    "plugins": [
-     "transform-object-rest-spread",
+     "@babel/plugin-proposal-object-rest-spread"
    ]
  }