mediawiki-extensions-Discus.../tests/qunit/index.js

// TODO: Is there a way to set this only for our tests, rather than globally?
QUnit.dump.maxDepth = 999;

require( './parser.test.js' );
require( './modifier.test.js' );
require( './ThreadItem.test.js' );
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0 2019-10-24 12:59:42 +00:00			`// TODO: Is there a way to set this only for our tests, rather than globally?`
			`QUnit.dump.maxDepth = 999;`

Add unit tests for parser#getTimestampRegexp Depends-On: I6c3d186de1877f73d4a4e3fec7d6d632a5d5fa83 Change-Id: Icdb44f793a8f5e56666ec635bb8b0125041b5aab 2019-10-24 11:41:25 +00:00			`require( './parser.test.js' );`
Integration tests for the modifier Document the current behavior of the modifier (which inserts the replies into the DOM tree), so that we can more easily see the effect of changes in I2a70db01e9a8916c5636bc59ea8490166966d5ec. Basically, add a reply to every comment, and dump the resulting HTML, comparing it to previously generated expected HTML (which can be checked visually). Have a look at the new HTML files. Notably, the very first section in the "pl" example demonstrates a case of wrong reply location due to list gap :) (T242822). Change-Id: I4aed0f0b112f53d98e3fe1da4d40db8687c7e537 2020-01-21 22:01:11 +00:00			`require( './modifier.test.js' );`
Move #getAuthors from parser to ThreadItem Change-Id: I16e513000e5366b3044b17a99da07d8d0f47a61f 2020-07-20 14:13:59 +00:00			`require( './ThreadItem.test.js' );`