It's the easiest/laziest way to get correct test results

The router gadget handles all URL interaction (generation, parsing). It is also responsible to handle redirection (as redirecting for hash and HTML5 pushState is different).

Ensure that redirect "block" the application until cancellation of the current page rendering.
This will prevent unexpected result for function calling redirect (in case of 401 for example)

Error handling function should always throw the catched error by default

run_only option does not seem to support regular expression or comma separated list.

For now, test ERP5 page template related gadget + some standalone pages.

This used to generate a 404 error

erp5_gadget_interface_validator: updated URL navigation handling to follow modified erp5 launcher and router logic.

Makes syntax highlighting work with codemirror for Web Page, Web
Script and Web Style portal types.

/reviewed-by @jerome  (on !20)

that causes ZODB conflicts and it is meaningless in multiple destination case.

This redirection is specific to each application (cookie, token, erp5, another backend, etc)

Revert all recent changes to erp5_hal_json_style & erp5_web_renderjs_ui(_test) that were committed by mistake

Following @rafael advice on a related commit to slaprunner

    nexedi/slapos@c8c81baa
    nexedi/slapos!22 (comment 1780)

let's also leverage multicore when building NumPy- & Ruby- related
software under testnodes.

/reviewed-by @rafael, @seb  (on !23)

it can be used as both portal type action and workflow action.

also add 'Declare as Delivered' transition so that the created event can become directly delivered state.