Automation Testing Mock Interview for Experienced | Automation Testing Interview Questions & Answers

Have a look at below Playlists:

Testing Interview Questions & Answers asked at various companies like Amazon, Capgemini, PayTM, Accenture, etc

Software Testing Mock Interviews

RPA (Automation Anywhere) Interview videos

This video contains Java interview questions, Selenium interview questions, TestNG interview questions and Database interview questions, Rest API interview questions, Manual Testing interview questions that were asked as part of Mock Interview Questions Process.

software testing interview questions,software testing tools,manual and automation testing mock interview,selenium automation testing mock interview,automation testing mock interview for experienced,manual testing mock interview for experienced,rd automation learning,automation testing interview questions for 3 years experience selenium,automation testing interview questions,automation testing interview questions and answers,automation testing interview mock,software testing questions guru99, hackerrank software testing interview questions

1. What are the different types of Maven Plugins?

Answer:

The different types of Maven plugins are listed below:

Building Plugins: These plugins are used at the time of build and are defined in the building element of the pom file.
Reporting Plugins: These plugins are used at the time of site generation and are defined in the reporting element of the pom file.

2. Name the build phases in Maven Build Lifecycle.

Answer: The build phases in Maven Build Lifecycle are listed down:

Validate: Checks if all the preconditions information to trigger the build is obtained.
Compile: Project source code is compiled.
Test: The Source code that is compiled is tested with the unit test framework. In this phase, the code is not deployed or packaged.
Package: Source code after compilation is packaged in the form of ZIP or JAR files.
Integration- test: After the package is deployed in an environment, the integration test cases are executed.
Verify: Examines to ensure that the package is correct and it meets all the required quality specifications.
Install: Installation of packages into the local repository.
Deploy: A specimen of the final package is made accessible to the remote repository for distribution among the other developers across projects.

3. What is the purpose of command mvn clean in Maven?

Answer: mvn clean aims to clean the project artifacts created by the previous Maven builds from the target directories. This is generally executed before initiating a new build process.

4. What do you mean by a Maven Repository?

Answer: Maven repository is the location of a directory where all the related project artifacts, jars, libraries, plugins are kept and can be utilized by Maven easily.

5. Explain the various types of Maven Repositories.

Answer: There are three types of Maven repositories.

They are:

Local Repository: This is placed in our local machine generally in the .m2 directory. This is generated once we are able to execute a Maven command successfully. All the project dependencies reside here. Once Maven scans the pom file, it first searches for its dependencies in the local repository.
Central Repository: This is supplied by Apache Maven. It contains most of the routinely used libraries. Once any of the dependencies are not found in the local repository, then Maven connects to a central repository.
Remote Repository: Sometimes companies develop their own custom repository comprising of their project artifacts, jars, and libraries. This is a type of repository that remains private for use inside that organization.

6. Selenium Automation - Exception - Element Isn’t Loaded Completely
In dynamic applications, elements are loaded on the fly. This means that all the elements you see aren’t completely ready. In such cases, if you try to click on the element, you’ll get the error. The solution to avoid this is to wait until the element is loaded completely.

7.What Causes the “Element Is Not Clickable at Point” Error?
Solution is to make sure that the overlapping element is closed before you try to click on another element. Another solution is to switch to the layer that contains the element you want to click.

8. Challenges faced in Automation

9. Handle Untrusted Certificate Selenium

10. Data-Driven Framework: In data-driven frameworks, test data is separated from test scripts and stored in an external resource such as text file, excel spreadsheet, CSV file or database table.

11. Keyword Driven Framework: In keyword driven frameworks, the test logic is divided into keywords and functions. A sequence of keywords is used to define the test scripts and these keywords are further defined as functions to implement the desired behaviour.

[rdautomationlearning]

Software Testing Mock Interviews Playlist

[nyc-night-eagles]

You are very good in explaining and making candidates comfortable with your gentle tone and respectful demeanor. Keep up the great work. Learning a lot from your videos and hopefully I will do well in my next interview.

[sachin]

soft assert is usually prefered, as we can assert a validation and keep the test case running, so that other fanctionality or validations can be verified, which are written after that assertion in the test case.

[revanth]

Usage of Assert totally depends on the scenario which you are going to verify...mostly hard assert we will use in Login Page becz if login not happened we cant execute other scenarios

[NeerajSingh-wbov]

It’s totally depends on the scenario which we are testing, we can use soft asset if the next test case doesn’t depends on the previous one, and we will use hard asset if the following execution of following test case depends on the current test case.
For example: If we want to test home age after login then we will use hard assert to verify if the login is successful or not, and if we want to just check that if the image is present on the page or not and doesn’t have to perform any action on that element then we will use soft assert.

[Learner-gu]

It totally depends on the functionality, but Hard assertions are important since it will block the execution immediately and error can be quickly observed.

[chandrashekharb]

Well done on the interview. I'll just share my knowledge here.
It is advised to proceed with a hard assert at the initial build stage, which involves writing the scripts module-by-module.

We use soft assert if you would like to view the complete outcome at the end of the test, i.e., if you would like to continue the test execution even after the test case fails.

[bhumidesai]

You are great sir! Most the time we work on such tools or systems but don’t know right way to explain at a time of an interview.Thank you for sharing great content😊

[vinavmevada]

It is totally depends on scenario which we are testing.

In hard asset it will abnormally terminate execution so whenever we are expecting actual results must be match with expected result in this case we can use hard assert.

But in you have scenario where you would like to verify broken link .To verify this scenario we have to store link in list webelemet and need to iterate loop in this scenario we should use softassert because for example if you have 100 link available and if 1st 2nd link is not working then it will abnormally terminate execution and it will not verify remaining link so we should use softassert to verify broken link in selenium.

[Different_Level]

Topic or subject can be different. But the way to communicate is wow. It's very helpful

[bhuviloganathan]

Thank u so much ji..last time I request you to give on videos on Jenkins and Mavens... within a week u had provided....thanks a lot 🙏🙏🙏🙏

[neha]

it is recommended to use hard assertions for critical test cases and soft assertions for non-critical test cases. You can also use a combination of both hard and soft assertions to achieve the desired level of test coverage.

[mdmokarram]

You're doing great work. from interview questions to the Q&A you share in description..amazing. and God bless.

[nellainayagam]

Rakesh sir doing a wonderful job for the QA aspirants hats off to u. Keep up the good work videos are very useful.

[snehachavre]

In soft and hard assert we can use one of the assert depends on the scenario that we have for example if wants to check login page is working or not then in this case we will use hard assert because if the first test case fails then there is no use to go further and check all the test cases...and we will use soft assert if we wants to check all the functionality of the software working fine or not if there is one or two test cases fails then it will goes further and check all other test cases are pass or fail .. it will depend on the situation that we have we can use assert..

[King_Kohli__loveever]

For critical functionality Hard Assert you can use in script but for other verifications Soft Assert is very good. According to your functionality, assertion you will use.

[MKB]

Great interview, thank you for sharing all details.It’s very helpful for those who need to get in to industry

[skaLife]

Thanks very much RD. Kindly do more of these experienced interviews.

[shivarajyadachi]

it depends on the scenario which assert we need to use, consider there is a Login failure using SoftAssert and there is no pointing of using for next verifications.

[exploreblog]

I prefer to use soft assert because in soft assert we can get all the failure at a time and fix at a time in other words due to time complexity u can use soft assert