Explore topic-wise InterviewSolutions in .

We have to CONSIDER various factors while SELECTING an AUTOMATION tool best suited to a PROJECT, such as:

• Required time to learn and implement the tool
• The APPLICATION scope which we desire to automate
• Cost and budget management calculation
• Support available for the tool
• Limitations of the tool

Yes, UI level testing is possible. But, we can do far from that. As early feedback is CRUCIAL for every testing project, we don’t NEED to wait until the UI layer GETS developed. We can test the APIs directly, so that we can share crucial feedback early in the project development, giving DEVELOPERS more time to fix the bugs more proficiently.

Few of the GOOD practices of automation testing will include:

• ADDING APPROPRIATE comments
• Following the language-specific coding conventions
• Identifying the reusable methods and MENTIONING them in a separate file
• Run the SCRIPTS regularly
• Properly maintain the test data in a separate file

These type of information which are USED very often and CHANGE as per the authorization and ENVIRONMENT should always be maintained in a separate FILE. In case the user hardcore it into the code SYSTEM, then the user has to change it in every file which has its reference.

In testing, 100% automation WOULD be tough to achieve because there would be several edge test cases and some of them are ALSO executed SELDOM. Automating these types of cases which are not executed that OFTEN will not add value to the automation suite.

Go through the our all automation testing interview questions that will help in your interview.

Software Development Life Cycle or COMMONLY known as SDLC refers to the all the activities PERFORMED during software development, such as the gathering of requirement, requirement ANALYSIS, CODING, DESIGNING, implementation, testing, deployment and maintenance.

A BUG that impacts the major functionality of an application and DUE to which the application can’t be delivered, can be defined as a CRITICAL bug. It’s different both in severity and characteristics compared to a blocker bug as it doesn’t block or affect the testing of other parts of the application.

Defect SEVERITY term is used to mention the severity of the defect impacting the FUNCTIONALITY. Based on the ORGANIZATION, the defect severity can be mentioned in different levels, ranging from minor to critical or show stopper.

Usually priority – severity defects are divided into four categories, Low priority-Low severity, Low priority-High severity, High priority-Low severity, and High priority-High severity.

To example, these defect level: a spelling mistake in a page non-frequently navigated page will be categorized as Low priority-Low severity, whereas application crash in some very corner case will be DEFINED as Low priority-High severity. For High priority-Low severity case example, BRAND name spelling mistake and logo colour change can be mentioned. And, login functionality issue can be categorized as High priority-High severity defect.

A test case can have numbers of ATTRIBUTES according to the case requires, but these are the CRUCIAL ones which we mostly have with any test case: TestCaseId, Test Summary, Description, PREREQUISITE, Test STEPS, Expected Results, Actual Results, Test Result, Automation Status, Date & Executed By.

There are TOTAL three types of locks in mainframe:

• Update: It is known as permissive lock. It helps the program to read and make changes
• Shared: With the help of this lock, locked space READS two or more programs. It doesn’t ALLOW the changes to take place
• Exclusive: It doesn’t let the locked space accessed.

Only one OBJECT is allowed by DBD in a specific TIME. For execution, when more than one object looks for PERMISSION, lock contention comes into ACTION.

If you TEST the code, it helps you identify the error or defect (if any).

• Difficult to IMPLEMENT EXHAUSTIVE testing
• Early testing
• Bringing all the errors or defects together
• Pesticide Paradox
• Testing is done on the BASIS of context
• Reduce or finish FALLACY error if there is any

It is the right set of SOFTWARE and Hardware that are GOING to be used to perform the test.

For web application in Windows Operating system, IIS is the web server, DOT Net is the Web page DESIGN, MS SQL server is Database and Chrome/Firefox/Internet Explorer is the BROWSER.

It is a document that DEFINES testing activity PERFORMANCE in a sequential manner. It is usually derived from SRS, Product Description and CASE Document. Here are certain things that it covers: Reference, Items to be TESTED, Introduction, Software Issues and Risks, Testing of FEATURES, Schedules, Responsibility and Approvals.

It holds all the CHANGES that foreign key make to the primary key. DELETE Cascade RULE has to be defined by the foreign key in order to serve the purpose.

• The application that needs to be automated
• Budget and Cost like overhead management
• Learning the TOOL and IMPLEMENTING it
• Available support for the tool
• What are the LIMITATION in the tool

LOGGER, Reusable, Modular, Integration, Reporting, Consistent and INDEPENDENT are some of the ATTRIBUTES of a good framework. If, on one side, it should be adaptable to change, then, on the other side, it should AUTOMATICALLY fit itself to the code.

Here are some of the fields in Bug Report:

• A UNIQUE Identification
• Description of the defect - Short description of the bug
• Reproduction steps - EXACT DATA TEST, time of identification of defect
• Application section/module
• Severity and Screenshot
• For follow-up QUESTION, Responsible Question and Answer

Quick TEST Professional (QTP) is a commercial automation tool known as HP UFT. It endorses DIFFERENT testing environment like PowerBuilder, Oracle, Java, Siebel, Visual Basic, Stingray, PeopleSoft, Mobile, ActiveX, Delphi, Flex and SAP. VBScript is the language that gets synchronized with Performance Testing Tool (HP LoadRunner) and Test Management Tool (HP ALM). One characteristic feature is that it’s framework is KEYWORD driven.

It is BASICALLY done with the HELP of JavaScript. Code Snippet written below for name FIELD in a form.

FUNCTION validate() {
  var X = document.forms["Form"]["name"].value;
  if (x == "") {
    alert("Name must be filled out");
    return false;
  }
}

These points should be considered:

• Assembly of sequential and UNIFORM naming
• For every 10 line code, 3 line COMMENT is required
• Right and proportionate indentation
• How to handle errors and MAKE recovery (in certain situations)
• Make possible use of framework

Here are some of the frameworks USED in Software AUTOMATION TESTING:

• Keyword driven automation
• Hybrid automation
• Modular automation
• Data-driven automation

Certain conditions make AUTOMATION TESTING USELESS for agile methods:

• When agile testing exhibits need of making changes in the requirement
• When comprehensive LEVEL of DOCUMENT submission is required

These STEPS are involved to carry out the AUTOMATION process:

• Select the testing tool
• State automation scope
• Plan, DESIGN and then develop
• Execute testing
• Maintenance; if any REQUIRED

Scroll down to KNOW more about manual testing interview questions and answers