I'm upgrading a cucumber project to cucumber 6. But after the upgrade intellij doesn't recognize my steps anymore. When I run via my pom there is no issue. But if you try to go to the step definition from the feature file intellij says that there is no stepdefintion
My runner is like this
package be.nbb.hive.cucumber;
import io.cucumber.junit.CucumberOptions;
import net.serenitybdd.cucumber.CucumberWithSerenity;
import org.junit.runner.RunWith;
#RunWith(CucumberWithSerenity.class)
#CucumberOptions(
plugin = {"pretty"},
features = "src/test/resources/features",
glue = {"be.nbb.hive.cucumber.Steps"}
)
public class CucumberTestSuite {}
And my steps are in the package
package be.nbb.hive.cucumber.Steps;
Is this the issue or is it something else that blocks the recognision?
I had similar issue. Installing cucumber for java and gherkin IntelliJ plugins from marketplace resolved it for me
Related
I am currently working on creating a Test Suite using Cucumber framework. I have created feature files for each of the functionality I have to test.
The feature file never shows the conditions to be covered via glue code. On click of Recalculate steps it throws an error : An internal error occurred during: "Scanning for step definitions".
java.lang.NullPointerException
I tried to change the path of glue in the Test Runner class but it did not solve the problem as well. The feature can be executed without any issue and the code runs fine, only issue is feature files keep on stating that there is no matching glue code.
#OrderInteraction
#Orders
Feature: Validating Order functionality
Background: Pre-requisites of Order Functionality
Given WebDriver is initialized
And Website is up and running
When User Enter "Username" and "Password" as Credentials
Then Validate User Login
Test Runner :
package Cucumber;
import org.junit.runner.RunWith;
import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
#RunWith(Cucumber.class)
#CucumberOptions(features = "Features", glue=
{"src/main/java/CucumberStepDefinitions"})
public class CucumberTestRunner {
}
I would like to find a way in which Cucumber feature files can recognize the glue code present. Feel free to guide me to a existing question which answers this or a documentation which will be of help.
There is a possible solution in this discussion https://github.com/cucumber/cucumber-eclipse/issues/303
Which basically says to make sure you don't have
import cucumber.api.java.en.*;
in your steps files, and to use
import cucumber.api.java.en.Given;
import cucumber.api.java.en.Then;
import cucumber.api.java.en.When;
instead.
Which fixed it for me
I finally was able to find the solution to this issue. Issue lies with the cucumber plugin version, I referred to Cucumber-Eclipse-Update-SiteSnapshot for resolution.
The steps were as below :
1.From Eclipse, go to menu Help > Install New software
2.Work with: https://cucumber.github.io/cucumber-eclipse-update-site-snapshot
3.Select the check-box for Cucumber Eclipse Plugin
4.Select Next as per the instruction shown during installation.
5.Restart your Eclipse after completion of instruction.
Once the plugin was updated Feature file automatically scanned for steps and found the matching glue code.
How to run the JUnit test suite containing a set of test cases(groovy based) from the command line. Following is the test suite class generated by eclipse.
package com.example.testclasses;
import org.junit.runner.RunWith;
import org.junit.runners.Suite;
import org.junit.runners.Suite.SuiteClasses;
#RunWith(Suite.class)
#SuiteClasses({ abc.class, xyz.class })
public class AllTests {
}
The above test suite works when I run the above test suite(AllTests)as JUnit from eclipse, however, I want to run the test suite(AllTests) from the command line. How do I do this?
Info: I am using Geb(Groovy) based testing where all the test cases(example: abc, def) are groovy based(having .groovy extension).
If you wish to run your tests from the command line I would suggest using a build system. My personal choice would be to use Gradle but you could probably also get away with using Maven.
The benefit of using a build system, apart from being able to run the tests from the command line, is that it will help you manage your dependencies and it will be easier to build the project for others working on the same codebase - they won't have to manually setup all the dependencies and their versions in the IDE.
Try this:
java -cp /path/to/groovy/embeddable/groovy-all-1.8.1.jar groovy.lang.GroovyShell AllTests.groovy
where 1.8.1 should be replaced with your version of groovy-all-*.jar
I recorded a test case using Selenium IDE 1.10.0. I exported the case as Java/TestNG/Remote Control.
My Eclipse version is 4.2.0 and I installed TestNG plug-in version 6.8
I am wondering how can I create a project within the eclipse to run this exported test case?
Please give me some instructions or share with me some online tutorial / documentations. Thanks!
Below is the java code generated by the Eclipse:
package com.example.tests;
import com.thoughtworks.selenium.*;
import org.testng.annotations.*;
import static org.testng.Assert.*;
import java.util.regex.Pattern;
public class SearchDonor extends SeleneseTestNgHelper {
#Test public void testSearchDonor() throws Exception {
// set overall speed of the test case
selenium.setSpeed("4000");
selenium.open("/?html=openid");
selenium.click("css=input[type=\"submit\"]");
selenium.waitForPageToLoad("30000");
Thread.sleep(4000);
selenium.click("id=cmp_admin");
selenium.waitForPageToLoad("30000");
selenium.click("id=quicksearch_anchor");
selenium.click("css=img[alt=\"Member\"]");
selenium.waitForPageToLoad("30000");
selenium.type("id=search_name", "suzy");
selenium.click("css=input[type=\"image\"]");
selenium.click("link=Balagia, Suzy");
selenium.waitForPageToLoad("30000");
}
}
After some trial and errors. I managed to execute the exported code in Eclipse as TestNG Test. Here are the steps I took to make it compile.
1.created a Java Project within the Eclipse
2.add a class to the Java Project
2a. I copied and pasted the code into the newly created the class
3.Right click on the project>build path>configure build path
3a. on the Java Build Path window select libraries>Add External JARS, then adding all the JAR files from Selenium Java Driver folder (e.g. folder name in this case is libs), plus selenium-java-2.31.0.jar and selenium-java-2.31-src.jar
4.click the Run icon next the debug icon on the top menu bar, Run AS TestNG Test
My code is compiling, but I got some exception errors. I am getting stared on a TestNG test case!
import geb.Browser
import org.openqa.selenium.firefox.FirefoxDriver
Browser.drive {
go "google.com"
}
I run the script above and get the following error:java.lang.NoClassDefFoundError: org/openqa/selenium/TakesScreenshot
As it says on the documentation page (and in it's maven info), you need:
org.codehaus.geb:geb-implicit-assertions:0.7.2
org.seleniumhq.selenium:selenium-api:2.15.0
org.seleniumhq.selenium:selenium-support:2.15.0
selenium-api depends on google guava
and selenium-support depends on junit and hamcrest
You'll also need to add groovy to the classpath as geb uses it under the covers
I am using junit 4.8 and intellij 8 and i would like to only run tests inside the IDE which are named something like *UnitTest.java.
How can this be achieved?
Found a solution with cpsuite. http://www.johanneslink.net/projects/cpsuite.jsp
Pitty it's not in the maven repo.
import org.junit.extensions.cpsuite.ClasspathSuite;
import org.junit.runner.RunWith;
#RunWith(ClasspathSuite.class)
#ClasspathSuite.ClassnameFilters(".*UnitTest")
public class UnitTestSuite {
}