Géry Debongnie
abf32b8b21
This rev. introduces robust helpers to use in the JS tests suite to
interact with DOM and components, and starts using them (almost)
everywhere.
All the helpers are exposed though testUtils.js.
There are 2 kinds of helpers:
1. Assertions
-------------
* assert.containsNone, containsN, containsOnce check that the DOM
(or a specific part of the DOM) contains a `selector`. It
generates a correct error message automatically.
ex: assert.strictEqual(form.$('.o_form_editable'), 1, "msg");
-> assert.containsOnce(form, '.o_form_editable');
* assert.isVisible, isNotVisible check that the DOM has an element
visible or not. They also check that the element is actually in
the DOM (before most tests didn't verify this).
* assert.hasClass, doesNotHaveClass, hasAttrVAlue, check specific
properties of a DOM element, and also validate that it is
applied on a single existing DOM element (before most tests
didn't verify this).
ex: assert.notOk(form.$('button').hasClass('btn-primary'));
-> assert.doesNotHaveClass(form.$('button'), 'btn-primary');
2. Utilities
------------
The goal of the utilities is to centralize the definition of many
standard components and interactions, ensuring that when we
refactor the JS framework, we do not need to change all the tests.
Existing mock utilities (addMockEnvironment, intercept, path,
patchDate, unpatch and fieldsViewGet) are moved to
'testUtils.mock.*'.
Existing DOM utilities are moved to 'testUtils.dom.*'.
New dom utilities are created for opendDatePicker, click,
clickFirst and clickLast. Helper `click` verifies that there is
exactly 1 element visible in the DOM you click on, `clickFirst`
and `clickLast` verify that there are more than one element on the
DOM.
ex: form.$('button').click();
-> testUtils.dom.click(form.$('button'));
New Form utilities: (testUtils.form.*)
clickEdit, clickSave, clickCreate, clickDiscard, all clicks on
the control panel buttons of the form.
`reload` reloads the form data.
New modal, graph, kanban and pivot utils (testUtils.pivot.*,
testUtils.kanban.*, etc.).
New fields utils: (testUtils.fields.*)
* editInput, editSelect: allow to change the value of a field,
using a selector to identify it. They validate that the input
exists and trigger the change event automatically.
* editAndTrigger: allow to modify a field and trigger specific
events after the value change
* many2one (testUtils.fields.many2one.*)
clickOpenDropdown, clickHighlightedItem, clickItem,
searchAndClickItem: use a field name instead of a selector and
do all the complex mechanism to open, filter and highlight
many2one fields.
Joint work with aab, dam, ged, mge, svs and vsc.
95 lines
3.0 KiB
JavaScript
95 lines
3.0 KiB
JavaScript
odoo.define('web.pager_tests', function (require) {
|
|
"use strict";
|
|
|
|
var Pager = require('web.Pager');
|
|
var concurrency = require('web.concurrency');
|
|
var testUtils = require('web.test_utils');
|
|
|
|
QUnit.module('chrome', {}, function () {
|
|
|
|
QUnit.module('Pager');
|
|
|
|
QUnit.test('basic stuff', function (assert) {
|
|
assert.expect(2);
|
|
|
|
var pager = new Pager(null, 10, 1, 4);
|
|
pager.appendTo($('#qunit-fixture'));
|
|
|
|
assert.strictEqual(pager.state.current_min, 1,
|
|
"current_min should be set to 1");
|
|
|
|
// click on next
|
|
testUtils.dom.click(pager.$('.o_pager_next'));
|
|
assert.strictEqual(pager.state.current_min, 5,
|
|
"current_min should now be 5");
|
|
|
|
pager.destroy();
|
|
});
|
|
|
|
QUnit.test('edit the pager', function (assert) {
|
|
assert.expect(5);
|
|
|
|
var pager = new Pager(null, 10, 1, 4);
|
|
pager.appendTo($('#qunit-fixture'));
|
|
|
|
// enter edition
|
|
testUtils.dom.click(pager.$('.o_pager_value'));
|
|
assert.containsOnce(pager, 'input',
|
|
"the pager should contain an input");
|
|
assert.strictEqual(pager.$('input').val(), '1-4',
|
|
"the input should have correct value");
|
|
|
|
// change the limit
|
|
pager.$('input')
|
|
.val('1-6')
|
|
.trigger($.Event('keydown', {which: $.ui.keyCode.ENTER})); // trigger the change
|
|
assert.strictEqual(pager.state.limit, 6,
|
|
"the limit should have been updated");
|
|
assert.strictEqual(pager.state.current_min, 1,
|
|
"the current_min should not have changed");
|
|
assert.strictEqual(pager.$('.o_pager_value').text(), '1-6',
|
|
"the input should have correct value");
|
|
|
|
pager.destroy();
|
|
});
|
|
|
|
QUnit.test('disabling the pager', function (assert) {
|
|
var done = assert.async();
|
|
assert.expect(4);
|
|
|
|
var pager = new Pager(null, 10, 1, 4);
|
|
pager.appendTo($('#qunit-fixture'));
|
|
|
|
pager.disable();
|
|
|
|
// try to go to the next or previous pages
|
|
testUtils.dom.click(pager.$('.o_pager_next'));
|
|
assert.strictEqual(pager.state.current_min, 1,
|
|
"current_min should still be 1");
|
|
testUtils.dom.click(pager.$('.o_pager_previous'));
|
|
assert.strictEqual(pager.state.current_min, 1,
|
|
"current_min should still be 1");
|
|
|
|
// try to change the limit
|
|
testUtils.dom.click(pager.$('.o_pager_value'));
|
|
assert.containsNone(pager, 'input',
|
|
"the pager should not contain an input");
|
|
|
|
// a common use is to disable the pager before reloading the data, and
|
|
// re-enable it once they have been loaded
|
|
// the following imulates this situation
|
|
pager.on('pager_changed', null, function () {
|
|
pager.disable();
|
|
concurrency.delay(0).then(function () {
|
|
assert.ok(pager.disabled, "pager should still be disabled");
|
|
pager.destroy();
|
|
done();
|
|
});
|
|
});
|
|
pager.enable();
|
|
testUtils.dom.click(pager.$('.o_pager_next'));
|
|
|
|
});
|
|
});
|
|
|
|
}); |