Details
-
Task
-
Resolution: Won't Do
-
Neutral
-
None
-
None
-
None
Description
While working on MGNLTEST-268 ...
... changes on the pom, adding depenencies used by cucumber ...
cucumber-ui-tests are triggered ...
BUT "normal" UI tests are not triggered anymore.
Actually IntelliJ is also does not launch the "normal" ui-tests anymore.
List of some of the "normal UI tests" in the test-fwk:
- it.info.magnolia.test.selenide.pageobjects.UiTestSelenideOnly
- all tests in package it.info.magnolia.test.selenium
How it should work
- junit5 UI-tests still can be launched via IDE
- cucumber ui-tests also can be launched via IDE via feature-file

- running mvn clean install -Pintegration-tests still works - launching the int tests

- cucumber INT/ui-tests alsco can be launched via mvn
e.g. via mvn clean install -Pcucumber-integration-tests
- (3) and (4) can be run both together in one "build"

P.S. (2) seems to work - but it is not exectuting code from it.info.magnolia.test.cucumber.ui.CucumberTests (which e.g. setups the webdriver)
The above "how it should work" adds a new profile. This means that we also need to adapt a jenkins-template.
Furthermore, ideally we use latest cucumber-libraries (see POM, cucumber-BOM, currently it is 7.0.0)
This also means that the java-class should not use @RunWith(Cucumber.class), @CucumberOptions),
But should use @Suite, see CucumberTests
Developer notes
See PR https://git.magnolia-cms.com/projects/PLATFORM/repos/test-framework/pull-requests/189/overview for changes on the pom
Checklists
Attachments
Issue Links
- is related to
-
MGNLTEST-280 (Consider) proper cucumber scenario testing reporting
-
- Closed
-