servettonga / wr-52.taqc-java-testproject Goto Github PK

Shorten Xpaths:

• footer
• privacy
• terms
• about
• contact us

Currently, the project has its own implementation of randomizing data, as shown in the snipped below.

As mentioned by @ignatenko-paul it's a good idea to introduce Faker to do the job for you.

The goal of this issue is to replace the mentioned implementation with Faker.

Rename SamplePageTest to something more accurate.

1. The configs field could be an inline variable (inside the getConfig() method.
2. Instead of referencing it from the file new File("src/test/resources/test.properties") it would be better to use Resource, as it is more abstract and will work also if the project get's packaged in a jar

The structure of the Test Project should contain the directories according to PageObject Model.

Create a base allure setup.

1. Create a test that uses it
2. Document the process of setting it up locally in README.md

Check that the background image of the Landing page changes within 5 seconds

• check if all the categories are there
• check if email validation works correctly
• check if clear button works as expected

This page is available after login.

• create test proposals
• implement them

• Rename TestSetUp to BaseTest, so it's more meaningful. Also make it abstract
• constant names should be written in UPPERCASE

Implement tests for register user which tryin to login without confirm his email.

Instead of looking for the elements "by hand" a useful annotation could be used instead.

This how it looks in action:

import org.openqa.selenium.WebDriver;
 import org.openqa.selenium.WebElement;
 import org.openqa.selenium.support.FindBy;
 import org.openqa.selenium.support.PageFactory;
 
 public class LandingPage {
 
     @FindBy(css = "#Content a")
     private WebElement enterStoreLink;
 
     private WebDriver driver;
 
     public LandingPage(WebDriver driver) {
         this.driver = driver;
         PageFactory.initElements(driver, this);
     }
 
     public void clickOnEnterStoreLink() {
         enterStoreLink.click();
     }
 
 }

Refactor current pages to make use of this.

.env file is required to run the tests.

• create an empty (or a dummy) .env file in the correct place
• expand README.md with the fields that are required there

Click on the Terms Page link
Verify the display of the Terms heading