Details
-
Task
-
Resolution: Fixed
-
Neutral
-
None
-
None
Description
Reduced scope now
See comment on MGNLTEST-279 why scope has been reduced.
Now only adding support for
- webdriver creation - using same code as in junit-5-UI-tests
- This ensures having exact same selenium webdriver setup
- reading the values from IntegrationTestSettings which is a central point of configuration for UI/INT tests
- Support for VncRecorder
Totally skipping dependency management for cucumber - letting this to module where the real tests are.
We may add dependency management for cucumber once we split up the TF into separate modules including a TF BOM.
OLD DESCRIPTION
(Old summary: Cucumber support for test-fwk (incl. for UI tests)
General tasks
- Manage dependencies for cucumber libs
- Manage dependencies for JUnit-libs which are required to run cucumber tests
- Enable dependency injection which is (often) required for step-definition-classes
- Ensure the test-fkw can trigger cucumber style tests
- Add self-tests
Regarding UI tests
UI-tests are the main use-case for cucumber-style tests. In this context, make sure that:
- Handle webdriver life-cycle (initialize & destroy)
- Handle VNCRecorder life-cycle / record&save video for failed tests
Checklists
Acceptance criteria
Attachments
Issue Links
- mentioned in
-
Page Loading...