mirror of
https://github.com/smogon/pokemon-showdown.git
synced 2026-03-25 19:25:25 -05:00
a65faf263f
It turns out that when I switched us from `assert` to `assert.strict`,
I didn't actually update any existing tests or tell anyone:
0df0d234f2
So apparently everyone else just kept on using `strictEqual`.
This will be a PR and also throw an error if people continue trying to
use it, which should make it much clearer what PS policy is on this.
A lot of the problem may be that TypeScript marks assert.strict.equal
as deprecated when it's not. This was fixed 4 days ago:
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/48452
But this probably hasn't made it to a thing yet. Until then, you'll
have to deal with TS marking your tests as deprecated, but it shouldn't
be too long.
Accidentally using `assert` instead of `assert.strict` should now show
an error. This protects against the probably much worse mistake of
accidentally using `assert.equal` rather than `assert.strict.equal`.
`assert.ok` is also deprecated now.
19 lines
431 B
JavaScript
19 lines
431 B
JavaScript
/**
|
|
* Tests for the Hosts chat plugin
|
|
* Written by Annika
|
|
*/
|
|
|
|
'use strict';
|
|
|
|
const assert = require('assert').strict;
|
|
const hosts = require('../../../.server-dist/chat-plugins/hosts');
|
|
|
|
describe("Hosts plugin", () => {
|
|
it('should properly visualize an empty list of ranges', () => {
|
|
assert.equal(
|
|
hosts.visualizeRangeList([]),
|
|
`<tr><th>Lowest IP address</th><th>Highest IP address</th><th>Host</th></tr>`
|
|
);
|
|
});
|
|
});
|