How to use
Trackingplan’s Regression Testing module allows you to validate that the analytics performed in each test session match the expected baseline without changing your current tests in your current frameworks. Exactly, just plug & play.
Moreover, you can also consult the results of the tests directly within your CI/CD pipeline using our API.
Here are some of the features you’ll be able to enjoy with Trackingplan’s Regression Testing:
- Pages Diff
- Sequence Validations
- Request Log
All of them are designed to:
- Ensure your test executions do not break your analytics before going into production.
- Automatically document the regressions found between test sessions or specific test cases and their baseline to fix those errors before compromising your data.
- Establish baselines, making it possible to confirm a difference as desired so that the test session becomes the new baseline.
After selecting the test session, you’ll be able to instantly see the compatible baselines you can compare them with.
Moreover, you also have the option to filter your tests and baselines to quickly spot them.
Once you’ve found the test session and the compatible baseline you want to compare it with, click on the green button in the bottom right of the modal. With that, Trackingplan’s regression testing module will automatically check and compare all the regressions found between the two different executions focusing on the following aspects:
- Missing events: Check that all events exist as in your baseline.
- Unexpected events: Check that there are no undesired events that are not present in your baseline.
- Missing properties: Check that events carry all the properties they do in your baseline.
- Unexpected properties: Check that your events do not carry undesired properties that are not present in your baseline.
- Specification Warnings: All specification warnings are supported in Regression Testing:
If you want to have a closer view of the regressions found, the Pages Diff will show you on which pages these differences can be found. To find it, just click on Pages Diff in the event you want to investigate.
This will provide you with precise information about the specific pages Trackingplan has spotted extra or missing hits to know where the problem needs to be solved exactly.
Ready to try it out? Contact us to get Trackingplan’s Regression module and easily spot where your warnings are located with our Pages Diff.
Moreover, you can also validate Sequences to check within your critical paths if certain values still match from one event to another.
The possibilities are endless. Let’s see some examples!
- Validate that the property
product_skucarries the same value between all the events in a critical path like PageHit -> CatalogImpression -> AddToCart -> ProceedCheckout.
- Ensure that the event PurchaseConfirmed contains all the SKUs that have been added to the event AddToCart.
- Check, whenever an event AddToCart occurs, if it matches with a previous ProductImpression event.
- Make sure the event PurchaseConfirmed has in its "purchased items" parameter the same values as in the event AddToCart.
- Check that the ‘page type’ in ProductImpression matches the ‘page type’ in PageHit (which is the event that occurs when the page is loaded).
To automatically verify that your events don’t change or any properties get lost in transitions between pages, just write us to email@example.com with the Sequences to validate and we will add them for you.
After that, we will display in your panel a new section called Sequences, where you will be able to verify the status of these custom validations created according to your needs.
After comparing a test session or a specific test case with any of its compatible baselines and seeing that some regressions have been found between them, it’s time to fix those errors before compromising your data.
And for it, you will need meaningful contextual information about the regressions found.
Trackingplan’s Request Log provides you with key information about all the tracks generated throughout a session to get all the necessary details to analyze them locally and debug them easily.
You can either download in bulk all the tracks generated by a specific session or individually by looking at the date, the provider, and the name of the event along with the page where they are displayed.
Just contact us for more details to try it out.