Testing Interview Questions and Answers
Testing is actually defined to identify and improve the coding to improve its efficiency and make it bug-free.
Before we pen down all the details on web testing, let's quickly define what is web testing? In simple words checking your web application for possible bugs before it's made live or you can say that checking web application before the code is moved into the production department is called web testing.
Most Frequently Asked Testing Interview Questions
| S.no | Manual Testing | Automated Testing |
|---|---|---|
| 1. | It is easy for the beginners who have just entered into the quality assurance industry to kick start career. | It can be used in different versions of the software, so it in the end reduces the cost to test different types of similar softwares. |
| 2. | WordPress websites, their inner links and all the plugins of the system are defined and it’s easy to verify the plugins and links in the system. | It’s in the hand of testers to define the test suites and write the suitable test scripts for the program to check, so they can easily build the test suites that can check all the features of the system easily. |
| 3. | As different features are there, and also it is developed by different teams. So, parallel development is possible. | It can be used in different versions of the software, so it in the end reduces the cost to test different types of similar softwares. |
| 4. | Plugins mostly have only one type of functionality to perform, so the developer’s mind is also focused on a single thing and can dedicate time towards one thing | Testers have the added advantage to program very hard tasks which can easily unveil any hidden information in the software that is being developed. |
Scroll down to know more about manual testing interview questions and answers
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
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
Here are some of the frameworks used in Software Automation Testing:
- Keyword driven automation
- Hybrid automation
- Modular automation
- Data-driven automation
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
| Retesting | Data Driven Testing |
|---|---|
| It is a procedure of checking bugs | In information that drives the testing process, the application is tried with different test information. |
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;
}
}
Selenium is a free (open source) Test Suite structure. It is utilized to computerized Web and Mobile conditions.
- WebDriver
- Distributed Testing (Grid)
- Browser Addon (Playback Tool and Record)
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.
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
| Static Testing | Dynamic Testing |
|---|---|
| It means document evaluation to identify if there is any error or not. It is usually conducted at SDLC beginning stage. | Dynamic Testing is used to execute the code. Expected outcome and output is validated simultaneously. |
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.
- 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
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.
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 is the right set of Software and Hardware that are going to be used to perform the test.
Example:
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.
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
| HDAM | HIDAM |
|---|---|
| It doesn’t have separate index file. Instead, every key file passes through randomizer that defines the record in the database. | It is a separate index file with base as root segment. It has an information file that marks data position. |
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.
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.
| Continue | Next Sentence |
|---|---|
| In this, the flow of control is continued to the next statement after the scope terminator | It means delivering the statement to the next period. |
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.
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 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.
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.
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.
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.
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
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.
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
There are different types of web testing:
- Functionality Testing
- Usability Testing
- Interface Testing
- Database Testing
- Compatibility Testing
- Performance Testing
- Security Testing
- Crowd Testing
To know more about testing interview questions, we are defining some of the Manual Testing Interview Questions and Automation Interview Questions.
During testing, we dig all the possible issues like the functioning of the site, ability to handle traffic, web application security, its access to regular users or handicapped, and much more.
When we talk about Software testing, it is a process of evaluating the functionality of a software application with one aim to find whether the software met that particular requirement or not and to spot the defects to ensure that the software is defect-free in order to make the quality product.
There are two types of software testing one is manual testing and another one is automation testing. You can do testing in a static way or dynamic way. Even there are different levels of testing like unit testing, integration testing, system testing, and the last one is acceptance testing.
You will find the complete information in Manual Testing Interview Question and Automation Testing Interview Question and Answers we are mentioning below.