Software Testing

Q.1 : Testing :
It refer to process of evaluating a system or
application to identify and fix any issues or errors
before it is deployed or released to user .
The goal of testing is to ensure the quality and
reliability and functionality of SW.
It ultimately provides a better user experience.

Q.2 : SW Testing :
It is the process of identifying the correctness and
quality of SW program.
It is crucial phase in the SW development life cycle.

Q.3 : Advantages of SW Testing :

 It finds the error and remove those error, which
prevents the SW from the O/P.
 It ensures that the SW is being developed
according to user requirement.
 It improves the quality of SW.
 It finds the error free SW.
  A well tested SW product leads to higher
customer satisfaction.
 It helps in optimizing the SW performance.

Q.4 : SW Metrics :
SW metrics are quantifiable measure that provide
insights into the SW development process.
It is defined as a quantitative measure that helps to
evaluate the project and quality of SW.

Q.5 : Difference between Error, Fault and Failure :

Error Fault Failure
An error is an A fault is state If the SW has
mistake made in that cause the lot of defects, it
code. SW to fail to leads to failure
accomplish its or causes
essential failure,
function,
The developers Human mistake The failure find
and automation cause fault. by manual test
test engineers engineer
raise the error. through the
development
cycle.
It is Fault may occur -
inconsistency by an improper
between actual stem in initial
and expected stage, process
outcome. or data
definition
There are two Types of faults : -
types of error. 1. Business Logic
1. Syntactic fault.
Error 2. Faulty GUI
2. Logical Error.

Q..6 : Principles of Testing :

1. Testing shows the presence of defects :
a. Primary purpose of testing is to identify
defect or issue in the SW.
2. Complete Testing is impossible.
a. It is impossible to test a every possible I/P
and scenarios within a SW applications.
3. Early testing.
a. Testing activities start as early as possible in
SW development life cycle which helps in
identifying and fixing issues as earlier stage.
4. Defect Clustering.
a. Small no of modular contains most of defects.
By focusing testing affords on these high risk
 areas , testers can find a significant no of
defects.

Q.7 : STLC :
STLC stands for Software Testing Life Cycle.
It is systematic approach to testing a SW to ensure
that meets the requirement and free of defects.
It is used to ensure that the SW is of high quality,
reliable and meets needs of end users.
The main goal of STLC is to identify defects and
issues in SW applications as early as possible in
development.
Following are stages of STLC :
1. Requirement Analysis :
a. It is first step of STLC.
b. In this phase, quality assurance term
understands the requirement like what is to
be tested.
2. Test Planning :
a. It is the most efficient phase of STLC where
all testing plans are defined.
 b. In this phase, manager of testing term
calculate the estimated efforts and cost for
testing work.
3. Test case Development :
a. This phase is started once the test planning
phase is completed.
b. In this phase, testing team notes down the
detailed test cases.
4. Test Environment Setup :
a. It is viral part of STLC.
b. Basically, the test environment decides the
conditions on which SW is tested.
5. Test Execution :
a. After the test case development and test
environment setup, test execution phase
starts.
b. In this phase, testing teams starts executing
test cases based on prepared test cases.
6. Test Closure :
a. It is final stage of STLC where all testing
related activities are completed and
documented.
Q.8 : Testing and Debugging :
Testing Debugging
Testing is process to find Debugging is process of
bugs and errors. correcting bugs found
during testing.
It’s primary goal of It’s primary goal is to fix
testing is to verify the defects, errors in SW
SW functions works as code.
expected and meets
specified requirements.
Testing is display of Debugging is deductive
errors. process.
Testing is done by Debugging is done by
Testers. developers.
Testing can be manual or Debugging is always
automated. manual.
Testing focuses on Debugging focuses on
validating the SW against identifying and rectifying
the requirement, ensure errors within code.
it’s behavior correctly
under different
conations.

Q.9 : Verification and its workbench :

Verification is process of checking that SW
development derives its goal without any bugs.
It is the process to ensure whether the product that
is developed is right or not.
 Workbench of Verification.
For diagram refer your book :
A verification workbench is a way of document how a
specific activity has to be perform.
1. Input : It is some entry definition.
2. Verification Process : It must describe step by
step activities to be conducted in workbench.
3. Check Process : It must describe how verification
has been checked.
4. Standards and tools : It may used for testing
standards for verification.
5. Output : It is exit criteria for workbench.

Q.10 : Verification and Validation :

 Verification Validation
It means are ‘ we building It means are ‘ we building
product right ’. right product ’.
It is done before It is done after
validation. verification.
It is static technique. It is dynamic technique.
It is human base checking It uses various testing
of documents and files. methods.
It doesn’t involve It involves execution
executing code. code.

Q.11 : Goals of SW Testing :

1. Immediate Goals :
a. It is also called as short term goals.
b. It includes.
 i. Bug Discovery : No of the bugs are
discovered in early stages of SW testing.
ii. Bug Prevention : It is consequent action
of bug discovery.
2. Long Term Goals :
a. It includes,
i. Quality : This goals enhance quality of
SW.
ii. Customer Satisfaction : It verifies SW
developed as per customer’s satisfaction.
iii. Reliability :It matters of confidence that
the SW will not fail.
iv. Risk Management : It is done do
decrease the failure.
3. Post- Implemented Goals :
a. This goal are important after a SW is
released.
b. It includes,
i. Reduced maintenance Cost : Post
released errors are costly to fixed.
ii. Improved SW testing process : This goal
improves testing process for future use
or SW projects.
Q.12 : Product Metric :
It is metric used to measure the characteristics of
product such as size, complexity, reliability and quality
level.

Q.13 : Process Metric :

It is a metric used to measure characteristics,
methods, technical tools and maintaining the SW
product or system.

Q.14 : ECP :
ECP is Equivalence Class Partitioning.
Its is a BBT ( Black Box Testing ) technique.
Its goal is to reduce the set if possible test cases into
smaller manageable set.

Q.15 : Difference between WBT and BBT :

WBT BBT
WBT stands for White BBT stands for Black Box
Box Testing. Testing.
In this technique, tester In this technique,
has knowledge about internal structure
internal structure. knowledge in unknown.
Code implementation is Code implementation is
necessary. not needed.
It is done by SW It is done by SW tester.
developer.
This testing is started This testing can be
after detail design initiated based on their
document. requirement specification
document.
Programming knowledge is Programming knowledge is
mandatory. not required.
It is also called as closed It is also called as clear
box testing. box testing.
It is less time consuming. It is time consuming.

Q.16 : Black Box Testing and Types :

BBT focuses on functional requirements of the SW.
It is done without internal knowledge of SW.
It verifies that the SW functions according to its
specification.
Test cases are designed based on typical user
scenarios and usage pattern.
BBT ensure that new changes or update negatively
impact by system functionality.
Types of BBT :
1. Functional Testing :
a. This technique focuses on verifying that SW
functions as expected its requirements.
2. Non – functional Testing :
a. This Technique evaluate aspects such as
performance, usability & reliability without
looking at internal code.
Advantages :
No need of Programming knowledge.
Disadvantages :
Cannot identify internal defects.

Q.17 : White Box Testing and its types :

WBT is a testing technology that examines the
program logic or code.
It is done on basis of internal structure of SW.
It is performed to test the programs internal
structure.
It’s primary goal is to validate the correctness of the
code ensuring that the cpde statement and conditions
behave as expected.
The test cases are designed based on internal logic of
code.

Types of WBT :
1. Basis path testing :
a. The basis path technique examines all
possible path of the execution at least for
once.
2. Control structures testing :
a. This technique is used to enhance coverage
area by testing various control structures.
Advantages :
 It ensures comprehensive test coverage.
It allows only detection of defects.
Disadvantages :
Detailed programming knowledge is required.

Q.18 : Test Case :

Test case is defined as test condition such as “ to
verify the particular program path or to verify the
functionality with a specific requirement “.

Q.19 : Test case design :

The test case is set of input, execution, conditions and
expected result developed for particular object.
Test case are derived from test scenarios.
Following is the test case design :
Refer your book :
1. Test ID : Unique ID for each test case.
2. Test Priority ( Low/Medium/High ) : This is useful
while test execution. Test priority for business
rules and functionality test cases can be medium
or high where as minor user interface cases can
be low.
 3. Module name : It is name of main module.
4. Test Designed by : Name of tester.
5. Test Designed Date : Test when written.
6. Test Executed by : Name of tester who is
executed testing.
7. Test Executed Date : Test Executed date.
8. Test Title : Test case title.
9. Test Summary : Describes test objective.
10. Pre-conditions : List all the pre-conditions in
order to execute this case.
11. Test Steps : List all test steps in detail.
12. Test Data : Data used for Input.
13. Expected Result : Mention expected Output.
14. Actual Result : Mention actual Output shown
after test execution.
15. Status ( Pass / Fail ) : Mention Testing is pass
or fail.

Q.20 : Test Strategy :

It is high level document that defines the overall
approach, goals, resources and schedule for SW
testing.

Q.21 : Characteristics of Testability :

Testability refers to the ease with which a SW
application or system can be tested.
Characteristics of Testability :
1. Operability ( The better it works, the more
efficiently it can be tested ) : If a system is
designed and implemented with quality of mind ,
relatively few bugs will block the execution of
testes.
2. Controllability ( The better we can control the
SW, the more testing can be automated ) : SW
and HW starts can be controlled directly by the
test engineer.
3. Observability ( What you see is what you test ) :
Incorrect OP is easily identified. IP provided as
part of testing and it produce same OP.
4. Simplicity ( The less there is to test, the more
quickly we can test it ) : The program should
exhibit functional simplicity, structural simplicity
and code simplicity.
5. Understandability ( The more information we
have, the smarted we will test ) : The
architectural design and development is easily
understandable.
 6. Stability ( The fewer the changes the fewer
causes to testing ) : The SW recovers well from
failure.
7. Decomposability ( By controlling the scope of
testing we can more perform smartly testing ) :
The SW are completed build from module then
can be test independently.

Q.22 : Test characteristics :

1. A good test should be neither too simple nor too
complex : Although it is possible to combine a
series of test into a one test case but it can lead
to mark errors. In general, each and every test
should be executed separately.
2. A good test has a high probability of finding a
error : The tester must understand the SW and
attempt to develop a mental picture of how a SW
might fail.
3. A good test be “ best of breed ” :
4. A good test is not redundant.

Q.23 : Working of web applications :

Web applications is application SW that runs on web
server.
Web application are developed using HTML, CSS.
JavaScript , etc & utilized using browser like chrome,
windows explorer, etc.
Working :

In general, a user sends a request to web server using

web browser such as Google chrome, Microsoft Edge,
etc over the internet.
Then the request of client is forwarded to web
applications server by the web server.
After that, web applications server perform the
requested operations like processing database
produces the request of requested data.
Then the result is displayed on web browser.

Q.24 : Techniques of Web application Testing :

 Web application Testing is an crucial to ensure the
reliability, security & performance of application.
 Following are techniques of web application.
1. Functionality Testing :
a. This technique can be considered as a way
of ensuring that all functionality of SW are
working as required.
b. It ensures that the functionalities of web
application are properly functioning or not.
c. This technique is performed to test the
functionalities of each feature on website.
d. Types of functionality :
i. System Testing
ii. Unit Testing
iii. Integration Testing

2. Interface Testing :
a. It is used to validate whether system pass
data ad control information properly over a
computer network.
b. It focuses on application server, web
server & database server,
c. It ensures the graphical elements of the
application are displayed correctly and
interactive.
 d. It ensured data integrity & consistency.

3. Compatibility Testing :
a. This technique is very important for all web
aspect.
b. It includes browser compatibility, OS
compatibility & mobile browsing
compatibility.

Q.25 : Dimensions of Quality :

The quality SW product is product that meets the
expectation of customers or end users.
Following are dimensions of Quality :
1. Structure
2. Content
3. Interoperability
4. Function
5. Usability
6. Compatibility
7. Security
8. Navigability
9. Performance
Q.26 : Test planning :
It is a crucial phase in SW testing process that
includes defining the overall approach and strategy
for testing a SW applications.

Q.27 : Testing process :

Testing plays a crucial role in the overall web
development.
It is very important in web development.
Follow diagram for this question

Q.28 : Strategy of web application :

The strategy for web application testing adopts the
basic principles for all SW testing & applies a strategy
that have been recommended for object oriented
system.

Q.29 : SW testing strategy :

Testing is process as sequence of steps performed for
a given purpose.
It is a set of activities that can be plan in advance &
conducted systematically.
Testing process is conducted by moving inwards in
spiral.
Development process is conducted by moving outwards
in spiral.
SW testing strategies is developed by SW developers
& test specialists.
Unit testing exercise a specifics control path &
concentrate on each unit of the SW as implemented in
source code.
Moving outward the spiral to integration testing,
where the focus is on design & SW architecture.
Validation testing assures that validation criteria of
SW fulfills all functional behavior.
Finally we arrive at system testing, it verifies that all
system elements functions properly.
Q.30 : Unit Testing :
It is a type of testing in which the smallest testable
units of SW are tested.
It is also called as module testing.
The purpose of unit testing is to validate that each
module of SW works properly.
In unit testing, each unit is tested separately before
integrating them into modules to test the separate
units.
Unit testing is very important type of SW testing that
tests individual SW components.
This testing is done to validate the code developed by
developers.
Advantages :
 Unit testing may reduce uncertainty in units.
 Unit testing finds error are early stages.
Disadvantages :
 Unit testing requires initial time.
 Unit testing will not catch every error in program.

Q.31 : Integration Testing :

It is SW testing methodology, during which the units
of SW is integrated.
Integration testing is a level of SW testing where
individual units are combined and tested in a group.
This level of testing is to expose faults in interaction
between integrated units.
The goal of integration tasting is to take tested units
and build program structure that has been design.
Integration testing use a big bang integration
strategy.

Q.32 : System testing :

Diagram :
System testing is process of attempting a SW
program doesn’t meets its original requirements of
goal.
It is a level of testing where integrated & complete
SW is validate to verify the system functionality.
In system testing, the system is tested against
functional and non – functional requirements such as
accuracy, reliability and speed is defined by customer.
The goal of system testing is to find and detect
original outcome of SW system.
Types of System Testing :
1. Regration Testing :
2. Usability Testing :

Q.33 : Usability Testing :

Usability testing refers to evaluating a product or
service by testing it with representative users.
It is a SW testing technique used in user centred
interaction design to evaluate a SW product by testing
on users.
The goal of Usability testing is to identify the
usability problem to collect qualitative & quantitative
data.
Usability testing is used to measure easy & user
friendly SW application.
Process of usability testing :
Q.34 : Accessibility Testing :
It is subset of usability testing.
Aim of accessibility testing is to determine whether
the SW or application is accurate for disable people.

Q.35 : ALPHA Testing :

Alpha testing comes after system testing & involves
both WBT and BBT techniques.
Features of Alpha Testing :
 Outside users are not involved while testing.
 WBT & BBT are used.
 Developers are involved.
Alpha testing is performed by developers.
Advantages :
 1. Alpha testing provides better view about the
reliability of the SW at early stages.
2. Alpha testing helps simulate real time user
behavior & environment.
Disadvantages :
1. In alpha testing, depth functionality cannot be
tested.
2. In alpha testing, sometimes developer & testers
are dissatisfied with there results.

Q.36 : BETA Testing :

Beta Testing is final round of testing before releasing
a product.
It is done at end of SW development cycle.
It is good way to find compatibility and configuration
bugs.
Beta testing is conducted in an environment in which
id not controlled by developer.
It is performed to know whether the developed SW
satisfies user requirements.
Advantages :
 It reduces product failure.
  It improves product quality.
Disadvantages :
 Test Management

Q.37 : Difference between alpha testing and beta

testing :
Alpha Testing Beta Testing
It is performed by It is performed by clients
testers. or end users.
It is performed at It is performed at client
developers site. site.
Reliability & Security Reliability & Security
testing are not testing are performed.
performed.
Involves BBT and WBT. Involves only BBT.
Requires lab environment Doesn’t require lab & test
or test environment. environment.
Long execution cycle may Only few week of
be required. execution are required.
Q.38 : Levels of testing :

Levels of testing includes different methodologies

that can be used while conducting SW testing.
Initially, individual units are tested and once they are
tested , they are integrated and checked for
interfaces established between them.
Following are main level of SW testing :
1. Unit Testing : Its purpose is to validate that each
unit of SW design works properly.
2. Integration Testing : Its purpose is to expose the
faults in integrated units.
3. System Testing : Its purpose is to evaluate the
system’s compatibility.
4. Acceptance Testing : Its purpose is to evaluate
business requirement.

Q.39 : Agile Quadrants :

Quadrant 1 : ( Automated )
 In agile testing, the lower left quadrant
represents test driven development which is agile
development practice.
 It is automated contains tests that are designed
to improve the code of practical being created.
Quadrant 2 : ( Automated & Manual )
 This quadrant contains calls that are business
driven and are implemented to support the team.
 Tests in this quadrant are also support work of
development team but on higher level.
Quadrant 3 : ( Manual )
 This quadrant provides feedback to quadrant.
  This quadrant primarily emphasizes the response
for the previous two phases.
Quadrant 4 : ( Tools )
 This quadrant primarily emphasizes non -
functional requirements including compatibility,
performance , Security and consistency.

Q.40 : Agile Testing and Traditional Testing :

Agile Testing Traditional Testing
It is closely aligned with It is associated with
Agile Development waterfall model.
Methodologies.
It occurs through the It occurs as operate
development process. phase after development.
Encourages continuous Limits customer
customer involvement & interaction until the final
feedback. product delivery.
Starts early Occurs late
Lightweight work product Risk of over
documentation.
Provides high Security Provides less security

Q.41 : Agile Testing :

A SW testing is practice that follows the principle of
Agile SW Development is called Agile Testing.

Q.42 : ATLC :

Phase 1 : Impact Assessments :

In this phase, we collect the I/P and respond from
user and stakeholders to execute the impact
assessment phase.

Phase 2 : Agile Testing Planning :

 In this phase, the developers test engineer
stakeholders, customer & end test users come
together to plan the schedule of testing process.

Phase 3 : Release Redlines :

In this phase, we review the features that have
been developed are ready or not.

Phase 4 : Daily Scrums :

This phase includes the daily morning meeting to
keep check on testing & determine the objective of
day.

Phase 5 : Test Agility Review :

This last stage encompasses the weekly meeting
with stakeholders to evaluate and assess the program
against goals.

Q.43 : Advantages of Agile Testing :

1. It gives way to get regular feedback & reviews
directly form end users, which help us to enhance
the SW product quality.
 2. It saves lot of time and money.
3. It reduces documentation work.
4. It reduces error/bugs/defects & enhances SQ
quality.

Q.44 : Principles of Agile Testing.

1. Testing is not a phase : Agile team tests alongside
the development team to ensure that the
features implemented during given interaction are
actually done.
2. Everyone Tests : In agile testing the entire team
including analysis development and testers test
the application.