Chapril/xmpp.chapril.org-conversejs
Chapril/xmpp.chapril.org-conversejs
25
0
Fork 0
Code Issues Pull Requests Projects Releases Activity
3f24720633
xmpp.chapril.org-conversejs/spec/spoilers.js

242 lines
11 KiB
JavaScript
Raw Normal View History

Let message component listen for changes... and render directly from those Instead of doing it higher up in the chat view (which requires more function calls and iterating through all messages).
2020-09-26 21:42:57 +02:00
/* global mock, converse */
Use Karma as test runner
2020-04-22 13:11:48 +02:00
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
const original_timeout = jasmine.DEFAULT_TIMEOUT_INTERVAL;
Use Karma as test runner
2020-04-22 13:11:48 +02:00
describe("A spoiler message", function () {
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
beforeEach(() => (jasmine.DEFAULT_TIMEOUT_INTERVAL = 7000));
afterEach(() => (jasmine.DEFAULT_TIMEOUT_INTERVAL = original_timeout));
Use Karma as test runner
2020-04-22 13:11:48 +02:00
it("can be received with a hint",
Turn roster into a custom element
2021-01-26 14:01:37 +01:00
mock.initConverse(['chatBoxesFetched'], {}, async (done, _converse) => {
Use Karma as test runner
2020-04-22 13:11:48 +02:00
await mock.waitForRoster(_converse, 'current');
const sender_jid = mock.cur_names[0].replace(/ /g,'.').toLowerCase() + '@montague.lit';
/* <message to='romeo@montague.net/orchard' from='juliet@capulet.net/balcony' id='spoiler2'>
Turn the chat toolbar into a component - Declaratively render the emoji picker dropup - Got rid of converse-emoji-views - Adapt OMEMO to the new buttons stuff - Make emojis json global, to try and speed up tests - omemo: Move functions to the top of the module
2020-06-08 12:12:49 +02:00
* <body>And at the end of the story, both of them die! It is so tragic!</body>
* <spoiler xmlns='urn:xmpp:spoiler:0'>Love story end</spoiler>
* </message>
*/
Use Karma as test runner
2020-04-22 13:11:48 +02:00
const spoiler_hint = "Love story end"
const spoiler = "And at the end of the story, both of them die! It is so tragic!";
const $msg = converse.env.$msg;
const u = converse.env.utils;
const msg = $msg({
'xmlns': 'jabber:client',
'to': _converse.bare_jid,
'from': sender_jid,
'type': 'chat'
}).c('body').t(spoiler).up()
.c('spoiler', {
'xmlns': 'urn:xmpp:spoiler:0',
}).t(spoiler_hint)
.tree();
_converse.connection._dataRecv(mock.createRequest(msg));
await new Promise(resolve => _converse.api.listen.once('chatBoxViewInitialized', resolve));
const view = _converse.chatboxviews.get(sender_jid);
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
await new Promise(resolve => view.model.messages.once('rendered', resolve));
Use Karma as test runner
2020-04-22 13:11:48 +02:00
await u.waitUntil(() => view.model.vcard.get('fullname') === 'Mercutio')
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
expect(view.querySelector('.chat-msg__author').textContent.trim()).toBe('Mercutio');
const message_content = view.querySelector('.chat-msg__text');
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
await u.waitUntil(() => message_content.textContent === spoiler);
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
const spoiler_hint_el = view.querySelector('.spoiler-hint');
Use Karma as test runner
2020-04-22 13:11:48 +02:00
expect(spoiler_hint_el.textContent).toBe(spoiler_hint);
done();
}));
it("can be received without a hint",
Turn roster into a custom element
2021-01-26 14:01:37 +01:00
mock.initConverse(['chatBoxesFetched'], {}, async (done, _converse) => {
Use Karma as test runner
2020-04-22 13:11:48 +02:00
await mock.waitForRoster(_converse, 'current');
const sender_jid = mock.cur_names[0].replace(/ /g,'.').toLowerCase() + '@montague.lit';
/* <message to='romeo@montague.net/orchard' from='juliet@capulet.net/balcony' id='spoiler2'>
* <body>And at the end of the story, both of them die! It is so tragic!</body>
* <spoiler xmlns='urn:xmpp:spoiler:0'>Love story end</spoiler>
* </message>
*/
const $msg = converse.env.$msg;
const u = converse.env.utils;
const spoiler = "And at the end of the story, both of them die! It is so tragic!";
const msg = $msg({
'xmlns': 'jabber:client',
'to': _converse.bare_jid,
'from': sender_jid,
'type': 'chat'
}).c('body').t(spoiler).up()
.c('spoiler', {
'xmlns': 'urn:xmpp:spoiler:0',
}).tree();
_converse.connection._dataRecv(mock.createRequest(msg));
await new Promise(resolve => _converse.api.listen.once('chatBoxViewInitialized', resolve));
const view = _converse.chatboxviews.get(sender_jid);
await new Promise(resolve => view.model.messages.once('rendered', resolve));
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
await u.waitUntil(() => u.isVisible(view));
Use Karma as test runner
2020-04-22 13:11:48 +02:00
await u.waitUntil(() => view.model.vcard.get('fullname') === 'Mercutio')
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
await u.waitUntil(() => u.isVisible(view.querySelector('.chat-msg__author')));
expect(view.querySelector('.chat-msg__author').textContent.includes('Mercutio')).toBeTruthy();
const message_content = view.querySelector('.chat-msg__text');
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
await u.waitUntil(() => message_content.textContent === spoiler);
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
const spoiler_hint_el = view.querySelector('.spoiler-hint');
Use Karma as test runner
2020-04-22 13:11:48 +02:00
expect(spoiler_hint_el.textContent).toBe('');
done();
}));
it("can be sent without a hint",
Turn roster into a custom element
2021-01-26 14:01:37 +01:00
mock.initConverse(['chatBoxesFetched'], {}, async (done, _converse) => {
Use Karma as test runner
2020-04-22 13:11:48 +02:00
await mock.waitForRoster(_converse, 'current', 1);
mock.openControlBox(_converse);
const contact_jid = mock.cur_names[0].replace(/ /g,'.').toLowerCase() + '@montague.lit';
const { $pres, Strophe} = converse.env;
const u = converse.env.utils;
// XXX: We need to send a presence from the contact, so that we
// have a resource, that resource is then queried to see
// whether Strophe.NS.SPOILER is supported, in which case
// the spoiler button will appear.
const presence = $pres({
'from': contact_jid+'/phone',
'to': 'romeo@montague.lit'
});
_converse.connection._dataRecv(mock.createRequest(presence));
await mock.openChatBoxFor(_converse, contact_jid);
await mock.waitUntilDiscoConfirmed(_converse, contact_jid+'/phone', [], [Strophe.NS.SPOILER]);
const view = _converse.api.chatviews.get(contact_jid);
spyOn(_converse.connection, 'send');
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
await u.waitUntil(() => view.querySelector('.toggle-compose-spoiler'));
let spoiler_toggle = view.querySelector('.toggle-compose-spoiler');
Use Karma as test runner
2020-04-22 13:11:48 +02:00
spoiler_toggle.click();
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
const textarea = view.querySelector('.chat-textarea');
Use Karma as test runner
2020-04-22 13:11:48 +02:00
textarea.value = 'This is the spoiler';
view.onKeyDown({
target: textarea,
preventDefault: function preventDefault () {},
keyCode: 13
});
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
await new Promise(resolve => view.model.messages.once('rendered', resolve));
Use Karma as test runner
2020-04-22 13:11:48 +02:00
/* Test the XML stanza
Render chatbox message form via lit-html
2020-06-26 15:47:32 +02:00
*
* <message from="romeo@montague.lit/orchard"
* to="max.frankfurter@montague.lit"
* type="chat"
* id="4547c38b-d98b-45a5-8f44-b4004dbc335e"
* xmlns="jabber:client">
* <body>This is the spoiler</body>
* <active xmlns="http://jabber.org/protocol/chatstates"/>
* <spoiler xmlns="urn:xmpp:spoiler:0"/>
* </message>"
*/
Use Karma as test runner
2020-04-22 13:11:48 +02:00
const stanza = _converse.connection.send.calls.argsFor(0)[0].tree();
const spoiler_el = stanza.querySelector('spoiler[xmlns="urn:xmpp:spoiler:0"]');
expect(spoiler_el === null).toBeFalsy();
expect(spoiler_el.textContent).toBe('');
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
const spoiler = 'This is the spoiler';
Use Karma as test runner
2020-04-22 13:11:48 +02:00
const body_el = stanza.querySelector('body');
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
expect(body_el.textContent).toBe(spoiler);
Use Karma as test runner
2020-04-22 13:11:48 +02:00
/* Test the HTML spoiler message */
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
expect(view.querySelector('.chat-msg__author').textContent.trim()).toBe('Romeo Montague');
Use Karma as test runner
2020-04-22 13:11:48 +02:00
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
const message_content = view.querySelector('.chat-msg__text');
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
await u.waitUntil(() => message_content.textContent === spoiler);
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
const spoiler_msg_el = view.querySelector('.chat-msg__text.spoiler');
Fix show/hide of spoilers
2020-07-08 10:22:20 +02:00
expect(Array.from(spoiler_msg_el.classList).includes('hidden')).toBeTruthy();
Use Karma as test runner
2020-04-22 13:11:48 +02:00
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
spoiler_toggle = view.querySelector('.spoiler-toggle');
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
expect(spoiler_toggle.textContent.trim()).toBe('Show more');
Use Karma as test runner
2020-04-22 13:11:48 +02:00
spoiler_toggle.click();
Fix show/hide of spoilers
2020-07-08 10:22:20 +02:00
await u.waitUntil(() => !Array.from(spoiler_msg_el.classList).includes('hidden'));
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
expect(spoiler_toggle.textContent.trim()).toBe('Show less');
Use Karma as test runner
2020-04-22 13:11:48 +02:00
spoiler_toggle.click();
Fix show/hide of spoilers
2020-07-08 10:22:20 +02:00
await u.waitUntil(() => Array.from(spoiler_msg_el.classList).includes('hidden'));
Use Karma as test runner
2020-04-22 13:11:48 +02:00
done();
}));
it("can be sent with a hint",
Turn roster into a custom element
2021-01-26 14:01:37 +01:00
mock.initConverse(['chatBoxesFetched'], {}, async (done, _converse) => {
Use Karma as test runner
2020-04-22 13:11:48 +02:00
await mock.waitForRoster(_converse, 'current', 1);
mock.openControlBox(_converse);
const contact_jid = mock.cur_names[0].replace(/ /g,'.').toLowerCase() + '@montague.lit';
const { $pres, Strophe} = converse.env;
const u = converse.env.utils;
// XXX: We need to send a presence from the contact, so that we
// have a resource, that resource is then queried to see
// whether Strophe.NS.SPOILER is supported, in which case
// the spoiler button will appear.
const presence = $pres({
'from': contact_jid+'/phone',
'to': 'romeo@montague.lit'
});
_converse.connection._dataRecv(mock.createRequest(presence));
await mock.openChatBoxFor(_converse, contact_jid);
await mock.waitUntilDiscoConfirmed(_converse, contact_jid+'/phone', [], [Strophe.NS.SPOILER]);
const view = _converse.api.chatviews.get(contact_jid);
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
await u.waitUntil(() => view.querySelector('.toggle-compose-spoiler'));
let spoiler_toggle = view.querySelector('.toggle-compose-spoiler');
Use Karma as test runner
2020-04-22 13:11:48 +02:00
spoiler_toggle.click();
spyOn(_converse.connection, 'send');
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
const textarea = view.querySelector('.chat-textarea');
Use Karma as test runner
2020-04-22 13:11:48 +02:00
textarea.value = 'This is the spoiler';
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
const hint_input = view.querySelector('.spoiler-hint');
Use Karma as test runner
2020-04-22 13:11:48 +02:00
hint_input.value = 'This is the hint';
view.onKeyDown({
target: textarea,
preventDefault: function preventDefault () {},
keyCode: 13
});
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
await new Promise(resolve => view.model.messages.once('rendered', resolve));
Use Karma as test runner
2020-04-22 13:11:48 +02:00
const stanza = _converse.connection.send.calls.argsFor(0)[0].tree();
Test message stanza with spoiler
2020-06-28 02:43:35 +02:00
expect(Strophe.serialize(stanza)).toBe(
`<message from="romeo@montague.lit/orchard" ` +
`id="${stanza.getAttribute('id')}" `+
`to="mercutio@montague.lit" `+
`type="chat" `+
`xmlns="jabber:client">`+
`<body>This is the spoiler</body>`+
`<active xmlns="http://jabber.org/protocol/chatstates"/>`+
`<request xmlns="urn:xmpp:receipts"/>`+
`<spoiler xmlns="urn:xmpp:spoiler:0">This is the hint</spoiler>`+
`<origin-id id="${stanza.querySelector('origin-id').getAttribute('id')}" xmlns="urn:xmpp:sid:0"/>`+
`</message>`
);
Use Karma as test runner
2020-04-22 13:11:48 +02:00
Turn the chat toolbar into a component - Declaratively render the emoji picker dropup - Got rid of converse-emoji-views - Adapt OMEMO to the new buttons stuff - Make emojis json global, to try and speed up tests - omemo: Move functions to the top of the module
2020-06-08 12:12:49 +02:00
await u.waitUntil(() => stanza.querySelector('spoiler[xmlns="urn:xmpp:spoiler:0"]')?.textContent === 'This is the hint');
Use Karma as test runner
2020-04-22 13:11:48 +02:00
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
const spoiler = 'This is the spoiler'
Use Karma as test runner
2020-04-22 13:11:48 +02:00
const body_el = stanza.querySelector('body');
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
expect(body_el.textContent).toBe(spoiler);
Use Karma as test runner
2020-04-22 13:11:48 +02:00
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
expect(view.querySelector('.chat-msg__author').textContent.trim()).toBe('Romeo Montague');
Use Karma as test runner
2020-04-22 13:11:48 +02:00
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
const message_content = view.querySelector('.chat-msg__text');
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
await u.waitUntil(() => message_content.textContent === spoiler);
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
const spoiler_msg_el = view.querySelector('.chat-msg__text.spoiler');
Fix show/hide of spoilers
2020-07-08 10:22:20 +02:00
expect(Array.from(spoiler_msg_el.classList).includes('hidden')).toBeTruthy();
Use Karma as test runner
2020-04-22 13:11:48 +02:00
Work on turning chat views into custom elements The eventual goal is to avoid UI-related stanza processing if the relevant chats aren't in the DOM. With the current architecture, chatboxes are created (and the stanzas related to them processed) even if `#conversejs` isn't in the DOM. * Initial work on making controlbox an element * Create a shared base class * Ceate ChatBoxViews proxy * Update sass now that certain classes are moved to converse-chats element
2020-12-08 12:54:14 +01:00
spoiler_toggle = view.querySelector('.spoiler-toggle');
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
expect(spoiler_toggle.textContent.trim()).toBe('Show more');
Use Karma as test runner
2020-04-22 13:11:48 +02:00
spoiler_toggle.click();
Fix show/hide of spoilers
2020-07-08 10:22:20 +02:00
await u.waitUntil(() => !Array.from(spoiler_msg_el.classList).includes('hidden'));
Render chat messages as web components - Render chat content as a <converse-chat-content> component - Create new component for rendering the message body - Get rid of `showMessage` method
2020-05-15 14:33:31 +02:00
expect(spoiler_toggle.textContent.trim()).toBe('Show less');
Use Karma as test runner
2020-04-22 13:11:48 +02:00
spoiler_toggle.click();
Fix show/hide of spoilers
2020-07-08 10:22:20 +02:00
await u.waitUntil(() => Array.from(spoiler_msg_el.classList).includes('hidden'));
Use Karma as test runner
2020-04-22 13:11:48 +02:00
done();
}));
Remove the need for require.js to run tests
2020-04-22 12:10:39 +02:00
});
Reference in New Issue Copy Permalink