Basics of Software

Testing

Question’s and Answer’s

Interview Questions and Answers

1. What is software testing ?

A1- Software testing is a systematic process to identify the bugs in software and ensure the
correctness and completeness of software application.

A2- Software testing is a well-organized process, which is to assure the clients (end user) about
the correctness and completeness of software application as per their requirement. The software
testing also ensures the quality of software application. There are multiple stages are involved in
software testing operations for which we can ensure to the client about the quality of the Software
application.

2. What is the necessity of software testing ?

A- Software testing is necessary because it can assure to clients about the application quality
along with this there are multiple factors are involved such as the important reasons as to why
software testing must be considered necessity (mandatory):
1. To gain customer confidence
2. To check software adaptability
3. To identify errors
4. To avoid extra costs
5. To accelerate software development
6. To avoid risks
7. To optimize business

3. What is objective software testing?

A- Here are following some objective of Software testing

 Finding defects which may get created by the programmer while developing the software.
 Gaining confidence in and providing information about the level of quality.
 To prevent defects.
 To make sure that the end result meets the business and user requirements.
 To ensure that it satisfies the BRS that is Business Requirement Specification and SRS that
is System Requirement Specifications.
 To gain the confidence of the customers by providing them a quality product.

4. Psychology of testing

In software testing, psychology plays an extremely important role. It is one of those factors that
stays behind the scene, but has a great impact of the end result.
It is mainly dependent on the mind-set of the developers and testers, as well as the quality of
communication between them. Moreover, the psychology of testing improves mutual
understanding among team members and helps them work towards a common goal.
The three sections of psychology of testing are:
 Mindset of Developers and Testers.
 Communication in a Constructive Manner.
 Test Independence.

5. What is Quality Control (QC)?

Quality Control is known as QC and focuses on identifying a defect. QC ensures that the
approaches, techniques, methods and processes are designed in the project are following correctly.
QC activities monitor and verify that the project deliverables meet the defined quality standards.
Quality Control is a reactive process and is detection in nature. It recognizes the defects. Quality
Control has to complete after Quality Assurance.

6. What is Quality Assurance (QA)?

Quality Assurance is known as QA and focuses on preventing defect. Quality Assurance ensures
that the approaches, techniques, methods and processes are designed for the projects are
implemented correctly.
Quality assurance activities monitor and verify that the processes used to manage and create the
deliverables have been followed and are operative.
Quality Assurance is a proactive process and is Prevention in nature. It recognizes flaws in the
process. Quality Assurance has to complete before Quality Control.

7. What is QAMS?

A quality management system is a collection of business processes focused on consistently

meeting customer requirements and enhancing their satisfaction. It is aligned with an
organization's purpose and strategic direction.

A quality management system (QMS) is a system that documents the policies, business processes,
and procedures necessary for an organization to create and deliver its products or services to its
customers, and therefore increase customer satisfaction through high product quality.

8. What is Verification in Software Testing?

Verification in Software Testing is a process of checking documents, design, code docuemnts, and
program in order to check if the software has been built according to the requirements or not.
The main goal of verification process is to ensure quality of software application, design,
architecture etc. The verification process involves activities like reviews, walk-throughs and
inspection.
 Verification does not involve code execution while Validation involves code execution.
 Verification uses methods like reviews, walkthroughs, inspections and desk-checking
whereas Validation uses methods like black box testing, white box testing and non-
functional testing.
9. What is Validation in Software Testing?

Validation in Software Engineering is a dynamic mechanism of testing and validating if the

software product actually meets the exact needs of the customer or not. The process helps to
ensure that the software fulfils the desired use in an appropriate environment. The validation
process involves activities like unit testing, integration testing, system testing and user acceptance
testing.

10. Capability Maturity Model (CMM-Levels)

It has long been accepted that continuous process improvement is based on many small
evolutionary steps rather than larger revolutionary innovations. The Capability Maturity Model
(CMM) provides a framework for organising these evolutionary steps into five maturity levels that
lay successive foundations for continuous process improvement.
This methodology is at the heart of most management systems which are designed to improve the
quality of the development and delivery of all products and services.

The five Software Capability Maturity levels have been defined as:
1. Initial
The software process is characterised as ad hoc, and occasionally even chaotic. Few processes are
defined, and success depends on individual effort and heroics.
2. Repeatable
Basic project management processes are established to track cost, schedule, and functionality. The
necessary process discipline is in place to repeat earlier successes on projects with similar
applications.
3. Defined
The software process for both management and engineering activities is documented,
standardised, and integrated into all processes for the organisation. All projects use an approved
version of the organisation’s standard software process for developing and maintaining software.
4. Managed
Detailed measures of the software process and product quality are collected. Both the software
process and products are quantitatively understood and controlled.
5. Optimising
Continuous process improvement is enabled by quantitative feedback from the process and from
piloting innovative ideas and technologies.

11. What is error?

A- Error is small mistake which is happed by developer in Software Code.

12. What is Defect or bugs or faults or issues ?

A- Defect is difference between expected and actual result.

13. What is Failure?

A1- A failure is the inability of a software system or component to perform its required functions
within specified performance requirements. When a defect reaches the end customer it is called a
Failure. During development, Failures are usually observed by testers.

A2- The major functionality of software or entire application is unable to perform their functions
on production environment, that known as failure.

14. Which are the Seven Testing Principles?

A- There are seven principle for software testing

1. Testing shows the presence of defects, not their absence

2. Exhaustive testing is impossible
3. Early testing saves time and money
4. Defects cluster together
5. Beware of the pesticide paradox
6. Testing is context dependent
7. Absence-of-errors is a fallacy

1. Testing shows the presence of defects, not their absence

Testing can show that defects are present, but cannot prove that there are no defects. Testing
reduces the probability of undiscovered defects remaining in the software but, even if no defects
are found, testing is not a proof of correctness.

2. Exhaustive testing is impossible

Testing everything (all combinations of inputs and preconditions) is not feasible except for trivial
cases. Rather than attempting to test exhaustively, risk analysis, test techniques, and priorities
should be used to focus test efforts.

3. Early testing saves time and money

To find defects early, both static and dynamic test activities should be started as early as possible
in the software development lifecycle. Early testing is sometimes referred to as shift left. Testing
early in the software development lifecycle helps reduce or eliminate costly changes.

4. Defects cluster together

A small number of modules usually contains most of the defects discovered during pre-release
testing, or is responsible for most of the operational failures. Predicted defect clusters, and the
actual observed defect clusters in test or operation, are an important input into a risk analysis
used to focus the test effort (as mentioned in principle 2).
5. Beware of the pesticide paradox

If the same tests are repeated over and over again, eventually these tests no longer find any new
defects. To detect new defects, existing tests and test data may need changing, and new tests may
need to be written. (Tests are no longer effective at finding defects, just as pesticides are no longer
effective at killing insects after a while.) In some cases, such as automated regression testing, the
pesticide paradox has beneficial outcome, which is the relatively low number of regression
defects.

6. Testing is context dependent

Testing is done differently in different contexts. For example, safety-critical industrial control
software is tested differently from an e-commerce mobile app. As another example, testing in an
Agile project is done differently than testing in a sequential software development lifecycle project
(see section 2.1).

7. Absence-of-errors is a fallacy

Some organizations expect that testers can run all possible tests and find all possible defects, but
principles 2 and 1, respectively, tell us that this is impossible. Further, it is a fallacy (i.e., a
mistaken belief) to expect that just finding and fixing a large number of defects will ensure the
success of a system.
For example, thoroughly testing all specified requirements and fixing all defects found could still
produce a system that is difficult to use, that does not fulfill the users’ needs and expectations, or
that is inferior compared to other competing systems.