0% found this document useful (0 votes)
94 views1 page

Automation Framework

The document outlines the key components of an automation testing framework including config properties, an Excel reader class, log and screenshot folders, application locators stored in properties files, page object and test base folders containing page and test classes, a test utility folder for custom methods, test scripts, a custom listener, a TestNG suite, and an Ant build file. The framework provides a standardized structure for organizing test artifacts and code to support running automated tests for a Java project.

Uploaded by

k varma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
94 views1 page

Automation Framework

The document outlines the key components of an automation testing framework including config properties, an Excel reader class, log and screenshot folders, application locators stored in properties files, page object and test base folders containing page and test classes, a test utility folder for custom methods, test scripts, a custom listener, a TestNG suite, and an Ant build file. The framework provides a standardized structure for organizing test artifacts and code to support running automated tests for a Java project.

Uploaded by

k varma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
You are on page 1/ 1

Framework

1. Automation project name:

Java project --- lot of packages / folder where we store (create lot of java files, xl data, property
file).

2. Config properties: URL, UID, PSWD, Browser types

3. Excel Reader: excel reader class which has all methods to read the data and write

4. Screen shots: where we store all failed screen shots.

5. Log folder: whenever we are running a script we need to know like how many lines has
been executed and if the script is failed at what point it got failed

We can do it in using 3 ways:

a. Log4j

b. Reporter class

c. Custom class writing log into test class.

6. Application locators (properties files, folder):

We perform action on the locators --- objects on the user interface (UI)

7. Page library folder:

Ex: Loginpage.java

8. Test Base folder: we need combine all the class, properties and packages

we have all objects installation e.g.: loading property files, installation of browser objects,
returning of web elements, excel sheets installation.

9. Test utility folder: we can override web driver methods

10. Test scripts:

11. Custom listener:

12. Test NG suite:

13. Build.xml:

You might also like