with Cucumber-java8, Cucumber Spring, custom annotation @PageObject, lambda expression ready, Selenide library and session manager (Selenium WebDriver) for:
- gradle
- Cucumber for Java plugin for IntelliJ
- Gherkin for IntelliJ
- chromedriver.exe (put it into project root)
- clone repository
- open build.gradle file in IDE (IntelliJ)
- import dependencies with gradle
- add your .feature files with scenarios
- create custom steps class / steps classes with @Autowired annotations for page objects class / classes
- generate steps- in .feature file press 'alt+enter' shortcut and choose 'Create step definition' option, choose created steps class / steps classes to paste steps
- create custom page objects classes with methods and with @PageObject and @Autowired annotations for webdriver manager
- delete example .feature files, steps classes and page objects classes
Add @PageObject in page object classes instead of Spring @Component annotation
Steps classes implements En interface and are prepared to use code by 'lambda-way'. Example of lambda expression is used in SignUpFormPageObjects class:
private void sendKeysForInputWithAttrubuteName(String partValueName, String keyToSend){
sessionManager.driver().findElements(By.cssSelector(USER_INPUT))
.stream()
.filter(elem->elem.getAttribute(USER_INPUT_ATTRIBUTE_NAME).contains(partValueName))
.findFirst()
.get()
.sendKeys(keyToSend);
}
If there is a need to use Selenide to find elements or take action, simply add one line in page object method:
WebDriverRunner.setWebDriver(your initialized driver);
Method in template, which is using Selenide to find element looks like below:
@PageObject
public class ActionPageObjects {
@Autowired
private SessionManager sessionManager;
private static final String JAM_MENU = ".Header-nav-item[href*=jam]";
public void clickJamMenu() {
WebDriverRunner.setWebDriver(sessionManager.driver());
$(JAM_MENU).click();
}
}
runTests
-Dbrowser=chrome runTests
clean test
clean -Dbrowser=chrome test
run CucumberRunner class
or run .feature file / directory with .feature files / scenario in .feature file
Reports are placed in 'target' directory, including screenshots of failed scenarios. To run report in browser, open 'target\html\index.html' file and choose browser.
Reports are placed in 'build' directory. To run report in browser, open 'build/reports/tests/runTests/index.html' file and choose browser.
- runTests
- deleteCucumberReports