This repository is supposed to be used as template for test automation projects using Neodymium Library. It contains both a pure Java and a Cucumber approach as well. A test automation template based on best practice libraries and added missing functionalities to aid test automation done by Xceptance.
Please perform the Hello World tutorial first to get a first insight and feeling for test automation with Neodymium. Afterwards you are ready to deep dive into more complex scenarios. Our Neodymium-example project demonstrates all the cool stuff that's possible with Neodymium. Furthermore, we set up a Neodymium Wiki to explain different concepts and use cases.
- Fork this project
- Rename the project (Open the
pom.xml
and adjust the name tag) - Import the project into an IDE of your choice. (It should be able to handle Maven project in order to sort all the dependencies for you)
- Set up WebDrivers and Browsers
- Open
config\browser.properties
- Set the property
neodymium.webDriver.chrome.pathToDriverServer
- Set the property
neodymium.webDriver.chrome.pathToBrowser
if you want don't want to use the default Chrome
- Open
- Add the URL to start in
template.settings.Settings.java
(or try with https://www.xceptance.com/en/ (already set) for demo purposes)
- Run the
template.neodymium.tests.smoke.HomePageTest.java
from the Neodymium package as JUnit test
- Uncomment
homepage.validateStructure();
within theHomePageTest.java
- Adjust the validation within the
template.pageObjects.pages.HomePage.java
to match the site that is going to be tested (only if you changed it) - Run the
template.neodymium.tests.smoke.HomePageTest.java
again
- Run the
template.cucumber.tests.RunAllTests.java
from the Cucumber package as JUnit test
If you want to adopt the template for your own project your certainly would like to change the template folder to something project specific. Please perform the following steps to rename it:
- Rename the
template
package to a name of your choice - Update the
pom.xml
(especially the Surefire configuration that states which tests should be executed) - Update the
@CucumberOptions
withintemplate.cucumber.tests.RunAllTests.java
to have the new path in features and glue
After you have decided whether you want to go the pure Java or the Cucumber way. You can simply delete the folder of the unused approach (either src/test/java/template/neodymium
or src/test/java/template/cucumber
).
If you like you can also clean up the Surefire configuration in the pom.xml
by removing the now unused <include>
path.
<includes>
<!-- Neodymium (pure Java) test cases -->
<include>template/neodymium/tests/**/*Test.java</include>
<!-- Cucumber test cases -->
<include>template/cucumber/tests/RunAllFeaturesTest.java</include>
</includes>
In case you want to use both approaches you are free to do so and take advantage of booth of their strengths.
MIT