In a Spring Roo project the tests fail but only when initiated from Infinitest running in Springsource Tool Suite 2.8.0 (STS). As Infinitest 5.1.93 fails to load the Spring context file all tests fail. When I run the same tests myself inside STS they all go green.
I reconfirmed that nothing else was wrong in this project by importing the project to the previous STS 2.7.x instead. Infinitest run the tests green under STS 2.7.x as expected.
Is Infinitest 5.1.93 currently not compatible with Eclipse Indigo and Springsource Tool Suite?
I currently use jdk1.5.
P.S. I initially wrote "Eclipse Juno" so corrected the question to Indigo. See comments below. D.S.
You can solve that problem not using the classpath: for the resource loading but the file: mechanism:
#ContextConfiguration({ "file:src/test/resources/context.xml" })
#RunWith(SpringJUnit4ClassRunner.class)
Related
We have an nunit3 test project that we're trying to run via command-line in dotnet core that is having problems being identified. In all our debugging we've not found an answer to fixing this.
Background: We build out these tests to test an API site after it's been deployed, alongside standard unit testing. So we package the test up as a DLL to run after we've built out the site, and configure it to run against the site. On our local machines, the tests can't be identified until we install Resharper on our Visual Studio.
After attempting a
dotnet test "path\to\bin\release\Test.dll"
we get the error:
No test is available in path\to\bin\release\Test.dll. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.
Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:.
According to Resharper site, the tools require the run: dotnet tool install -g JetBrains.ReSharper.GlobalTools
doing so I've found the adapters at
C:\Users\USER\.dotnet\tools\.store\jetbrains.resharper.globaltools\2020.3.2\jetbrains.resharper.globaltools\2020.3.2\tools\netcoreapp3.1\any\TestRunner\Adapters
but when trying to load a given adapter dll using /TestAdapterPath, it says it can't find it. any idea how to get this test running?
Ensure your test project has a reference to the test adapter built in:
<PackageReference Include="NUnit3TestAdapter" Version="3.17.0" />
can be pulled from nuget package manager in Visual studio or placed into the section with all other package references.
after this, run dotnet test against your built DLL
I want to run a DotNet5 Console app on Yocto Linux (Dunfell). We run this on a iMX8MM based CPU module. I have followed the manufacturers guide to clone the repos and have a custom Yocto Build running.
The Issue I'm now having is that a Hello World c# app compiled as a self-contained DotNet5 app gives this error:
./VarisciteTest: error while loading shared libraries: libgssapi_krb5.so.2: cannot open shared object file: No such file or directory
When I compile the same app as DotNetCore 3.1 it runs just fine.
I tried adding CORE_IMAGE_EXTRA_INSTALL += "krb5" to the local.conf (as a quick test) but that does not help.
Can someone tell me what dependency I need to add to Yocto to make Dotnet5 apps run?
I figured out that you need to add this:
libgssapi-krb5
to the recipe of the Yocto build.
I'm using JBDS 11.3.0.GA on Ubuntu 16.04 LTS. I'm generating a Fuse project for Fuse 7.1.0 on standalone Karaf platform, using the camel-spring-cxf-code-first template. The project generates correctly but, trying to run it as described by the ReadMe.txt file fails. For example, after installing the bundle as follows:
karaf#root()> install -s mvn:com.mycompany/camel-spring-cxf-code-first/1.0.0-SNAPSHOT
Bundle ID: 223
karaf#root()>
trying to go to http://localhost:8181/cxf/report/?wsdl (of course, after having replaced in the generated code 9292 by 8181) displays "No service was found." in the browser and shows the following in the log file:
16:33:36.209 WARN [XNIO-4 task-1] Can't find the the request for http://localhost:8181/cxf/report/'s Observe
meaning that the generated project is not valid.
Kind regards,
Nicolas
The deployment of this kind of projects is not working at the moment - see the following statement in the Readme.txt file.
Note: This project does not currently work. It has some issues. It is based
on the archetype.
I raised an issue for developers - https://issues.jboss.org/browse/FUSETOOLS-3177.
When I run Corda flow tests from IntelliJ, the tests fail with the following errors:
QUASAR WARNING: Quasar Java Agent isn't running. If you're using
another instrumentation method you can ignore this message; otherwise,
please refer to the Getting Started section in the Quasar
documentation.
and
java.lang.IllegalStateException: Missing the '-javaagent' JVM
argument. Make sure you run the tests with the Quasar java agent
attached to your JVM. See https://docs.corda.net/troubleshooting.html
- 'Fiber classes not instrumented' for more details.
How can I fix this?
Corda flows need to be instrumented using Quasar before they are run, so that they can be suspended mid-execution.
To achieve this in IntelliJ, you need to:
Create a run config for your tests
Open the run config and change the VM options to -ea -javaagent:PATH-TO-QUASAR-JAR
In the CorDapp example and templates, quasar.jar is located at lib/quasar.jar, so you'd use -ea -javaagent:../lib/quasar.jar
Alternatively, you can edit the default JUnit run config to use the Quasar javaagent by default, avoiding you having to do this every time you pick a new test to run.
This is a basic error that you get if you don't set Quasar, you need to select your test-> go to Intellij top bar-> Run -> Edit Configurations and then set up like this photo in VM options:
From template readme
We recommend editing your IntelliJ preferences so that you use the Gradle runner - this means that the quasar utils plugin will make sure that some flags (like -javaagent - see below) are set for you.
To switch to using the Gradle runner:
Navigate to Build, Execution, Deployment -> Build Tools -> Gradle ->
Runner (or search for runner) Windows: this is in "Settings" MacOS:
this is in "Preferences" Set "Delegate IDE build/run actions to
gradle" to true Set "Run test using:" to "Gradle Test Runner" If you
would prefer to use the built in IntelliJ JUnit test runner, you can
run gradlew installQuasar which will copy your quasar JAR file to the
lib directory. You will then need to specify -javaagent:lib/quasar.jar
and set the run directory to the project root directory for each test.
Btw, if you face same error in VSCode, you can add
"java.test.config": {
"vmArgs": ["-ea", "-javaagent:../lib/quasar.jar"]
},
to settings.json. The path ../lib/quasar.jar may be different in your project.
i just started using jhipster and face a problem already,
here's my development stack :
- os windows 7
- eclipse Juno
- maven 3.1
- latest node and npm
- mysql as db in ubuntu vm
and here's what i have done :
- generate jhipster "yo jhipster"
- convert it to maven project "mvn eclipse:eclipse"
- maven compile "mvn clean" & "mvn install"
- add jhipster-reload feature in eclipse run vm arguments
- and run the main class in eclipse "right click Application.java and run as java application"
- generate new entity yo jhipster:entity ala
- everything was pretty much generated for this new entity, only the liquibase changelog doesn't generated
- i try to recompile the maven from eclipse then i found the line below
[ERROR] io.github.jhipster.loaded.JHipsterFileSystemWatcher - Failed to register the directory 'target\classes\config\liquibase\changelog'
- AFAIK it seems to be the same bug here, but they says it's fixed
Thanks for anyone that could help this, i'm confused as what to do here as i'm new to jhipster, liquibase, hot reload concept, and the documentation or google search barely help as jhipster is relatively still young.
Do not use "mvn eclipse:eclipse" in jhipster projects.
Just import the project as existing Maven project.
See this.