grunt-contrib-qunit - npm Package Compare versions

Comparing version 9.0.0 to 9.1.0

chrome/bridge.js

		@@ -110,2 +110,29 @@ /*

		// It is encouraged to listen to `qunit.on.testEnd` instead, so that you
		// don't have to deal with:
		// * grouping tests by test and module (testName provides "fullName",
		// and provides FailedAssertion in one go instead of per-assertion).
		// * inversion of "todo" tests (i.e. pass when failing).
		// * undefined actual/expected for passing tests.
		QUnit.log(function(obj) {
		var actual;
		var expected;
		if (!obj.result) {
		// Dumping large objects can be very slow, and the dump isn't used for
		// passing tests, so only dump if the test failed.
		actual = QUnit.dump.parse(obj.actual);
		expected = QUnit.dump.parse(obj.expected);
		}
		sendMessage('qunit.log', {
		result: obj.result,
		actual: actual,
		expected: expected,
		message: obj.message,
		source: obj.source,
		module: obj.module,
		name: obj.name,
		todo: obj.todo
		});
		});

		QUnit.done(function() {
		@@ -112,0 +139,0 @@ sendMessage('qunit.done');

package.json

		{
		"name": "grunt-contrib-qunit",
		"description": "Run QUnit unit tests in a headless Chrome instance",
		"version": "9.0.0",
		"version": "9.1.0",
		"author": {
		@@ -6,0 +6,0 @@ "name": "Grunt Team",

README.md

		@@ -1,2 +0,2 @@
		# grunt-contrib-qunit v9.0.0 [![Build Status](https://github.com/gruntjs/grunt-contrib-qunit/workflows/Tests/badge.svg)](https://github.com/gruntjs/grunt-contrib-qunit/actions?workflow=Tests)
		# grunt-contrib-qunit v9.1.0 [![Build Status](https://github.com/gruntjs/grunt-contrib-qunit/workflows/Tests/badge.svg)](https://github.com/gruntjs/grunt-contrib-qunit/actions?workflow=Tests)

		@@ -112,3 +112,3 @@ > Run QUnit unit tests in a headless Chrome instance

		When true, this will suppress the default logging for individually failed tests. Customized logging can be performed by listening to and responding to `qunit.log` events.
		When true, this will suppress the default logging for individually failed tests. Customized logging can be performed by listening to `qunit.on.testEnd` events.

		@@ -250,2 +250,3 @@ #### puppeteer
		* `qunit.begin`
		* `qunit.log` `(obj)`
		* `qunit.done`
		@@ -279,2 +280,3 @@

		* 2024-06-11 v9.1.0 Re-introduce `qunit.log` Grunt event.
		* 2024-06-09 v9.0.0 Update to Puppeteer 22. Require Node.js 18 or later. Remove [details parameter](https://qunitjs.com/api/callbacks/QUnit.done/) to Grunt event `qunit.done`, deprecated since QUnit 2.2. Remove Grunt events `qunit.testStart`, `qunit.log`, `qunit.testDone`, `qunit.moduleStart`, `qunit.moduleDone`. Use `qunit.on.*` instead.
		@@ -281,0 +283,0 @@ * 2023-09-16 v8.0.1 Add stack trace to uncaught errors.

New alerts