How To Explain Selenium Automation Framework In Interviews

In this video we would explain Selenium Automation framework , how to explain selenium automation framework in interviews
explain test automation framework in interview,how to explain selenium test automation framework in the interview,explain framework in selenium,how to explain hybrid framework in selenium interview,selenium,selenium webdriver,java
How To Explain Test Automation Framework In Interviews For Selenium
How To Explain Automation Framework In Interviews For Selenium
How To Explain Framework In Interviews For Selenium

[QAstudioByAshish]

"HOW TO EXPLAIN SELENIUM AUTOMATION FRAMEWORK

1. Programming language: Our automation framework for the Arousr website was built using Java as the programming language. We implemented a data-driven framework, which allows us to separate the test data from the test scripts, promoting flexibility and reusability.

2. Framework Type: Data driven framework, keyword driven by using Page Object Model

3. POM: We followed the Page Object Model design pattern to maintain a class for each web page in the application. This approach helps in creating a clear separation between the page elements and their associated methods, making the code more maintainable and readable .As per the Page Object Model, we have maintained a class for every web page. Each web page has a separate class and that class holds the functionality and members of that web page. Separate classes for every individual test.

4. Packages: To organize our code effectively, we utilized separate packages for Pages and Tests. The Pages package contains the page class files, while the Tests package holds the test scripts. This structure helps maintain a clear distinction between the page actions and the test scenarios. For example, Payment Page and Login Page have separate classes to store element locators.

5. Properties file: We utilized a properties file named config.properties to store static information throughout the framework. This file includes details such as browser-specific information, application URLs for development and testing environments, screenshot paths, security questions and answers, and login credentials. Using a properties file allows easy configuration and modification without touching the code. This file (config.properties) stores the information that remains static throughout the framework such as browser-specific information, application URL, development, testing URL screenshots path, security questions and answers, username, passw(Ctrl)ing, development, testing URL, etc.

6. Screenshots: As part of our framework, we incorporated functionality to capture screenshots during test execution. Screenshots are captured at specific steps or on test failures, providing visual evidence and aiding in troubleshooting and debugging. Screenshots will be captured and stored in a separate folder and also the screenshots of failed test cases will be added to the extent reports.

7. Maven: We integrated Maven as our build and dependency management tool. It helped us manage project dependencies, handle libraries, and streamline the project's build process. Maven ensures that all necessary dependencies are resolved and enables efficient project compilation and execution. Using Maven for build, execution, and dependency purpose. Integrating the TestNG dependency in the POM.xml file and running this POM.xml file using Jenkins.


8. Version Control Tool: To track and manage code changes, we utilized a version control tool such as Git or SVN. This allowed us to collaborate with other team members, track revisions, and easily manage different versions of our automation framework.

9. Jenkins: For continuous integration and automation of our test execution, we leveraged Jenkins. Jenkins enabled us to schedule and execute our automated tests at specific intervals or on code changes, providing faster feedback on the application's stability. By using Jenkins CI (Continuous Integration) Tool, we execute test cases on a daily basis and also for nightly execution based on the schedule. Test Results will be sent to the peers using Jenkins.

10. Installer Batch Files: We created installer batch files to facilitate easy setup and deployment of our automation framework. These batch files automate the installation and configuration process, ensuring that all necessary dependencies and environment settings are in place. In case of desktop-based applications installation you would be keeping PowerShell batch files.

11. src/test/resources: AutoIT Scripts, Sikuli images, licenses to make your application under test up & running, etc files kept

12. Test Base Class: Test Base class (TestBase.java) deals with all the common functions used by all the pages. This class is responsible for loading the configurations from properties files, Initializing the WebDriver, Implicit Waits, Extent Reports. I

13. Reports : We incorporated reporting functionality to generate comprehensive test reports. These reports provide detailed information about test execution, including test results, pass/fail status, execution times, and any errors or exceptions encountered during the test run."

[VloggerBubu]

i saw a person who was writing framework in selenium in intellij and before he write a code there was cursor writing itself in gray color and this person just was choosing the options. it was amazing

[sanketsardar]

Thank You Sir, Was Struggling to explain Automation Framework, now got it 🙏🙏🙏

[sangeetasalian]

Thank you for such a detailed explanation…it’s so helpful..thank you for all your efforts to benefit others…appreciate it..

[mrdesigner]

Seriously yesterday night I was searching this today you are uploaded this video.
Thank you so much sir

[rahulnaikwade]

Much needed video and nicely explained Sir

[Maverism]

Thank you Rakesh sir for your detailed information....

[Imran_A]

Waited for this video long time sir
Thanks much

[prashantnikam]

very useful for interview preparation, thanks.

[poreshrautofficial]

Thank you very very very very very much sir for the information you have provided

[bhargavchandra]

Sir good explanation same thing if you make video on BDD cucumber how to explain in interview it would be great and boost confidence since most of the companies using bdd selenium framework

[divyakulkarni]

Thank you for this video. it will be more helpful if you share the document that you described in video

[MustafizurRahamanMustak]

Please make a video with these type of questions
1.How you integrating ExtentReport with Selenium ?
2.How you will fetch data from Excel in Data driven testing ?

3.Write the code for take screenshot or Scroll ?

4.How you implement OOPs concepts on your Framewormk explain?

5.What are things you can't Automate in that scenario what you will do ?

6.Your web application has a functionality like if logged in from India it will show location as India, if you logged in from London it will show London How you will test it ?

7.How to find all the broken links in a page ?

[saratmosuganti]

Sir I am really happy to see this perfect video for us ..How to say thank you I don't know

[sirishamacharla]

How can you proceed to write existing frame work? (Adding some function in application)

[nithyalakshmi]

Hi Sir,
Can you please explain the flow of execution where it starts and how it goes ? in this framework.Thanks in advance :)

[xcpegzc]

HOW TO EXPLAIN SELENIUM AUTOMATION FRAMEWORK
1. Programming language: Java
2. Framework Type: Data driven framework driven by using Page Object Model
3. POM: As per the Page Object Model, we have maintained a class for every web page. Each web page has a separate class and that class holds the functionality and members of that web page. Separate classes for every individual test.
4. Packages: We have separate packages for Pages and Tests. All the web page related classes come under the Pages package and all the tests related classes come under Tests package. For example, Payment Page and Login Page have separate classes to store element locators.
5. Properties file: This file (config.properties) stores the information that remains static throughout the framework such as browser-specific information, application URL, development, testing URL screenshots path, security questions and answers, username, passwc-ing, development, testing URL, etc.


The above screenshot illustrates a standardized maven project. As per the above maven project, all the tests are kept in the 'src/test/java'and remaining files (such as config.properties, element locators (POM classes files, test data, etc., ) kept under 'src/main/java'.

5.TestNG: Using TestNG for Assertions, Grouping, and Parallel execution.

6. Screenshots: Screenshots will be captured and stored in a separate folder and also the screenshots of failed test cases will be added to the extent reports.

7. Maven: Using Maven for build, execution, and dependency purpose. Integrating the TestNG dependency in the POM.xml file and running this POM.xml file using Jenkins.

8. Version Control Tool: We use Git as a repository to store our test scripts.
9. Jenkins: By using Jenkins CI (Continuous Integration) Tool, we execute test cases on a daily basis and also for nightly execution based on the schedule. Test Results will be sent to the peers using Jenkins.

10. Installer Batch Files: In case of desktop-based applications installation you would be keeping PowerShell batch files.

11. src/test/resources: AutoIT Scripts, Sikuli images, licenses to make your application under test up & running, etc files kept

12. Test Base Class: Test Base class (TestBase.java) deals with all the common functions used by all the pages. This class is responsible for loading the configurations from properties files, Initializing the WebDriver, Implicit Waits,
13.Reports. Extends reports

[sadhanaacharya]

Hi..Please share this document..this is really helpful..very nycly u are explaining..thanks..

[kalebtadesse]

Its helpful explanation please post documents

[nagalakshmirajasekaran]

Can you explain the java programming question, especially interviewer asked