Software Testing Tools

Q1) What is software testing.Why it is needed.Also explain its

purpose.
Ans :
● Software Testing is a process of executing software or system with
intent of finding/detecting the errors.

★ Why it is needed :
● Software Testing is very important because it discovers defects/bugs
before the delivery of the software to the client ,which guarantees
the quality of the software.
● It makes the software error free ,more reliable and easy to use.

★ Its purpose:
● Checking product and documentation in order to determine how far
the needs and requirements are met.
● To find errors,defects to measure quality and risks.

Q2) What is the test case? How to design it.Which techniques are
used
for designing a test case.
Ans :
● A test case is a set of conditions under which a tester will determine
whether the functionalities of software are working properly or not.

★ How to design it :
● Designing the test cases is the most challenging assignment of test
engineers.
● Test cases have to be designed based on two criteria namely…
1) Reliability &
2) Validity.
● A set of test cases is considered to be reliable if it detects all errors.
● A set of test cases is considered as valid,if atleast one test case
reveals the errors.
★ Techniques for test case design :
1) Black box
2) White box
3) Experience-Based

Q3) Define Testing.

Ans : Testing is defined as “It is a process to execute a software/system
with the intent of finding /detecting errors.”
Q4) What is a test tool?What is its purpose?Also give name of
popular
testing tools.
● A testing tool is a software product that enables software testers to
define software testing tasks.

★ Its Purpose: The purpose of test tool is as follows :

● Using a test tool an organization achieves greater speed,reliability and
efficiency in the testing process and also better quality.

★ Some popular software testing tools are :

1) JMeter
2) LoadRunner
3) TestProject
4) CloudTest
5) Selenium
6) Katalon
7) Bugzilla

Q5) What is Fault.

Ans :
● A Fault is an incorrect step or process in computer programming that
causes the program to perform in an intended manner.
● A Fault is a missing or incorrect statement in a program resulting from
an error is a fault. So a Fault is the representation of an error.
● A computer programmer makes an error which results in a fault in the
software source code.
● A Fault is commonly called a Bug.

Q6) Define Error.

Ans :
● A mistake made by a computer programmer is called an Error.
● The error refers to the difference between the actual output and
correct output of the software.

Q7) Define Software Metric.

Ans :
● A Software Metric is a measurement based technique which is
supplied to processes , products and services to supply engineering
and management information.
Q8) What is the goal of Software Metric?
Ans : The goal of Software Metric is to identify and control essential
parameters that affect software development.

Q9) Define the objective of Software Metric?

Ans:
1) Measuring the size of the software quantitatively.
2) Assessing the level of complexity involved.
3) Estimating cost of resources and project schedule.
4) Assessing the testing technique.
5) Specifying when to stop testing.
6) Determining the date of release of the software.

Q10) What is meant by test case design techniques.Enlist them.

Ans :
● Test case design techniques are the key planning,designing and
implementing tests for software applications.
● These techniques involve various steps that aim to ensure the
effectiveness of test cases in uncovering bugs or other defects in
software programs.
● The main goal of test case design techniques is to test the
functionalities and features of the software with the help of effective
test cases.

★ Test case design techniques are :

1) Specification-Based.
2) Structure Based.
3) Experience Based.

Q11) What is Cyclomatic Complexity?

Ans :
● It is a software metric that provides a quantitative measure of the
logical complexity of a program.

Q12) What is code coverage testing?

Ans :
● Code coverage testing is a technique that involves measuring the
percentage of a system's code that is being tested by a test suite.
● Code coverage testing is determining how much code is being
tested.
● Formula :

Q13)
Explain (No. of lines to be
Branch executed)

coverage testing with its advantages and

Disadvantages.
Ans :
● Branch coverage testing techniques are used to cover all the
branches of the control graph.
● It covers all the possible outcomes of each condition of decision
point at least once.
● Branch coverage technique is a white box testing that ensures that
every branch of each decision point must be executed.
● Formula :

(No. of branches executed)

Branch Coverage =

● Branch coverage and decision coverage are very similar but there is
a key difference between two.
● Decision coverage technique measures the coverage of conditional
branches whereas Branch coverage technique measure the
coverage of
conditional and unconditional branches.

★ Advantages :
1) To validate that all the branches in the code are reached.
2) To ensure that no branches can be executed abnormally.
3) It eliminates problems that occur with statement coverage testing.

★ Disadvantages :
1) This metric ignores branches within boolean expressions which occur
due to short-circuit operation.
2) It is costly.
3) It takes more time to perform the task.

Q14) What is the formula to find coverage in Decision Coverage

testing.
Ans :

(No. of decision outcomes executed)

Decision Coverage =

Q15) Explain decision coverage testing with examples.

Ans :
● Decision coverage testing is a white box testing technique which
reports the True/False outcomes of each boolean expression of
source code.
● It covers all possible outcomes of each and every boolean condition
of the code by using CFG(Control Flow Graph) or chart.
● Generally a decision point has two decision values one is TRUE and
another is FALSE.Thus most of the times the total number of
outcomes is two.

★ Formula :

(No. of decision outcomes executed)

Decision Coverage =

★ Example :
1. Test ( int X)
2. { if ( X > 4 )
3. X=X*3
4. print( x)
5. }
Test Case 1 : X = 9
Explanation :
● The outcome of this code is “True” if condition (X>5 ) is
Checked.
● The Flowchart for the above code is Thus Decision Coverage =
50%
Q16) Enlist the various code coverage techniques.
Ans :
1) Statement coverage
2) Decision coverage
3) Branch coverage
4) Loop coverage
5) Path coverage

Q17) List the goals of Loop coverage techniques.

Ans :
1) To fix the infinite loop repetition problem.
2) To know the performance.
3) To identify the loop initialization problems.
4) To determine the uninitialization problems.

Q18) What is simple loop testing?

Ans :
● Testing performed in a simple loop is known as simple loop testing.
● It is a type of testing that is performed basically to test the condition
of the loop whether the condition is sufficient to terminate the loop
after some point of time.

Q19) Differentiate between a specification and structural test case

design.
Ans :

Sr.No Specification test case design. structural test case design.

1 The main objective is to test the The main objective is to test the
functionality,behavior of an infra-structure of an application.
application

2 Knowledge of code is not required. Knowledge of code is required.

3 This is less time consuming This is more time consuming

4 Tester can identify missing Testers can identify defects in

functionalities implementation features.

Q20)What is the formula to find coverage in Statement Coverage

testing.
Ans :

(No. of statements executed)

Statement Coverage =
X 100 %
Q21) Define Path Coverage.
Ans :
● The Path Coverage base technique strategy requires us to design
test cases such that all linearly independent paths in the programs
are executed at least once.

Q22) Define Branch Coverage.

Ans :
● Branch coverage technique is a white box testing that ensures that
every branch of each decision point must be executed.

Q23) Define Statement Coverage testing.

Ans :
● Statement Coverage is the simplest form of white box testing ,where
a series of test cases are run such that each statement is executed
at least once.

Q24) Write a note on Path-Coverage Testing.

Ans :
● The Path-Coverage based testing strategy requires us to design test
cases such that all linearly independent paths in the program are
executed at least once.
● In the Path testing method , the control flow graph of a program is
designed to find a set of linearly independent paths of execution.
● In this method ,Cyclomatic complexity is used to determine the no.of
linearly independent and then test cases are generated for each
path.
● Path Testing Process :
Q25) Explain Statement Coverage testing with examples.
Ans :
● Statement Coverage is the simplest form of white box testing ,where
a series of test cases are run such that each statement is executed
at least once.
● Statement Coverage is used for calculation of the number of
statements in source code which have been executed.
● The main purpose of Statement Coverage is to cover all possible
paths,lines and statements in source code.

★ Example :

★ Explanation :
1) Test case 1 : If X=6 and Y=2 Statement Coverage Code is =
2) Test case 1 : If X=-4 and Y=-6 Statement Coverage Code is =

Q26) Give the classification of loop testing.Explain any one in

detail.
Ans :
● Classification of loop testing is :
1) Simple Loop Testing
2) Nested Loop Testing
3) Concatenated Loop Testing
4) Unstructured Loop Testing

1) Simple Loop Testing :

● Testing Perform in a simple loop is known as Simple Loop Testing.

● Simple loop is basically a normal “for”,”while” or “do-while” in which
condition is given & loop runs and terminates according to True or
False condition.
● It is a type of testing basically to test the condition of a loop.
● For example :

2) Nested Loop Testing :

● Testing performed in a nested loop is known as Nested loop testing.
● Nested loop is basically one loop inside another loop.
● In a nested loop there can be a finite number of loops inside a loop
and there a nest is made.
● It may be either of any of three loops i.e., for, while or do-while .

3) Concatenated Loop Testing:

● Testing performed in a concatenated loop is known as Concatenated

loop testing.
● It is performed on the concatenated loops.
● Concatenated loops are loops after the loop. It is a series of loops.
● Difference between nested and concatenated is that in nested loop
is inside the loop but there loop is after the loop.

4) Explain Unstructured Loop Testing.

● Testing applied on an unstructured loop is known as Unstructured
Loop Testing.
● Unstructured loop is the combination of concatenated and tested
loop.
● In other words,It is a group of loops that are in no particular order.
● For Example :
Q27 )What is an Experience-based technique?
Ans :
● It is test case design technique are used complement black-box and
White-box technique.
● In this,People knowledge ,skills and experience are required.In this
the both technical & business people required.
● It is based on human knowledge and experience.
Chapter 3

Q1) What is the test plan?

Ans :
● A test plan can be defined as a “detailed document that describes
the scope ,approach ,schedule,resource etc. of intended software
product testing activities.

Q2) What is the test incident report?

Ans :
● Test incident report is an entry created in the detect repository with
a unique ID for each incident encountered.
● The test incident report documents all issues found during the
various phases of testing.

Q3) What is meant by exit criteria in the test plan.

Ans :
● Exit criteria defines the benchmarks that signify the successful
completion of a test phase or project.
● The exit criteria are the expected results of tests and must be met
before moving on to the next stage of development.

Q4) What is the Entry Criteria?

Ans :
● The Entry Criteria are the conditions that must be met before you
can start the test.

Q5) Define Errors with different types.

Ans :
● An Error is a mistake made by the programmer in the code that's
why we can not execute or compile code.
● Types of errors are :
1) Syntax Errors
2) Logical Errors
3) Functional Errors
4) Missing Command Errors

Q6) What is the test case?

Ans :
● A test case is a set of actions performed on a system to determine if
it satisfies software requirements and functions correctly.
Q7) What are the objectives of writing cases?
Ans :
1) To guide testers through their day-to-day hands-on activity.
2) To validate specific features and functions of software.
3) To provide a blueprint for future projects.
4) Helps to detect usability usages and design gaps early on.

Q8) What is the test report?

Ans :
● A test report is an organized summary of testing
objectives,activities and results.
● It is created and used to help stakeholders to understand product
quality.

Q9) What is the test Scenario.

Ans :
● A Test-Scenario is a statement describing the functionality of the
application to be tested.
● It is used for end-to-end testing of a feature.
● It is a documentation of a use case.

Q10) Define test -planning.

Ans :
● Test planning is the most important activity to ensure that there is
initially a list of tests and milestones in a baseline plan to track the
process of the project.
● Test planning also defines the size of the test effort.

Q11)List the general components of the test plan.

Ans :
1) Test Plan ID
2) Introduction
3) Scope
4) Test Strategy
5) Test Items
6) Features to be tested
7) Features not to be tested
8) Approach
9) Item Pass/Fail criteria

Q12) What is suspension Criteria?

Ans :
● Suspension Criteria means suspending the complete or part of the
testing activities.
● It defines the benchmarks for suspending all tests.

Q13)What is Test Strategy?

Ans :
● Test strategy is an integral part of software development.
● It is used to identify the level of testing.

Q14) Define Test Summary Report.

Ans :
● It is a simple as the name suggests it is a closure report of the
product.
● A test summary report is a Test Document that formally summarizes
the result of testing.
● The manager prepares this document at the end of testing.
Chapter 4
Q1) What is the defect?
Ans :
● The variation in the expected result and actual result is known as
defect.
● A defect is an error or bug in an application.
● A defect can be defined as “inconsistency in the behavior of the
software”.
● Defects in testing tools can arise due to various reasons, such as
programming errors, design flaws, compatibility issues, or usability
problems.

Q2) What are Requirement Defects?

Ans :
● These defects arise in a product when one fails to understand what
is required by the customer.
● It may occur due to customer’s gap where the customer is unable to
define his requirement.
● These defects can arise due to misunderstandings, ambiguities,
inconsistencies,or incompleteness in the requirements
documentation.
● These defects can be classified into :
1) Functional Defects
2) Interface Defects
● For example :
➢ Imagine a project to develop a messaging app. The
requirement states that users should be able to send
messages to each other.
➢ However, the requirement does not specify whether the
messaging feature should support sending multimedia files like
images or videos.
➢ During development, the team assumes that sending
multimedia files is not required since it's not mentioned in the
requirement.
➢ Later, during testing or after the app is released, users
complain that they can't send images or videos through the
messaging feature, which they expected to be included.
➢ This oversight represents a requirement defect because the
requirement documentation did not explicitly address the need
for supporting multimedia files, leading to a gap in
functionality compared to user expectations.

Q3) What is a design defect?

Answer:
● A design defect means that something inherent in the product's
design makes it unreasonably dangerous to the users.
● They may be due to problems with design creation and
implementation during SDLC.
● A design defect means that the product was manufactured correctly,
but the defect is inherent in the design of the product itself, which
makes the product dangerous to consumers.
● Design defects occur during the conceptualization and planning
phases of product development and can lead to issues with the
product's functionality, performance, safety, or usability.
● For example, mechanical defects, which are common occurrences in
cars and other motor vehicles.

Q4) What is a coding Defect?

Ans :
● These defects may arise when designs are implemented wrongly or
a program fails to execute a specific function correctly due to an
error in the code.
● If there is an absence of coding standards,it may lead to coding
defects.
● It can be classified into :
1) Variable initialization
2) Commenting defects
3) Database related.
● For Example : Imagine a program designed to calculate the total
price of items in a shopping cart. However, due to a coding defect,
the program fails to add the prices of certain items, which results in
an incorrect total.

Q5) What are Functional Defects?

Ans :
● Functional Defects are mainly about the functionalities
present/absent in the applications which are expected/not expected
by the customer.

Q6) What are Testing Defects ?

Ans :
● This testing was introduced in an application due to wrong testing.
● Testing defects are found during software testing processes, where
testers systematically examine the software to identify and report
any deviations from expected behavior.
● It can be classified into :
1) Test Design
2) Test Tool
3) Test Environment
● For Example : Login feature for a website. During testing, you notice
that even when entering the correct username and password, the
system sometimes fails to authenticate the user and allows access
to unauthorized users.

Q7) When to define defects in “New” state.

Ans :
● When a new defect is found ,it is in a “New” state.

Q8) Define Priority.(Or Define Defect Priority)

OR Define priority defect and its different levels.
Ans :
● Priority is defined as the order in which the defects should be
resolved.
● It is usually set by the QA-Team.
● The Priority status is set based on the requirements of the end users.
● For example : if the company logo is incorrectly placed in the
company's web page then the priority is high but it is of low severity.

Q9) How Priorities can be categorized.(Levels of Priority)

Ans : A Priority can be categorized in the following ways :
1) Low − This defect can be fixed after all the critical defects are
(fixed) resolved.
2) Medium −Means the defect should be fixed in the next versions or
updates of the software.
3) High − The defect must be resolved immediately because the
defect affects the application to a considerable extent and the
relevant modules cannot be used until it is fixed.
4) Urgent − The defect must be resolved immediately because the
defect affects the application or the product severely and the
product cannot be used until it has been fixed.

Q10) Define Severity.

Ans :
● Severity refers to how much trouble the defect causes in the
application and how difficult it is to fix in the code.
● It is set by the development team.
● It is related to the development aspect of the product.
● Severity status provides an idea how much the defect has affected
the functionality of the application.
● For Example − For flight operating websites, a defect in generating
the ticket number against reservation is high severity and also high
priority.

Q11) How Severity can be categorized.

Ans : A Severity can be categorized in the following ways :

1) Critical /Severity 1 −
● Defect impacts the most crucial functionality of Application
and the QA team cannot continue with the validation of
application under test without fixing it.
● For example, App/Product crashes frequently.
2) Major / Severity 2 −
● Defect impacts a functional module; the QA team cannot test
that particular module but continue with the validation of other
modules.
● For example, flight reservation is not working.
3) Medium / Severity 3 −
● Defect has issues with a single screen or related to a single
function, but the system is still functioning.
● The defect here does not block any functionality.
● For example: Ticket number format doesn't follow the correct
pattern of having alphabetical characters for the first five
characters and numeric characters for the last five characters.
4) Low / Severity 4 −
● It does not impact the functionality.
● It may be a cosmetic (appearance) defect, UI inconsistency for
a field or a suggestion to improve the end user experience
from the UI side.
● For example, the background color of the Submit button does
not match with that of the Save button.

Q12) List the types of defects.

Ans :
1) Requirement Defect
2) Coding Defect
3) Design Defect
4) Testing Defect

Q13) Explain classification of Defects.

Ans :
● Defects can be classified as :
1) Priority
2) Severity

● From the QA team's perspective, defects are classified based on

their Priority. This means determining how urgently they need to be
fixed or addressed.
● From the development team's perspective, defects are categorized
based on their Severity. Severity refers to how serious or impactful
the defect is on the system or application's functionality.
● From the QA team perspective Defects are classified from the QA
team perspective as Priority and from the development perspective
as Severity

Q) Define Severity and Priority :

Severity measures the impact of a defect on a software's functionality, while

priority measures how urgent the defect is to fix.
Severity
● How much a defect impacts the software's usability
● How much a defect disrupts the user experience
● How much a defect impacts the software's functionality
● An objective measure of a bug's impact

Priority
● How soon a defect should be fixed
● How much a defect impacts the business or users
● How much a defect impacts development timelines
● How much a defect impacts customer impact
● A subjective measure that may vary between users or businesses

Example
● A misspelling on a website's home page might be low severity but
high priority because it affects the brand's reputation
●
● A bug that prevents a user from logging into an application might be
high severity and high priority

Q14) What is the “Deferred” state?

Ans :
● If the developer feels that the defect is not a very important
priority,it can be fixed in the next release, which is called “Deferred”.

Q15) What is the Defect Report?

Ans :
● A Defect Report describes defects in software and documentation.
● A Defect Report is also called a Bug Report.

Q16)List out the types of software defects by priority.

Ans :
1) Immediate/Critical
2) High
3) Medium
4) Low

Q17) List out the types of software defects by Severity.

Ans :
1) Critical
2) Major
3) Minor
4) Low

Q18) What are Critical Defects?

Ans :
● A Critical Defect is a defect that leads to the complete failure of the
software system.
● Critical Defects critical functionality or critical data.
● It does not have a workaround.

Q19)What is meant by high priority defect.

Ans :
● Defects with high priority and low severity status must be corrected
immediately but do not harm the application.

Q20) What are Testing Defects ?

Ans :
● This testing was introduced in an application due to wrong testing.

Q21)What is the defect? List it causes in s software.

Ans :
● The variation in the expected result and actual result is known as
defect.
● A defect is an error or bug in an application.
★ Root Causes of Defect are :
● Requirements are not defined clearly by the customer.
● Designs are wrong and not implemented properly.
● People are not trained for work in collecting requirements.
● Testing is not capable.
Q22) What is the test case ?Explain the general test case
template
briefly.
Ans :
● A test case is a set of actions performed on a system to determine if
it satisfies software requirements and functions correctly.

1) Test Case ID : Each test case ID should be represented by a Unique

ID.
2) Test Case Description : Pick a test case from the test scenario.
3) Pre- Conditions : Conditions that need to be met before executing
the test case.
4) Post- Conditions : Conditions that need to be achieved when the test
case was successfully executed.
5) Expected Result : The result which we expect once the test cases
were executed.
6) Actual-Result : The result which shows once the test case was
exceuted.
7) Status : Finally set the status as pass or fail based on the expected
result against the actual result.

Q23)What is the defect in the Life Cycle?

Ans :

● Defect Life Cycle is a cycle in which a defect goes through during its
lifetime.
● The defect life cycle starts when a defect is found and ends when a
defect is closed ,after ensuring it is not reproduced.
● Its life cycle is representation of different states of different levels.

● Diagram :
Q24) Explain different states of defect in defect workflow.
Ans :
1) New :
● Whenever any new defect is found in an
application/software ,it is defined as “New” state.
2) Assigned :
● Newly created defect is assigned to the development team on
which the manager of the project has to work.
● This state is defined as an “Assigned State”.
3) Open :
● In the open state ,the developer analyzes the defect,works on
it and fixes it if required.
4) Fixed :
● When a developer finishes the task of fixing a defect by
making the required changes ,then it is marked as “fixed”.
5) Retest :
● At this point the Tester starts the task of retesting the defect
to verify if the defect is fixed properly by the developer or not
as per the requirement.
6) Verified :
● After re-testing of the defect ,If the tester does not find any
issue in the defect after being assigned to the developer then
it goes to the next state which is closed.
● And if the tester feels that the defect has been fixed
accurately,then the status of the defect gets assigned to
“verified” .
● If the defect is not fixed properly by the developer,then it is
sent to the Re-open state.
7) Closed :
● When the defect does not exist any longer,then the tester
changes the status of the defect to “Closed”.
Q25) Explain the attributes of the defect report.
Ans :
1) Defect ID : It is the unique identification number for the defect.
2) Defect Name : It is the name of the defect which explains the defect
in brief,its nature and type.
3) Project Name : It indicates the project for which the defect is found.
4) Module Name : For which the defect is found may be mentioned to
create a reference.
5) Phase Introduced : It gives information about when the defect has
been added in the application being involved.
6) Phase Found : It is the phase of the project when a defect is found is
added here.
7) Severity : It defines the severity of the defect which is declared in
the test plan.
Chapter 5
Q1) Define Manual Testing.
Ans :
● Manual Testing is the process of testing software for defects
manually.
● It is the oldest type of software testing.
● It is a method used by software developers to run tests manually
without the usage of automation tools or scripts.
● It is a process that is carried out manually in order to find defects
without using tools or scripts.

Q2) List limitations of Manual Testing.

Ans :
1) Manual Testing is slow and costly because it takes a long time to
complete the test.
2) It increases cost.
3) Manual testing does not scale well.
4) Manual Testing is not repeatable.
5) Lack of Training is a common problem.
6) Testing is difficult to manage.

Q3) What is automated testing?

Ans :
● Automated testing is done automatically without human involvement
by using testing tools and various testing frameworks.

Q4) What are Automation Testing Tools?

Ans :
● An Automation Testing Tool is software that lets us define software
testing tasks.
● Automated Testing Tools vary in their underlying approach,quality,
and ease of use.

Q5) List different test automation frameworks.

Ans :
1) Data Driven Automation framework.
2) Keyword Driven Automation framework
3) Modular Automation framework
4) Hybrid Automation framework
Q6) Define Test Automation.
Ans :
● Test Automation is the process of testing various parts of new
software with no involvement of human beings.
● It makes sure every aspect of software design works without humans
sitting in front of computing hours to manual testing.

Q7) What are the characteristics of testing tools?

Ans :
1) Testing tools should be easy to use.
2) Testing tools should use one or more testing strategies for
performing testing on the host and target platform.
3) Testing tools should support GUI-Based test preparation.

Q8)Explain different types of testing tools.

Ans :
1) Static Analysis Tools :
● It is used for static testing which is used by developers.
2) Test Management Tools :
● It is used for test managing,scheduling,defect logging,tracking and
analysis.
● It is used by the tester.
3) Performance Testing Tools :
● It is used for monitoring the performance response time.
● It is used by the tester.
4) Test Execution Tools :
● It is used for implementation and execution.
5) Incident Management Tools :
● It is used for managing the tools.
● It is used by Testers.

Q9) Enlist two open source automation Tools.

Ans :
1) Selenium
2) Katalon
3) Apache JMeter
4) K6
Q10) What are the benefits of Automation Testing?
Ans :
1) Faster Feedback Cycle :
● Test Automation helps to reduce the feedback cycle.
2) Increase Efficiency :
● Test Automation is useful because it detects errors during the
development process.
3) Reliable : Eliminating human errors.
4) Repeatable :
● We can repeat the execution of some operations.
5) Re-Usable :
● We can reuse tests on different versions of an application.
6) Better Quality Software :
● It provides better quality of software.
7) Fast : Automation tools run faster than human users.
8) Cost Reduction : we can save money and time by using an
automated test environment.
9) Improve Accuracy : Automation testing can execute tests with 100%
accuracy.
10)It vastly increases test coverage.

Q11) Write a note on Selenium.

Ans :
● Selenium is one of the most commonly used open source test
automation tools.
● The tool supports multiple programming languages such as
C#,java,python etc to create selenium scripts.

Q12) List out Selenium installation steps in short.

Ans:
1) Download and install the latest version of Java & JDK.
2) Download and install the latest version of Eclipse.
3) Download Zip of Selenium and Extract it in one folder(.jar files)
Q13) Differentiate between Manual Testing and Automated
Testing.
Ans :
Sr.N Manual Testing Automated Testing
o

1 It is the process which is conducted Automation testing is a process

manually without any help of any which is conducted with the help of
automated tool. automation tools.

2 It is performed by humans. It is performed by automation tools

or scripts.

3 It is less reliable It is more reliable

4 It is slow and time consuming It is faster as compared to manually

testing.

5 In this investment requirement for In this,automation tools are

human resources required.

6 There is no need for a programming There is Need for a programming

language in manual testing. language in automated testing.

7 Gives Low quality Give high quality

8 It is not costly. Initial cost of automation testing is

more than manual testing.

9 The Regression Testing process is The Regression Testing process is

difficult to perform. easy to perform by tools.

10 Testing large amounts of software It is easy to test large amounts of

can be challenging. software.

Q14 ) Write any two features of Bugzilla Tools.

Ans :

1) Bugzilla is powerful and it has advanced searching capabilities.

2) Bugzilla supports user configurable email notifications whenever the
bug status changes.
3) Bugzilla displays the complete bug change history.
4) Bugzilla provides inter bug dependency track and graphic
representation.
5) Bugzilla allows users to attach Bug supportive files and manage it.
6) Bugzilla has an integrated, product-based, granular security schema
that makes it more secure.
7) It has a complete security audit and runs under Perl's taint mode.
8) Bugzilla supports a robust, stable RDBMS (Relational Database
Management System) back end.
9) It supports Web, XML, E-Mail and console interfaces.
10) Bugzilla has a wide range of customized, user preferences
features.
11) It supports localized web user interface.
12) Bugzilla has a smooth upgrade pathway among different versions.