I am trying to execute cucumber test from custom/another module than test however facing issue.
java.lang.IllegalStateException: Unable to locate CDIProvider
at javax.enterprise.inject.spi.CDI.findAllProviders(CDI.java:121)
at javax.enterprise.inject.spi.CDI.getCDIProvider(CDI.java:82)
at javax.enterprise.inject.spi.CDI.current(CDI.java:64)
at io.quarkiverse.cucumber.CucumberQuarkusTest$CdiObjectFactory.getInstance(CucumberQuarkusTest.java:184)
Not sure how to provide CDI to custom module. Any help on this would be appreciated.
I am able to execute cucumber test from test module however I want to separate it from JUnits.
The code is attached in Git issue:
https://github.com/quarkiverse/quarkus-cucumber/issues/38
Related
Im trying to using Cucable plugin for my cucumber automation framework, In order to be able to run scenarios and scenario outline in parallel and tests are getting skipped.
I tried to implement this using https://github.com/trivago/cucable-plugin#cucablerunner.
I followed each step but still I dont have success
I'm using serenity-cucumber-archetype project and run it in different ways (in pom I specified firefox as webdriver.driver and in serenity.properties -> chrome as webdriver.driver):
1. using test runner, which successfully runs the tests in Chrome
#RunWith(CucumberWithSerenity.class)
#CucumberOptions(features="src/test/resources/features/consult_dictionary/LookupADefinition.feature")
public class DefinitionTestSuite {}
using mvn site, which successfully runs the tests in Firefox
BUT, when I run separately *.feature file or single Scenario from *.feature file I get exception in run log:
Exception in thread "main" java.lang.NoClassDefFoundError: gherkin/formatter/Formatter
Please advise, how to fix it and to make it possible to run single Scenario or single *.feature file
If you are using IntelliJ and Cucumber v2.x:
You might need to upgrade IntelliJ, and/or the Cucumber-for-Java plugin.
If that doesn't work, try uninstalling/installing the plugin.
Bachground:
There are changed to the Cucumber event model as of Cucumber v2.x and the Cucumber-for-Java plugin has been updated for those.
I am trying to automation using groovy script in soapui for that I want to use http-builder. I worte code like this
#Grab(group='org.codehaus.groovy.modules.http-builder',modules='http-builder',version='0.5.2')
import statements
but when I run this it shows following exception:
org.codehaus.groovy.control.multipleCompilationErrorException:startup-failed Error Grabbing grape[unresolved dependency]javaRuntimeException
why I am getting this error. Is there any proxy problem?if yes where to add it?Please help me out
SOAPUI doesn't support Grapes as dependency management by default, so #Grab annotation doesn't work.
An alternative way to use http-builder is download all necessary libraries and place it on SOAPUI_HOME/bin/ext directory, restart SOAPUI in order to load it. Then you can use it on Groovy script testStep adding the necessary imports and so on.
Hope this helps,
I was tring to use mockito with arquillian.
I used with simple JUnit and it runs fine although i am trying to figure out the deployment for arquillian which is where i think the problem is !!!
Can anyone help me to figure out ?
Thank you.
Here is the link to my junit file and pom file
When you're using external libraries in your tests, you must make sure those libraries have been added to the microdeployment.
I need to run set of code after the build is completed. I use groovy postbuild plugin(version2.2). I am new to jenkins and groovy. I tried simple println but it is not working. I tried something like this and its also not working. I dont even see error message if i make any syntax or something.
and i see this output
can anyone tell me how do i use groovy postbuild ?
Your groovy postbuild configuration and syntax look fine to me.
I assume you are experiencing this with a Build Flow type job.
I can reproduce this behavior with a configuration similar to yours and I suspect that it is related to the build flow.
One solution that worked for me was to enable the Flow run needs a workspace checkbox in the Flow section of the job configuration and start a new build.