mavoweb/test

Unit tests for Mavo

test's Issues

Make it possible to automatically click on elements

This would help make many manual reftests automatic.

Requirements:

• Clicking by selector, since many of the elements that need to be clicked, are not present in the original HTML, but are generated afterwards. The attribute would be placed on either the whole table or individual tests (<tr>s).
• If selector is missing, target is the element itself
• Clicking should almost never happen immediately when the testsuite initializes. Usually what is needed is to specify after an event, and possibly a few seconds after the event. The event could default to DOMContentLoaded if not specified, so that plain time offsets can be used too.

Potential syntax:
data-click=".mv-bar .mv-save wait 5s after mv-load"
data-click=".mv-bar .mv-save wait 3s" (no event, DOMContentLoaded assumed)
data-click="wait 1s after load" (no selector, element assumed)

Add tests for `intersection(list1, list2)`

and() logical operator returns leftover number items when arrays are passed

So I was fixing the "bug" with binaryOperation(), and made changes so that new and old tests passed, except one:

This doesn't really make sense to me because and() and the contains() I'm implementing now are similar in that they both return booleans. We already established that the contains() function should only return booleans and instead of adding unprocessed array items into the return array. Yet here, the expected result of the and() does the exact thing that we decided is not right.

Should this be fixed or is there a difference between and() and contains() in terms of what they should return that I'm missing here?

Setting to use old versions of Mavo

I was trying to figure out what caused this regression and I realized this would be incredibly useful: A setting to use an older version of Mavo in the tests.

Not sure yet if this can be generalized into an htest feature, or if we should implement it here. I suspect it's simpler to implement it here and figure out if/how to generalize later.

An easy but dirty way to implement this is to use a URL param (?version=v0.2.0) and document.write() to output a <script> element with the correct URL. The downside is we'd need to do this on every single tests page. Maybe it's time to move htest to 11ty?