With the introduction of the new integration tests in our testing framework, it would help if we can identify easily when and where failures occur. The system is different than our current existing setup, so a little bit of knowledge share can go a long way…
This will be an ongoing article, but the first way to identify an error is when you see the following (see below). Cleaning up of the test suite whilst in the middle of a task, is a shore fire way to see that it exited early and was attempting to clean up all the things!
==> Cleaning up ====> Cleaning up jujus ====> Introspection gathering
I’ve made a card for me to update the script runner to dump out an error stack and make it much easier to identify issues.