In most cases, we write a CI/CD workflow where all of the steps succeed. If a step fails, the job and workflow fails. But what do we do when we need the workflow to handle a failing step or job?
Continuing the topics from my last post, this week I want to offer a deep dive into the lifecycle of a Jest TestEnvironment by exposing the events that are raised when tests are run. I’ll also explore some of the details that are included with each event.
I needed a way to implement integration tests that would allow me to ensure that I could clean up the emulators I was using after each test cycle. Jest Test Environments provided a powerful way to do this, and TypeScript makes it easy to do (aside from a few quirks).
Trying to integrate unit tests and code coverage Azure DevOps to other systems and things seem to be disappearing? Learn why it happens and how to fix it…
