UI Test Automation Framework

Question 1

What is POM?

Answer 1

A page object or a page class is basically a representation of all or some of the actions and operations which can be performed on that page of your application. POM (Page Object Model) is a design pattern that is used in selenium test automation for organizing the helper code for maintainability and reducing code duplication.

Question 2

What is LoadableComponent?

Answer 2

LoadableComponent is a base class that aims to ensure:
    Pages are loaded.
    The initial state of the page is asserted.
    The elements are intractable before we use them.

Question 3

WebDriver Manager

Answer 3

create our web driver objects in a way that it can handle parallel runs

Question 4

BaseTest

Answer 4

super class for all test classes

Question 5

locators file

Answer 5

Locators file could be of any format, such as .properties, .xml, .json, .yaml, .ini, .toml. For demonstration purposes, .properties is considered.

Question 6

Need for DataManager

Answer 6

Oftentimes, we will be using some static test data that is specific to an environment. The environment could be staging, production, development, etc For maintaining the environment, we can have a separate class for managing that.

Question 7

Sample page objects

Answer 7

when creating instances of the pages, we need to call get() to take advantage of the LoadableComponent feature.

Question 8

Abstract Base Test class

Answer 8

Abstract base test class will be a superclass for all test files; it will have driver initialization, navigating to launch Urls and will have common functionalities used across the test classes

Question 9

Best practices for automation

Answer 9

No hardcoding of test data in a test class.
Add logs for important steps.
Lots of meaningful assertions should be added.
No hard coding of configurations.
Page operations should be part of the page object class.
Helpers for DB, files, etc., should be part of utility class.
Add proper test comments.
Give meaningful names to the test methods and follow java naming conventions.
Group tests (such as sanity, regression, P0, etc.).
Avoid dependent tests.

Question 10

Building a gradle project#

Answer 10

gradle clean build -x test

Question 11

Tests for allure steps and attaching screenshots on failure:

Answer 11

gradle clean test –tests “com.educative.test.TestGoogleSearch” -Dbrowser=chrome

Question 12

Overriding configuration from command line

Answer 12

gradle test -Dbrowser=firefox

Question 13

Generated report paths

Answer 13

TestNG - ./test-output/index.html
Allure - ./build/reports/allure-report/index.html
Gradle - ./build/reports/tests/test/index.html

Question 14

./gradlew clean build -x test

Answer 14

Generating the test Framework Jar. The project will be cleaned, compiled and the distribution jar will be created along with Javadoc and sources

Question 15

Uploading the test Framework Jar

Answer 15

./gradlew uploadArchives

Question 16

Distribution of Test Framework Library

Answer 16

Create the framework jar using any build management tool (Maven or Gradle).
Upload the binary to the Artifactory (hosted locally or remotely).
Create a Java test project and download the binary as a dependency for writing and executing tests.
Setup Jenkins or any CI tool.
Create a job for running tests via CI tool.
Reports will be shared to stakeholders.

Question 17

Artifactory

Answer 17

used for hosting the framework jar or library

Question 18

Code Repository

Answer 18

repository to host the framework code and test project code ( GitHub, BitBucket, etc.)