Automation Testing Mock Interview for Experienced | Automation Testing Interview Questions & Answers
Vložit
- čas přidán 18. 08. 2021
- Have a look at below Playlists:
Testing Interview Questions & Answers asked at various companies like Amazon, Capgemini, PayTM, Accenture, etc
• Amazon Interview Quest...
Software Testing Mock Interviews
• What is Software Testi...
RPA (Automation Anywhere) Interview videos
• What is RPA?| What is ...
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.
Software Testing Mock Interviews Playlist
czcams.com/video/tJ5Cv8TVXSw/video.html
Sir i have an interview in 2 days as they set it up pretty soon but i really need a help from you on it. Can we please connect.
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.
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.
Thanks very much RD. Kindly do more of these experienced interviews.
Great interview,thank you for sharing all details.It’s very helpful for those who need to get in to industry
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.
Hii
Yes this is perfect answer
@@priyapatil2771 hello
@@amolvijay309 hi
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
Rakesh sir doing a wonderful job for the QA aspirants hats off to u. Keep up the good work videos are very useful.
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.
Topic or subject can be different. But the way to communicate is wow. It's very helpful
You're doing great work. from interview questions to the Q&A you share in description..amazing. and God bless.
Thanks for watching.
I would have given a love for the jenkins explanation.. thank you
Hello sir you are doing great job i have cleared so much doubt about Jenkins ci cd git and tc thank you so much 👏
बहुत शानदार इंटरव्यु,
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😊
Thank you for watching!
@@rdautomationlearning609 sir please upload only automation testing interview questions for fresher
Depends on how many scenarios we are testing . If we find out exceptions i critical scenarios then we can modify to hard assert .. but usually there is lot of manual observation which is a bad practice... Atleast for smoke scenarios we can use hard assert and later we can use softassert
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
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.
Thanks ji completely understood
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.
usage of assert commands totally depends on the scenario which you are going t verify mostely the hardest will thorw exception imediatly bcz if the login scenario fails we cant excute other scenarios the soft assert will not throw exception it will wait some time
Soft assert is recommended because even 1 test case fails remaining tests might pass when we use soft assert
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.
Thanks for your explanations :)
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 🙏🙏🙏🙏
Most welcome 😊
@@rdautomationlearning609 Good morning sir,
I am preparing for interview.
Can you please share video Maven and Jenkin.
Thank you so much for doing this one it helps a lot 👏 💐
Glad it was helpful!
It's Based on Schenerios , Hard Assert for Mandatory fields and Soft Assert For Nonmandotary field
Can you also insert introduce yourself part. It will be useful for us
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..
Thanks for your explanation
Thanks for uploading this interview. It was a very good experience.
Thanks for giving mock interview on our channel!
It's good
Good job priya
hi priya your confidence is very high and talking is very fluentaly...
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.
Very good interview questions. Very informative
Glad it was helpful!
Hard assertion by default we can use it it throw exception if aasert failes.
If we want run teat cases even some them is failed we can suggest soft assertion
Softassert is mostly use because it will kip our failed test case and continues with execution.and we can get that asset by using asert all method
Thank you RD automation ❤
its a great session...thank you... just reminding you at 20minutes, its DSL(Domain-Specific Language)
Yes, you are right
Thank you for the interview
Soft assert is more powerful because once all test execution we can check results also
Thank you so much sir for explaining the CI concept with so ease. 😄
Just want to ask if this process is same for GITLAB too ?
Yes, definitely
@@rdautomationlearning609 thank you sir 🙂❤️
@@maheshkumarvishwakarma happy to help!!
If I have 100 test cases but I would like to execute 50 test cases how it would be executed on Jenkins?
Soft assert is preferred because it will not fail you entire code and will continue to the next case but you will still be able to see in your report which assertion failed and why
Bless you sir for the knowledge.
Thanks for watching.
SoftAssert are mostly usde because hard assert is any verificaton are fail then next validation will be stoped and soft asrt are use to overcome assert class drowback , in soft assert any varification fail then next validation will be continue
In my opinion a beginner or at least who have 1 year of experience in automation shouldn't be use any tool for finding the xpaths. It will make to totally rely on that tools, you can't solve xpath making problems in the interviews.
This is what I have seen in my career.
Groovy
interesting and understandable
Thanks for watching.
If i have multiple assertions i can use softAssert and put assertAll and if i have a single assertions i can use hard assertion.
Soft assert is more prefered to used bcoz
in soft asseertion,
suppose we have multiple assertion,
and in this our 1st assert got failed....so in that condtion remaining aseertion still executed.
in hard assertion,
if 1st assertion got failed then remaining also failded with that.
My pointofview is based on priority of the testcases we have to choose soft/hard asserts,
If we compare like popup masgs /welcome masgs we gowith softasserts and remaining test cases we choose hard asserts.
Can you explain more about ci and cd pipeline
SoftAssert is better, because even if the test cases fails, we can catch it in the reports and complete the tests in parallel
Absolutely True!
Actually assert all method is used to convert the soft assert to hard assert right?
Soft assert because it collect errors during test method and will continue with next steps...
nice sis
One question i want to ask is "Is it compulsory to learn Jenkins if i'm apply for the post automation testing?" Because from the ans it sounds like its a part of DevOps teams and not of testers..
It depends on the company interviewing you. It is not always compulsory but it is an added advantage
Soft asert because it has to run after test case will fail it will continue to run next if it was fail it is continue to run
Assert soft is good ,bz it will recorded the start to end failure.
Thanks for response!
Hello Sir can u please do a mock interview for test lead interview
Can i get to know that tool we are using to identify an X-Path?
Hard asert if it fail the test case it will stop the execution and go fir next test case
No of occurrences of a in java
Hii, i can't understand the answer of how do you run the automation suite? you are given the answer so lengthy and it is difficult to remember. So can u give the answer in short form so that it will be easy to understand and easy to remember?
soft assert
are used more
Hard assert
@RD Automation Learning , could you please help connecting with me. I have an interview in 2 days on Senior Automation engineering. Please sir. Just 30 mins will help.
Hello Sir, thanks for your video's. I'm unable to crack the interviews I have given multiple interviews so far. Is there any way that I can get the assistance from you to crack the interview.
Thank you.
Thank you for watching and support!
Soft assert is more preferable to use
Sir I am one year experience in manual and automation testing and I want to apply for mock interview please consider for the same
Please share your CV at rdautomationlearning@gmail.com
how to attend mock interviews?
Sir your contain is really best..
But i want to suggest something for your channel growth so your channel reach to manny people
1. improve thumbnail
2. Improve editing
3. Need introduction of video
4. Video production
Thank you ❤️
Bro I want to interview with u sir
Hai sir day after tomorrow i have an interview can i connect with you
Language is groovy scriting language sir
Thank you!!
softassert
soft assert
Soft assert
hello, sir can you take my mock interview for manual testing??
Please share your CV at rdautomationlearning@gmail.com
Please load the vdo for bdd cucumber interview questions/& answers
Language name is groovy
What is this mock interview? Like the candidate just acting or is she real candidate for interview but not for any company really
I have 100 test cases and jenkins is set to run the build at 8:00PM my shift ends at 5:00PM.
1.Use soft assert 20th test failed entire suit fails
2.Use hard assert 20th test fails no proble remaining 99 passes
case 1: build not ready and you dont know what happens to other test cases, and get scolds from manager🤣🤣
case 2: modify the failed case and build ready to release, time saved you, manager, & customer happy.
Voice is too low
Gherkin language
Thank you for watching!
Soft assert
softassert