karmatest | Test Opa5 tests in karma-openui5 | Unit Testing library

When I run Karma via PowerShell for the Baseline Branch, PowerShell reacts in a similar manner as though Environment::Exit(1) was executed if there are any failed tests in the results. This causes the Jenkins build to fail prematurely without running the remaining components. I want to bypass this so that the Job only fails if a legitimate issue arises, there are failing tests found when running karma against the Target Branch (branch containing code changes), or the code coverage percentage for new lines is lower than the required minimum.

I am working with Jenkins, PowerShell, and Karma to provide code coverage tests for a web application. In Jenkins, I have a PowerShell task that executes karma as so:

In the Job, I am checking out two branches (one to act as a baseline the other contains the code/test updates). I restore all NuGet packages, then build the solution of the Baseline Branch. Next, I run karma to get the current coverage. I then build the solution for the Target Branch, followed by running Karma to get the code coverage. Using SonarQube, I am comparing the results to provide new line coverage.

Things I have already tried:

• adding in -ErrorAction SilentlyContinue
• looking into the quality gates
• looking up documentation on karma start
• adding | $true and || $true to the end of the karma start command