Tests and Testing - Ken Muse

Testing Kubernetes Operators and Controllers With Minikube

Fri, 27 Sep 2024 00:00:00 -0400

Sometimes you need to try out a modified image or custom chart you're creating in Kubernetes. Minikube can make that process easier.

How to Handle Step and Job Errors in GitHub Actions

Fri, 06 Sep 2024 00:00:00 -0400

In most cases, we write a workflow where all of the steps succeed. In this post, we'll explore how to create workflows that can handle a failing step or job.

Mastering the Jest TestEnvironment Event Types

Thu, 29 Aug 2024 00:00:00 -0400

If you're implementing a TestEnvironment, you'll need interact with the testing lifecycle. This post will explore events that are raised and how to use them.

A Crash Course on Jest TestEnvironments with TypeScript

Sat, 24 Aug 2024 00:00:00 -0400

Want to get the most out of Jest and you love TypeScript? Need some code that runs outside of the tests? Learn how (and why) to build custom TestEnvironments.

Restoring Azure Tests for SonarQube

Wed, 25 Sep 2019 00:00:00 -0400

Continuing from the previous post, SonarQube expects a certain set of files to be present in $(Common.TestResultsDirectory). When it doesn’t find the files in the folder, it can prevent it from reporting the results correctly. Because of changes to the vstest task, that folder is cleaned up once the tests results are uploaded, meaning that the files may not exist when SonarQube looks for them. We have a few options for resolving this issue.

Missing Tests on Azure DevOps

Tue, 24 Sep 2019 00:00:00 -0400

The customer was having a rough day. They had lots of unit tests, but were seeing an unexpected behavior from Azure DevOps and SonarQube. Because some tests were written in XUnit and others with MSTest, they had separated the execution into two tasks in their build. At the end of the build, results were sent to SonarQube for analysis. The problem was that each time the second set of tests ran in Azure DevOps, the results from the first pass disappeared. The assumption was that the files were being overwritten by the second test run. The fix seemed simple – copy the results before the second set of tests executed.