Scribd
Upload
51 views

Interview Questions

The document discusses various topics related to software testing interview questions, including: 1. The basis on which acceptance plans are prepared, including requirement documents, customer input, and project plans. 2. Coverage techniques in software testing including statement, decision, and path coverage. 3. The use of TestNG and JUnit for managing test cases and generating reports in Selenium. 4. Reasons why Selenium is a preferred tool for automation testing, including its open source nature and ability to work across browsers, languages, and integrate with tools. 5. That black box test cases are typically written before white box cases since black box cases only require initial project documents while white box requires more architecture clarity

Uploaded by

prasad ghate
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
51 views

Interview Questions

The document discusses various topics related to software testing interview questions, including: 1. The basis on which acceptance plans are prepared, including requirement documents, customer input, and project plans. 2. Coverage techniques in software testing including statement, decision, and path coverage. 3. The use of TestNG and JUnit for managing test cases and generating reports in Selenium. 4. Reasons why Selenium is a preferred tool for automation testing, including its open source nature and ability to work across browsers, languages, and integrate with tools. 5. That black box test cases are typically written before white box cases since black box cases only require initial project documents while white box requires more architecture clarity

Uploaded by

prasad ghate
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Reference Links:-

https://www.edureka.co/blog/interview-questions/software-testing-interview-
questions/#queone

https://www.guru99.com/software-testing-interview-questions.html

https://www.softwaretestingmaterial.com/100-software-testing-interview-questions/

1.On what basis the acceptance plan is prepared?

Basically, the acceptance document is prepared using the following inputs.

Requirement document: It specifies what exactly is needed in the project from the
customers perspective.
Input from the customer: This can be discussions, informal talks, emails, etc.
Project plan: The project plan prepared by the project manager also serves as good
input to finalize your acceptance test.

2. What is coverage and what are the different types of coverage techniques?
The parameter used in software testing to describe the extent to which the source
code is tested is known as coverage.
There are three basic types of coverage techniques and they are:

Statement coverage: It ensures that each line of source code has been executed and
tested.
Decision coverage: It assures that every decision (true/false) in the source code
has been executed and tested.
Path coverage: Here we ensure that every possible route through a given part of the
code is executed and tested.

3.What is use of testNG & Junit in selenium

-- TestNG & JUnit for managing test cases and generating reports

Some of the noteworthy features of TestNG are:


Powerful and wide variety of annotations to support your test cases.
Helps to perform parallel testing, dependent method testing.
The flexibility of running your tests through multiple sets of data through
TestNG.xml file or via data-provider concept.
Test cases can be grouped and prioritized as per need basis.
Provides access to HTML reports and can be customized through various plugins.
Test logs can be generated across tests.
Can be easily integrated with eclipse, Maven, Jenkins etc.

4.Why Selenium is a preferred tool for Automation testing?


Selenium is an open source tool which is used for automating the tests carried out
on web browsers. Since Selenium is open-source, there is no licensing cost
involved,
which is a major advantage over other testing tools. Other reasons behind
Selenium’s ever-growing popularity are:

Test scripts can be written in any of these programming languages: Java, Python,
C#, PHP, Ruby, Perl &.Net
Tests can be carried out in any of these OS: Windows, Mac or Linux
Tests can be carried out using any browser: Mozilla Firefox, Internet Explorer,
Google Chrome, Safari or Opera
**It can be integrated with tools such as TestNG & JUnit for managing test cases
and generating reports
It can be integrated with Maven, Jenkins & Docker to achieve Continuous Testing

5.Which test cases are written first: white boxes or black boxes?
Usually, black box test cases are written first and white box test cases later. To
write black box test cases we need the requirement document and,
design or project plan. These documents are easily available at the initial start
of the project. White box test cases cannot be started in the initial phase
of the project because they need more architecture clarity which is not available
at the start of the project. So normally white box test cases are written
after black box test cases are written

6.What is meant by Defect Cascading?


Defect cascading is a defect which is caused by another defect. One defect triggers
the other defect. When a defect is present in any stage but is not identified,
hide to other phases without getting noticed. This will result in an increase in
the number of defects.

Let us understand this by an example.

You are designing the Login Module of a WebPage:

In phase 1 – You are designing Register User Module for Login and mobile number is
mandatory but you can leave it blank due to a bug that gets unnoticed.

In Phase 2 – You will design the login form having username and password. The
password is OTP which will be sent to User’s registered mobile number.

Now as Register module has a bug that mobile number can be left blank so this may
lead to Login failure or maybe some system error or crash
if a null mobile number is not handled. This is known as defect cascading.

7.Can we do performance testing manually

Yes you can do Performance testing manually. For this you should open many active
sessions of the application and should test it out.
It also depends on what type of performance test you want to do. However, in
general you can judge the active sessions, number of DB connections open,
number of threads running (I have taken JAVA based Web applications as eg), the
amount of the CPU time and memory being used by having a performance viewer.
You can have IBM Tivoli Performance viewer. It is available for trial version also.
Usually the the test is done by deploying the application on the server
and accessing the application from multiple client machines and making multiple
threads to run. The performance viewer should of course be installed on the server.

You might also like