Some CI servers, like Jenkins and Bamboo, require JUnit/Ant compatible XML reports be generated for test runs to be reported correctly.

Reference reporter from BusterJS - http://docs.busterjs.org/en/latest/modules/buster-test/reporters/#xml-reporter

intern should include a performance/benchmarking API alongside the functional and unit test functionality.  I will re-submit (eventually) my integration of Benchmark.js to provide this API.

Hi! Is it possible to use Cucumber.js ( https://github.com/cucumber/cucumber-js ) together with intern? I would like to write my functional tests as features in pure Gherkin Syntax. What I have to do if I want to use Cucumber.js? Regards!

When running the tests locally I actually don't have any problem, but when Travis CI runs them, the following error raises:

! Cannot read property 'numToReport' of undefined
TypeError: Cannot read property 'numToReport' of undefined
  at Pretty.suiteEnd  <src/lib/reporters/Pretty.ts:162:41>
  at <src/lib/reporters/Reporter.ts:94:31>
  at <src/lib/executors/Executor.ts:302:30>
  at <node_modules/@dojo/core/async/Task.ts:351:12>
  at handler  <node_modules/@dojo/core/async/ExtensiblePromise.ts:229:14>
  at process._tickCallback  <internal/process/next_tick.js:109:7>
! [POST http://localhost:4444/wd/hub/session / {"desiredCapabilities":{"idle-timeout":60,"name":"intern","build":"f735be36d579fa4ff583a7ec9a5f2faa0793c532","browserName":"chrome","chromeOptions":{"args":["headless"]}}}] unknown error: Chrome failed to start: crashed
  (Driver info: chromedriver=2.33.506092 (733a02544d189eeb751fe0d7ddca79a0ee28cce4),platform=Linux 4.14.12-041412-generic x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 60.18 seconds
Build info: version: '3.5.2', revision: '10229a9020', time: '2017-08-21T17:54:21.164Z'
System info: host: 'travis-job-inad9300-soil-333461114', ip: '172.17.0.8', os.name: 'Linux', os.arch: 'amd64', os.version: '4.14.12-041412-generic', java.version: '1.8.0_151'
Driver info: driver.version: unknown
UnknownError: [POST http://localhost:4444/wd/hub/session / {"desiredCapabilities":{"idle-timeout":60,"name":"intern","build":"f735be36d579fa4ff583a7ec9a5f2faa0793c532","browserName":"chrome","chromeOptions":{"args":["headless"]}}}] unknown error: Chrome failed to start: crashed

Here is how my Intern configuration:

{
    "environments": [{
        "browserName": "chrome",
        "chromeOptions": {"args": ["headless"]}
    }],
    "capabilities": {"fixSessionCapabilities": false},
    "loader": {"script": "dojo2"},
    "suites": ["build/**/*.test.js"],
    "coverage": ["build/!(testing)/**/!(*.test).js"],
    "reporters": [{
        "name": "pretty"
    }, {
        "name": "jsoncoverage",
        "options": {"filename": "coverage.json"}
    }]
}

Goal is to make sure Intern 4 feels natural and efficient to use.

Ways to do this:

• Install Intern 4 per instructions within Intern readme
• Review source and APIs
• Review existing examples and documentation
• Run tests
• Port some tests from Dojo 2 to use Intern 4

As you do this, you should look for things that feel suboptimal from a usability or developer ergonomics perspective, in particular:

• Authoring tests with ES6 and TypeScript
• Does the loaderless Intern approach feel straightforward
• Can we easily test ES6 features without transpilation
• What ES6+ features should be supported but are not yet within tests (e.g. async/await)
• What do we need to do to improve the documentations, tutorials, and examples
• What else?

I thought it was due to the following issue with wd: https://github.com/admc/wd/issues/129 , but this is not the case (applying the workaround for the issue in wd does not resolve the problem in intern).

It appears that the following line of code in lib/wd.js fails the execution of a test suite:

                this._wd.execute('return typeof __internCoverage !== "undefined" && JSON.stringify(__internCoverage)', function (error, returnValue) {
                    if (error) {
                        dfd.reject(error);
                        return;
                    }

                    // returnValue might be falsy on a page with no coverage data, so don't try to publish coverage
                    // results to prevent things from breaking
                    returnValue && topic.publish('/coverage', self.sessionId, JSON.parse(returnValue));

                    wrappedFunction.apply(self, args).then(dfd.resolve.bind(dfd), dfd.reject.bind(dfd));
                });

The execution of 'return typeof __internCoverage !== "undefined" && JSON.stringify(__internCoverage)' always fails with AdnroidDriver (https://code.google.com/p/selenium/wiki/AndroidDriver).

As a result, the runner.js execution hang foerever, an no error message is displayed in the console.

My default Firefox update to 53 and now the Intern tests are failing to start properly:

Suite firefox on any platform FAILED SessionNotCreatedException: [POST http://localhost:4444/wd/hub/session / {"desiredCapabilities":{"firefox_profile":"UEsDBBQACAAIAAqylEoAAAAAAAAAAAAAAAAHAAAAdXNlci5qc61XXW/bNhR9368w/DC0wEzLSYNtCYqhS9shQIsA84LtjaClK4s1RWokZdn79TvURyLbsh0DRfKgKPfyfvDcc49KR5YXltI3Y1EUrCwS4YmJ0pvxT6NUKEdv734oB41Ii4WiZNhuYU0FL5aYSisjEpYLLZZ44TJT/Z2RnnthvdTL0+6fnr58YGZN1sqEYOptuZdQF6i2vGYijqnwdVbHbZXUK2YK0pw2nqwWCkdf7Rbanftiq6mqpEZBx41NmsI+JDrQuu5EJ1Kqn1E9e1UTHQkbZ+3lDB8eCtFOGu3YQpl4paTzrz3c1X7eWGKWXJkTT63JeWyFy4ajPZeSkVIszihefaRUlMr/3tz7aTcvFo5VwupHfa+MO9OvnvUj7uz00S7AqixYAbDBMhq+1J0ryIVCLnS6W925mckpnM0rUjGeeWkDeMZiYUp/u1BCr8a7MRNae2OUYwCxsTFuyKh+sEOYJiZniXRhuniN0qS0wAoPczRcfe/2w+h+bJznMbwdPGZ7beiZK7Nc7uLwMJ+eecsPJ1F7aK6Nl+n2CXwwnL4mXxm7ajli0k7RBD33Zch/YJg6l8z7An6bCRqrKfZhAiYF2QmCgTYGit/xLDLpsu0kEFwhnJso0ksfQH91c7N7jV1SYEnHhFKm4ostTxrUw+GwbQWGqPCOAb88N4lQZxBGMa7Zb1kqFeGJGStxNbwwSsZbRLjeTcjt2ztvZez5vttA855dwwxy0uDAgK/69ZFhPOlSkzo3Or7MuSKxQl2vTzA4XBZLkVhfVtqux2XRXLnIpedSv76Ta0lYKkuey82xVbrb+h2Hs+nJpTYarJ5TviA7r/88MlGBpFbSs3Y+un3dEtEgwjsXTwoRvN2eRviheTMideF76/fQ1tI3zPeRzf5NrIWLrSw89npNAnVrHvR9w7eD6XdbLPBts9lZUuZFr4jDoa5okVgJZuGN0uClhpFDXjwm60NvTzk1xMm18DiD0xqzd84FtBRW8ksciRc1sx0GCpWADHnTCm5Lzb3Mw1Re762AZ1DVwONgT+gH32gHlFan176E9+CI2rWMyTG31THDGmFgRtIJJF4gsPDmUc9LyDE3XCEEnfY1323QSoP6wKulh8yxEiHHgdlvp9PZ1c8sws/s9tcoiqbr2d56HToGeDdQsSnWLfGTZ15H19H0xe63sDVQ1ftQ1I91/Rv/Pt2A593Km4JfEt5h2qQ+Wk4durH57mEhgI518TlsWXyfsI580PHuTMTWau/22n63KPJmhQ+DenE//fnQA8GeV+9LxQFr2g9DNKdECqaxAZYC6pZBFuQYHkiETl4FOXU4RWGyYbaQKsCzYYlK+iyGSgyhDj2WpMliwQcdAXGIQep9s4y/mv+kUmJ6w6LRm68iltobl92NHjBzaoQXo8f56B+oNDaL7kZ2ffsOgH87+gOq2kyvolmE39nos8RXmtlMwz9Hnzcf/iKwjp3OWLTXnZ7+qpX5PWQI+KYt5x3GabhdZ/x+OebX0Wit0/ujN2nYbrBjmwJb0kNHsTAC0Hn48sCe+rdElUdE7otLlUl0LnzhnPbYRVf4ym2BdvlRp5uj5TLzKoi0AaakDYAHFq4JrmbWT89vznuckdovR7uyKIxtFuSZLLDbZQr4dCO7B6BOIdcqd9JLv5ft/1BLBwi7/Tsi2gQAADgQAABQSwECLQMUAAgACAAKspRKu/07ItoEAAA4EAAABwAAAAAAAAAAACAApIEAAAAAdXNlci5qc1BLBQYAAAAAAQABADUAAAAPBQAAAAA=","name":"tests/intern_functional","idle-timeout":60,"browserName":"firefox","marionette":true}}] Unable to create new remote session. desired capabilities = Capabilities [{marionette=true, name=tests/intern_functional, browserName=firefox, idle-timeout=60, moz:firefoxOptions=org.openqa.selenium.firefox.FirefoxOptions@392f6c41, firefox_profile=org.openqa.selenium.firefox.FirefoxProfile@7c2df500}], required capabilities = Capabilities [{}] Build info: version: '3.1.0', revision: '86a5d70', time: '2017-02-16 07:57:44 -0800' System info: host: 'Vlads-MBP', ip: '192.168.1.144', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.12.4', java.version: '1.8.0_111' Driver info: driver.version: FirefoxDriver at Server.createSession <node_modules/intern/node_modules/leadfoot/Server.js:355:15> at <node_modules/intern/lib/executors/Runner.js:198:23> at retry <node_modules/intern/lib/util.js:818:13> at <node_modules/intern/node_modules/dojo/Promise.ts:393:15> at runCallbacks <node_modules/intern/node_modules/dojo/Promise.ts:11:11> at <node_modules/intern/node_modules/dojo/Promise.ts:317:4> at run <node_modules/intern/node_modules/dojo/Promise.ts:237:7> at <node_modules/intern/node_modules/dojo/nextTick.ts:44:3> at nextTickCallbackWith0Args node.js:489:9 at process._tickCallback node.js:418:13 TOTAL: tested 0 platforms, 0/0 tests failed; fatal error occurred

Does anyone have this working? I'm trying to find working tunnelOptions. This worked in FF50 to FF52

    tunnel: 'SeleniumTunnel',
    tunnelOptions: {
      // this tells SeleniumTunnel to download geckodriver
      drivers: [{
        name: 'firefox',
        version: '0.11.1'
      }],
      // version of Selenium
      version: '3.1.0'
    }

It's quite difficult to arrange setup + teardown behaviour with well-nested describe contexts in Intern: Intern only runs the beforeEach/afterEach for tests at the same describe/Suite level rather than for tests in descendant levels as well.

Other frameworks that offer BDD-interfaces with functions 'beforeEach' / 'afterEach' (e.g. Jasmine, RSpec) run the beforeEach functions before every test in the same level and all descendant levels.

With beforeEach not executing code before each and every test, I'm ending up having to construct a hierarchy of nested setup + teardown functions, which is very error-prone. I thought at first this was just my mistake, but having seen that at least Jasmine and RSpec drive beforeEach as I'd expect, this feels more like an issue in Intern? (I can't find an Intern test that is asserting its current nesting behaviour so I'm not sure it's intended.)

Here's some test code to illustrate in slightly more concrete terms:

define(["intern!bdd", "intern/chai!expect"], function(bdd, expect) {
    bdd.describe("Top-level describe", function() {
        bdd.before(function() {
            console.log("Top-level before");
        });

        bdd.beforeEach(function() {
            console.log("Top-level beforeEach");
        });

        bdd.after(function() {
            console.log("Top-level after");
        });

        bdd.afterEach(function() {
            console.log("Top-level afterEach");
        });

        bdd.it("Top-level it", function() {
            console.log("Top-level it #1");
        });

        bdd.it("Top-level it", function() {
            console.log("Top-level it #2");
        });

        bdd.describe("Nested describe", function() {
            bdd.before(function() {
                console.log("Nested-level before");
            });

            bdd.beforeEach(function() {
                console.log("Nested-level beforeEach");
            });

            bdd.after(function() {
                console.log("Nested-level after");
            });

            bdd.afterEach(function() {
                console.log("Nested-level afterEach");
            });

            bdd.it("Nested-level it", function() {
                console.log("Nested-level it #1");
            });

            bdd.it("Nested-level it", function() {
                console.log("Nested-level it #2");
            });
        });
    });
});

I would expect the following output:

Top-level before
Top-level beforeEach
Top-level it #1
PASS: Top-level it (1ms)
Top-level afterEach
Top-level beforeEach
Top-level it #2
PASS: Top-level it (1ms)
Top-level afterEach
Nested-level before
Top-level beforeEach
Nested-level beforeEach
Nested-level it
PASS: Nested-level it
Nested-level afterEach
Top-level afterEach
Top-level beforeEach
Nested-level beforeEach
Nested-level it
PASS: Nested-level it
Nested-level afterEach
Top-level afterEach
Nested-level after
Top-level after

(Not quite sure about some of the detail, but I'm definitely expecting to see the top-level beforeEach just before each nested-level beforeEach.)

however Intern 1.1 gives me:

Top-level before
Top-level beforeEach
Top-level it #1
PASS: Top-level it (1ms)
Top-level afterEach
Top-level beforeEach
Top-level it #2
PASS: Top-level it (1ms)
Top-level afterEach
Top-level beforeEach
Nested-level before
Nested-level beforeEach
Nested-level it
PASS: Nested-level it
Nested-level afterEach
Nested-level beforeEach
Nested-level it
PASS: Nested-level it
Nested-level afterEach
Nested-level after
Top-level afterEach
Top-level after

There's a good sample of RSpec behaviour described here: http://www.wulftone.com/2012/01/22/rspec-gotchas-before-after-all-and-each/

And another page which describes the usefulness of per-test beforeEach functions in Jasmine here: http://thatextramile.be/blog/2011/08/take-advantage-of-your-bdd-framework/

Thanks!

Provides a benchmarking API for the Intern, based on Benchmark.js. This includes self test unit tests. Let me know if you want to see any changes to the code.

Refs #13.

Individual calls to emit(<event>) currently start a new asynchronous promise chain. In the intern-cucumber plugin, this causes overlapping handling of the events, since the suiteEnd handling is not yet finished before the new suiteStart event is triggered. This problem is easily fixed by chaining this suiteStart event at the end of the suiteEnd chain.

• Testing engine framework hierarchy
• Determine what stays and what gets abstracted out
• Separate suites, tests, import object, import TDD, import BDD
• Work off of TS conversion branch

Bumps express from 4.17.1 to 4.17.3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps qs from 6.7.0 to 6.9.7.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps decode-uri-component from 0.2.0 to 0.2.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

There are small typos in:

• docs/api.md
• docs/architecture.md
• docs/configuration.md
• docs/how_to.md

Fixes:

• Should read without rather than wihtout.
• Should read something rather than somthing.
• Should read scripts rather than scriptss.
• Should read points rather than poitns.
• Should read information rather than informatioon.
• Should read functionality rather than funtionality.
• Should read dependency rather than dependecy.

Semi-automated pull request generated by https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

Bumps loader-utils from 1.4.0 to 1.4.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps minimatch from 3.0.4 to 3.0.5.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.