No JUnit test report in sonar - junit

The unit test coverage is working but not the unit report, it tells me 0.
I have a multi module project in my sonar-project.properties I have these 2 lines defined :
# Tells SonarQube where the unit tests execution reports are
sonar.junit.reportsPath=target/surefire-reports
# Tells SonarQube where the unit tests code coverage report is
sonar.jacoco.reportPath=target/coverage-reports/jacoco-ut.exec
When I check in jenkins logs I see this :
Sensor JaCoCoSensor...
- Analysing C:\Users\Administrateur\workspace\MyProject\ModuleA\target\coverage-reports\jacoco-ut.exec
- Sensor JaCoCoSensor done: 8253 ms
Here path looks good but not for unit test reports :
- Sensor SurefireSensor...
- parsing C:\Users\Administrateur\workspace\MyProject\.sonar\sonar.projectKey_sonar.modules\target\surefire-reports
- Sensor SurefireSensor done: 0 ms
It looks into a .sonar/ directory at the root and not in the target/ directory of the module.
Any idea of the issue ? Thanks !

Related

TestCafe tests pass but job randomly fails [error]Process completed with exit code 1

The scenario is very similar to this one https://github.com/DevExpress/testcafe/issues/6804
Scenario:
I'm running a set of tests using testcafe, in a folder, with concurrency 4:
UI clicks
UI navigation
File upload scenario
Assertions
The job runs in github actions, with self-runners (docker container with no limits set) in AWS, using a properly sized m5.2xlarge box.
All goes well, tests pass, but randomly the job fails with an elusive error:
2022-06-11T08:10:53.9599698Z 30 passed (4m 34s)
2022-06-11T08:10:54.2336015Z Error:
2022-06-11T08:10:56.2617307Z ##[error]Process completed with exit code 1.
testcafe version 1.17.1
node version 14.17.18
I've tested changing/resizing the EC2 runner but didn't help. There are no errors on infra side, just the exit code 1 w/ no other details.
Is anyone else having this issue or have any advice on troubleshooting it?

How to resolve below error-ERROR: Child Process Error: Test runner sel (JUnitTester) has failed with retcode 1

When I ran the selenium script using Taurus and want to convert in JMX then got the error-
10:55:54 ERROR: Child Process Error: Test runner sel (JUnitTester) has failed with retcode 1
10:55:54 ERROR: JUnitTester STDERR:
May 02, 2022 10:55:50 AM com.blazemeter.taurus.junit.CustomRunner main
INFO: Starting: [C:\Users\sss\2022-05-02_10-55-36.435651\runner.properties]
Exception in thread "main" com.blazemeter.taurus.junit.exception.CustomRunnerException: Nothing to test
at com.blazemeter.taurus.junit.CustomRunner.main(CustomRunner.java:54)
How it resolved?
It means that Taurus JUnit Executor failed somewhere somehow, inspect logs in the Artifacts Directory and look for Java/JUnit-related errors there.
Most probably JUnit executor wasn't able to detect any test cases to run, it's impossible to tell for sure what is the root cause without seeing the full logs and your automation code.
Be aware that you can use another approach not involving Taurus, i.e.
Kick off BlazeMeter Proxy Recorder
Configure your tests to use the above recorder as the proxy
Run your tests from IDE or console
The BlazeMeter proxy recorder will capture the requests and convert them into .jmx file (you can also export it as "SmartJMX" with automatic detection and correlation of the dynamic parameters)

SSIS deploy package with variables using project parameters using package deployment model

There is an existing project(say Project1) which I am working on having
project param like
Name - Param_Local_Dir
Value - F:\Test\Company\Process\
In a package(say Package1) this project param is used in the package variables to identify the value
Name - Pkg_Local_Dir
Value - REPLACE( #[$Project::Param_Local_Dir], "Company", "AA")
The project was deployed into SQL Server using project deployment model and it was running with no issues through a scheduled job.
Now I need to deploy the package into the SQL Server as there is some changes(Integration Services Catalog -> project1 - right click -> Deploy Packages)
When I select the package from the package deployment window, it gives following error -
TITLE: SQL Server Integration Services
Warning:
The variables "$Project::Param_Local_Dir" were not found in the variable colletion. The variables might not exist in the correct scope.
Error:
1. The expression for variable "Pkg_Local_Dir" failed evaluation. There was an error in the expression.
We are not in a condition to do the whole project deployemnt again as there are many packages and this is the only package that is changed.
Is there any way this error can be fixed in order to do a package deployment?
Project Deployment mode and Package Deployment are completely different beasts. You cannot refer Project parameters within a Package deployed in Package deployment mode . That is the reason you are getting the errors.
In SSIS 2016 you can deploy single package from your project staying in Project mode, but not in SSIS 2012 or 2014.
In your case I would unload the Project from server, do necessary modifications to the package and deploy the updated Project back.

Getting Assemble script failed error building application in Redhat Openshift

I'm new to Redhat OpenShift and trying to deploy node application (with angularjs + mysql) and running into build issues.
Using openshift console created node application and in advanced options pointed to the private repository and linked configured secret (ssh key to private repository).
My build is failing with "Assemble script failed". Pasting the logs as below (from console - obfuscated private keys and values).
Not sure if I'm missing some configurations. Appreciate help on this.
Cloning "ssh://username#bitbucket.org/username/my-app.git" ...
Commit: xxxxxxxxxxxxxxxxx (Fixed readme)
Author: Name <email>
Date: Wed Sep 6 19:50:59 2017 -0700
Pulling image "docker-
registry.default.svc:5000/openshift/nodejs#sha256:0000000000000" ...
---> Installing application source
---> Building your Node application from source
Current git config
url.https://github.com.insteadof=git#github.com:
url.https://.insteadof=ssh://
url.https://github.com.insteadof=ssh://git#github.com
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
remote.origin.url=ssh://username#bitbucket.org/username/my-app.git
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
branch.master.remote=origin
branch.master.merge=refs/heads/master
---> Installing dependencies
---> Using 'npm install -s --only=production'
error: build error: non-zero (13) exit code from docker-
registry.default.svc:5000/openshift/nodejs#sha256:0000000000000
Pls note that my source code is hosted on private repository and per log above it appears openshift is able to access the repository and download the source code.
Thanks Graham for the pointer. I recreated the application and this time in advanced options on the web console selected 1 GB (from default of 500 mb) after which my build worked fine.

JUnit are failing when upgraded from JDK 1.6 to JDK 1.8 in maven, but its works in eclipse

I am using the JUnit for code coverage in my project. For db i am using the dbunit as like mock DB. When i am running JUnit from Eclipse UI its getting passed, but its getting failed when run through maven.
Above set up is running fine in JDK 1.6.25 by using maven and its started failing when upgraded to 1.8.51. I had updated the maven compiler plugin, its doesn't work. I am used below versions, junit - 4.7 2.dbunit - 2.4.8 hsqldb - 2.0.0 maven - 2.2.1.
Issue:
-> All test cases which ran fine in JAVA 1.6, started failing on migrating to JDK 1.8.51.
-> Due this we faced build failure issue and also code coverage reduction.
Root Cause:
-> JUnit uses Java reflection to get the test methods from Test classes. In JAVA 1.6 test method order returned as same as declaration in source file.
-> But from JAVA 7 onwards the methods order returned the by JVM is not same as the source file, it will be returned randomly.
-> Since our test cases are dependent on each other, due to order change it started failing.
For Example below test cases are using the same data (Mock DB) for execution,
-> AddOperationTestCase()
-> EditOperationTestCase()
-> DeleteOperationTestCase()
If delete run first due JVM random order, for Add and Edit data won't be available it will fail.
Solution :
-> I had tried to find options in JUnit and Sure Fire plugin to maintain same order as like source file, but I could not find feasibility there.
-> I have identified the class which will returns the order of execution in JUnit library and override that accordingly to run it source file order.
-> As of now I had added this annotation wrapper to failed classes, now build is running successfully.
Link for Wrapper class:
https://somethingididnotknow.wordpress.com/2014/03/07/run-junit-tests-in-order/