Pipelines - improved test coverage
Test Plan
Introduction
Customer ticket (internal) resulted in two bugs being identified:
-
#35438 (closed)
- regular expressions in variables don't work properly
- this bug was found by the customer
-
#36940 (closed) - variables containing
$are cleansed of$prior to exporting the variables in the runner- I found this bug reproducing the customer's bug
- This one might be more end-to-end, will become clearer when the location of the bug is identified
It'd be great to improve the test coverage so customers aren't finding bugs like this; it's one of the parts of the product we consider (nearest to) lovable, but tripping over bugs isn't consistent with that experience ;)
In the case of the regex bug, the customer spent a lot of time trying to protect the regex when populating the variable, trying to protect the variable while using it .. but ultimately it was never going to work.
The customer specifically suggested improving test coverage in the ticket discussion. My background is an infrastructure engineer, no test or development, so how I would go about testing this is unlikely to be how it's done in practise. Given some guidance - so I don't go completely off piste - I can assist in fleshing out the test plan.
Scope
ACC Matrix
| Secure | Responsive | Intuitive | Reliable | |
|---|---|---|---|---|
| CI/CD | x | x |