Skip to content

Yeti junit output for qunit tests doesn't contain testcase elements. #78

Description

@wdemoss

Running the latest version of qunit with the --junit flag produces incomplete an xml file. Here is my simple test case:

my index.html:

<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8">
  <title>QUnit Example</title>
  <link rel="stylesheet" href="qunit.css">
</head>
<body>
  <div id="qunit"></div>
  <div id="qunit-fixture"></div>
  <script src="qunit.js"></script>
  <script src="tests.js"></script>
</body>
</html>

my tests.js:

test( "hello test", function() {
  ok( 1 == "1", "Passed!" );
});

qunit.js was downloaded from http://code.jquery.com/qunit/qunit-1.14.0.js
qunit.css was downloaded from http://code.jquery.com/qunit/qunit-1.14.0.css

Yeti version:
$ yeti --version
0.2.27

I ran yeti:

$ yeti --junit index.html > junit.xml
Creating a Hub. Open `yeti --server` in another Terminal to reuse browsers for future batches.

Waiting for agents to connect at http://192.168.1.75:9000
...also available locally at http://localhost:9000
When ready, press Enter to begin testing.
  Agent connected: Chrome (33.0.1750.117) / Mac OS from 127.0.0.1

✓ Testing started on Chrome (33.0.1750.117) / Mac OS
✗ ✖ QUnit Example on Chrome (33.0.1750.117) / Mac OS

✓ Agent completed: Chrome (33.0.1750.117) / Mac OS
✗ Failures: 1 of 2 tests failed. (0.26 seconds)

The output junit.xml:

$ cat junit.xml 
<?xml version="1.0" encoding="UTF-8"?>
<testsuites>
<testsuite name="Chrome (33_0_1750_117) / Mac OS.✖ QUnit Example" failures="1" total="2" time="0.088">
</testsuite>
</testsuites>

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions