Serge Huber created UNOMI-1033:
----------------------------------
Summary: Tracker: compatibility test harness
Key: UNOMI-1033
URL: https://issues.apache.org/jira/browse/UNOMI-1033
Project: Apache Unomi
Issue Type: Sub-task
Components: unomi-tracker
Reporter: Serge Huber
Tests that compare a new build of the tracker with a reference build on the
same pages, so we know a change does not affect existing websites. They run in
CI, without a Unomi server.
* Reference builds: the published 1.5.0, and 2.0.0 before the refactoring.
* A simulated Unomi answers the requests, including personalization results and
errors (500, timeout).
* Compared: requests (URL, headers, body), cookies, changes made to the page,
JS events dispatched, callbacks and their order, and the final digitalData.
* Scenarios cover the public API: context loading, clicks, forms, searches,
videos, personalization and optimization tests, digitalData overrides,
referrer, crawler detection, session and profile reset.
* Random ids and dates are fixed, so both builds can be compared exactly.
* Each intended difference is a named rule in the test (like the empty page
"attributes" today).
* Also checked: the methods of the tracker object and the generated TypeScript
types, the bundle formats (UMD, CommonJS, ES module) and the language level of
the output (it is not ES5 today, because es6-crawler-detect is not transpiled),
with a size limit.
Builds on test/servers/compare-1.5.0.spec.js, which covers only the context and
a click.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
