Last updated 19/06/2020
Where can a business reach without implementing automation in their process?
Well, that’s easy to answer, NOWHERE!
Yeah. That’s right. With a hell lot of mundane tasks blocking their way, how can a business expect to grow?
That’s why businesses nowadays are focusing on automating everything. Yes, including testing.
But how does test automation exactly work?
Well, test automation is a very crucial part of software testing. In software testing, test automation is the use of software separate from the software being tested to control the execution of tests and the comparison of actual outcomes with predicted outcomes. Test automation can automate some repetitive but necessary tasks in a formalized testing process already in place, or perform additional testing that would be difficult to do manually. If we are to write about the contribution of Test Automation of continuous delivery, it might take up pages. Yes, Test automation is critical for continuous delivery and continuous testing.
So you can understand if you are not even remotely aware of test automation and its contribution, you don’t stand a chance in your DevOps Interview. So let us give you an idea about what kind of questions you might face about test automation in your next DevOps interview through these 20 interview questions that we fetched for you!
Answer: Any action that is able to reduce human efforts is called automation
Answer: Automation Testing is the process of using exclusive software tools or scripts to perform testing tasks such as data entering, execution of the test steps, collation of the results, etc.
Answer: Here is a list of things that you can automate:
Answer: Automation testing is useful in the following scenarios:
a) Regression testing: When you are in a dire need of a bug fix or new module implementation, you have to ensure that functionalities implemented remain unchanged and do not get affected at any cost. For this matter, you can end up running the regression test case multiple times.
b) Non-functional Testing: Testing the non-functional aspects of an application.
c) Complex calculation: checks or test scenarios that are prone to human errors.
d) Repeated execution of the same tests: When you are about to run the same set of test cases for a different set of data or after each build release or on multiple hardware, software, or combination of both.
Automating the test cases in the above scenarios assists you in achieving the speed of testing with minimized human errors.
Answer: Identifying the appropriate test cases for automation is the most important step towards automation.
Answer: 100% automation would be difficult to achieve because there would be many edge test cases and some cases that are executed seldom. Automating these cases which are not executed that often will not add value to the automated suite.
Answer: In order to identify the tool for Automation testing in your project:
a) Understand your project requirements thoroughly and identify the testing scenarios that you want to automate.
b) Search for the list of tools that support your project's requirements.
c) Identify your budget for the automation tool. Select the tools within your budget.
d) Identify if you already have skilled resources for the tools. If you don't have the necessary skilled resources then identify the cost for training the existing resources or hiring new resources.
e) Now compare each tool for key criteria like:
f) Once you have compared the tools, select the tool which is within your budget and support your project requirements, and gives you more advantages based on the key criteria mentioned above.
Answer: Concluding which tool is best suitable for the project requires a lot of brainstorming and discussions.
Answer: Once we finalize the tool, our next step would be to design the framework.
Answer: A framework is a set of the structure of the entire automation suite. It is also a guideline, which if followed can result in a structure that is easy to maintain and enhance.
These guidelines include:
Answer: The characteristics include:
Answer: Frameworks are guidelines and not mandatory rules, so we can do without a framework, but if we create it and follow it, enhancing and maintaining would be easy to implement.
Answer: Open source tool like Selenium, JMeter, etc.
Paid tools like QTP, Load Runner, Ranorex, RFT, and Rational Robot.
Answer: Normally the structure should have – (It would differ from project to project)
Answer: This information should always be maintained in a separate file.
Answer: URL, Login, and passwords are the kind of fields that are used very often and these change as per the environment and authorization. In case we hardcode it into our code, we have to change it in every file which has its reference.
In case if there are more than 100 files, then it becomes very difficult to change all the 100 files and this, in turn, can lead to errors. So this kind of information is maintained in a separate file so that updating becomes easy.
Answer: Different types of frameworks includes:
Answer: Some of the good coding practices include:
Answer: Tests that should not be automated are:
Answer: Today as we are moving to the Agile mode, testing is not limited to the UI layer. Early feedback is imperial for an agile project. If we concentrate only on the UI layer, we are actually waiting until the UI is developed and available to test.
Rather we can test even before the UI is actually developed. We can directly test the APIs or the methods using tools like Cucumber and FitNesse.
In this way, we are giving the feedback much early and are testing even before the UI is developed. Following this approach will help us to test only the GUI aspect of small cosmetic changes or some validations on the UI and will help the developers by giving more time to fix the bugs.
Hopefully, this sneak peek was enough for you to understand what kind of questions you’ll be facing during your DevOps interview. Want to know more about test automation and its role in continuous delivery? Join our DevOps Courses to learn about it in detail!
NovelVista Learning Solutions is a professionally managed training organization with specialization in certification courses. The core management team consists of highly qualified professionals with vast industry experience. NovelVista is an Accredited Training Organization (ATO) to conduct all levels of ITIL Courses. We also conduct training on DevOps, AWS Solution Architect associate, Prince2, MSP, CSM, Cloud Computing, Apache Hadoop, Six Sigma, ISO 20000/27000 & Agile Methodologies.
|AWS Solution Architect Associates|
|PRINCE2 Foundation & Practitioner|
|DevOps Foundation By DOI|
|ITIL4 Managing Professional Bridge Course|
|Certified DevOps Developer|
|DevOps Practitioner + Agile Scrum Master|
|Certified Digital Transformation Officer|
|Certified DevOps Engineer|
|ISO Lead Auditor Certification|
|Microsoft Azure Administrator AZ-104|
|Certified Full Stack Data Scientist|