jdi-templates / jdi-light-testng-template Goto Github PK

View Code? Open in Web Editor NEW

7.0 23.0 5.0 21.47 MB

License: MIT License

Java 100.00%

jdi-light testng allure ui-testing jdi java automated-testing automation-ui selenium

jdi-light-testng-template's Introduction

JDI Light project template

For run new UI test automation just download and open this project Powered by JDI Light and Selenium

Instruction:

Download template and unpack in appropriate folder
Open project in IDE (for example IntelliJIdea)
For running demo tests:
- Maven: just use "mvn clean install" command
- IDE: run by click on "example" folder in src/test and select "Run tests"
Logs: Observe test run results in Console log
Reporting: After running tests just run allure:serve in maven plugins
Use as template for your project:
- just remove all content from src/main/.../example folder, add your package you Page Objects
- replace tests in src/test/.../example folder with your tests
TestNg Retry and before after listeners: You can also modify rules of retry tests (now it is 1 retry for each test) and actions before/after all tests (now it prints test name and result) in org.mytests.tests.testng folder

jdi-light-testng-template's People

Contributors

Stargazers

Watchers

Forkers

dmitriidobroliubov-epam nick130589 vklonin kkeerthipriya sergei820

jdi-light-testng-template's Issues

Only a suggestion. Maybe it'll be good to move strings like "FAILED", "PASSED", "ERROR: ", etc. to separate static final String variables

Maybe it'll be good to move next strings:
"PASSED",
"FAILED",
"SKIPPED",
"ERROR: ",
"UNKNOWN ERROR"
to separate static final String variables

Beta version of TestNG is used in dependencies 7.0.0-beta1

Unstable TestNG used in pom.xml:

        <dependency>
            <groupId>org.testng</groupId>
            <artifactId>testng</artifactId>
            <version>7.0.0-beta1</version>
        </dependency>

Download Driver always true

It doesn't matter what value you set in Test.Properties file. Project always want to download driver.

TestNG.xml (general.xml) file doesn’t find test classes because it searches in “packages”, not in classes

TestNG.xml (In this repository it named general.xml) file doesn’t find test classes because it searches in “packages”, not in classes.
Here's how to fix it:

Public modifier should be deleted in TestsInit interface’s methods

Public modifier should be deleted in TestsInit interface’s methods.
Default methods are implicitly public, there's no need to specify the public modifier.

screenshots doesn't attach to Allure report if jdiAssert fails test scenario

jdiAssert fails test scenario, but doesn't fail test step,
that's why there's no attached screenshots in steps, failed by jdiAssert and there is in steps, failed by UIElement.is() asserts.
(discovered while researching screenshot attachment trouble)

Template test run is not successfull

Exactly like in the build logs on travis, I receive an
java.lang.RuntimeException: java.lang.RuntimeException: Failed to do screenshot. No Drivers run Caused by: java.lang.RuntimeException: Failed to do screenshot. No Drivers run
exception after running the command mvn install/mvn clean install or while running a test in the IDE (eclipse) with TestNG Plugin.

Could you please fix this issue or at least explain, what should a beginner user do to make test run successful?

JDI framework doesn’t get "healdess" parameter from test.properties

JDI framework doesn’t get "healdess" parameter from test.properties.
Framework gets "healdess" parameter from common.properties and from driver name.properties.
Expected: possible to set the parameter in test.properties.
Actual: parameter in test.properties is ignored.

Also there's no description how this parameter works on https://jdi-docs.github.io/jdi-light/. Would be nice to add.