CCS366 Software Testing Automation

Unit-I
FOUNDATIONS OF SOFTWARE TESTING
PART - A
1) Define Software Engineering.
Software Engineering is a discipline that produces error free software with in
a time and budget.

2) Define software Testing.

Testing can be described as a process used for revealing defects in software,
and for establishing that the software has attained a specified degree of quality with
respect to selected attributes.
3) Why do we need software testing?
 Preventing bugs,
 Cost-effective
 Product-Quality
 Security

4) Differentiate between verification and validation?(U.Q Nov/Dec 2009)

Verification Validation
1. Verification is the process of 1. Verification is the process of
evaluating software system or evaluating software system or
component to determine whether the component during
products of a given development phase or at the end of the , the development
satisfy the conditions imposed at the start phase satisfy the conditions imposed at
of that phase. the start of that phase.
2. Verification is usually associated with
activities such as inspections and 2.Verification is usually associated with
reviews of the s/w deliverables. Traditional execution _based testing, i.e.,
Exercising the code with testcases.
5) Define the term Testing.
 Testing is generally described as a group of procedures carried out to evaluate
some aspect of a piece of software.
 Testing can be described as a process used for revealing defects in
software, and for establishing that the software has attained a specified
degree of quality with respect to selected attributes.

6) Differentiate between testing and debugging.

Testing Debugging

1. Testing as a dual purpose 1. Debugging or fault localization is

process the process of
 Reveal defects  Locating the fault or defect
 And to evaluate  Repairing the code, and
quality attributes  Retesting the code.
7) List the members of the critical groups in a testing process
 Manager
 Developer/Tester
 User/Client

8) Define Error.
An error is mistake or misconception or misunderstanding on the part of a
software developer.
9) Define Faults (Defects).
A fault is introduced into the software as the result of an error. It is an
anomaly in the software that may cause nit to behave incorrectly, and not according
to its specification.
10) Define failures.
A failure is the inability of a software or component to perform its required

functions within specified performance requirements.

11) Distinguish between fault and failure. (U.Q May/June 2009)
Fault Failure
1. A fault is introduced into the 2. A failure is the inability of a
software as the result of an error. It software or component to
is an anomaly in the software that perform its required functions
may cause nit to behave incorrectly, within specified performance
and not according to its requirements.
specification.

12) Define Test Cases.

A test case in a practical sense is attest related item which contains the following
information.
 A set of test inputs. These are data items received from an external
source by the code under test. The external source can be
hardware, software, or human.
 Execution conditions. These are conditions required for running the
test, for example, a certain state of a database, or a configuration of a
hardware device.
 Expected outputs. These are the specified results to be produced by
the code under test.

13) Write short notes on Test, Test Set, and Test Suite.
A Test is a group of related test cases, or a group of related test cases and
test procedure.
 A group of related test is sometimes referred to as a test set.
A group of related tests that are associated with a database, and are usually run
together, is sometimes referred to as a Test Suite.
14) Define Test Bed.
A test bed is an environment that contains all the hardware and software needed to test
a software component or a software system.

15) Define Software Reliability?

Software Reliability is defined as the probability of failure-free software operation for a
specified period of time in a specified environment.
16) Define Software Safety?
Software Safety is defined as the probability of mishap-free software operation for a specified
period of time in a specified environment.
17) Compare Black-Box and White Box Testing?
Black box testing White box Testing
Black box testing , the tester is no The White box approach focuses on the
Knowledge of its inner structure(i.e. how inner structure of the software to be
it woks)The tester only has knowledge tested.
of what it does(Focus only input &
output)
Black box approach is usually White box approach is usually
applied large size piece of software. applied small size piece of software.
Black box testing sometimes called White box sometimes called clear or glass
functional or specification testing. box testing.
18) What is Program Inspection?
A code inspection is a set of procedures and error-detection techniques for group code reading.
Most discussions of code inspections focus on the procedures, forms to be filled out.

19) Define coupling.?

The coupling is the measure of the degree of interdependence between units. Two units with
high coupling are strongly connected and thus, dependent on each other.

20) What is System Testing?

A system is defined as a combination of the software, hardware and other associated parts that
together provide product features and solutions. System testing ensures that each system
function works as expected and it also tests for non-functional requirements like performance,
security, reliability, stress, load, etc.

21) What are the Integration strategies?

 Top_ Down: In this strategy integration of the module begins with testing
the upper level modules.
 Bottom_ Up: In this strategy integration of the module begins with testing
the lowest level modules.

22) Define Error Guessing.

The tester/developer is sometimes able to make an educated “guess’ as to which type of
defects may be present and design test cases to reveal them. Error Guessing is an ad-hoc
approach to test design in most cases.

23) What is Inspections?

It is a type of review that is formal in nature and requires pre-review preparation
on the part of the review team. The Inspection leader prepares is the checklist of items
that serves as the agenda for the review.

24) Why Equivalence & Boundary Analysis Testing need?

1. This testing is used to reduce a very large number of test cases to manageable chunks.
2. Very clear guidelines on determining test cases without compromising on the effectiveness of
testing.
3. Appropriate for calculation-intensive applications with a large number of variables/inputs

25) What do you mean by functional requirements and non-functional requirements?

Functional requirements: Functional requirements define a function that a system or system element
must be qualified to perform and must be documented in different forms. The functional requirements
describe the behavior of the system as it correlates to the system's functionality.

Non-functional requirements: Non-functional requirements are not related to the software's

functional aspect. Basic non-functional requirements are - usability, reliability, security, storage, cost,
flexibility, configuration, performance, legal or regulatory requirements, etc.

Part- B & C
1. State and explain Software testing principles.
2. Explain in detail the tester’s role in a software development organization
3. Explain in detail Black-Box and White-box Testing?
4. Illustrate with an example the following Black-Box testing Techniques
i. Boundary Value Analysis
ii. Equivalence Partitioning
5. Explain in detail about V-Model of Software Testing?
6. Explain in detail about Software Testing Life cycle?
7. Explain about various stages of Testing?
8. Illustrate with an example the following White-Box testing Techniques
i. Logic Coverage
ii. Conditional Coverage
 Unit-II- TEST PLANNING
PART-A

1) What is the goal of Software Tester?

The goal of Software tester is to find bugs, find the as early as possible, and make sure
they get fixed

2) What is Test Planning?

A Test Plan is a detailed document that catalogs the test strategies, objectives, schedule,
estimations, deadlines, and resources required to complete that project. Think of it as a
blueprint for running the tests needed to ensure the software is working correctly.
 
3) What is Test Strategy?
Test strategy is a high-level and comprehensive document describing the software testing
approach. It comprises various components like scope, objectives, customer
communication strategy, documentation formats, test processes, etc.

4) Difference Between Test Strategy and Test Plan

Test Plan Test Strategy
Test strategy is a set of guidelines
A test plan for software project can be
that explains test design and
defined as a document that defines the
determines how testing needs to be
scope, objective, approach and emphasis on
done
a software testing effort

Test Plan can change Test strategy cannot be changed

It is set at organization level and
It is defined at project level
can be used by multiple projects

5) Define Bug Reporting?

Bug reporting is an integral part of software testing as it helps to identify and
document any issues that arise during the process. By using a Bug report, testers can track
the progress of their work and compare results over time. This allows them to change
their test plans and strategies if needed.

6) What is Test Release Document(TRD)?

A document that programmers release with each build stating what’s new, different, fixed
and ready for testing.

7) What is Test Schedule?

A test schedule includes the testing steps or tasks, the target start and end dates, and
responsibilities. It should also describe how the test will be reviewed, tracked, and
approved.
 8) What is Metrics and Statistics?
Metrics and Statistics are the means by which the process and the success of the project and the
testing are tracked.

9) Differentiate Test case and Test Scenario?

S.N Test Case Test Scenarios

O
1. The test case is a detailed document, The test scenarios are those
which provides information about derived from the use case and
the testing strategy, testing process, give the one-line information
preconditions, and expected output. about what to test.
2. It includes all the positive and Test scenarios are one-liner
negative inputs, navigation steps, statement, but it is connected
Expected results, pre and post with several test cases.
condition, etc.
3. These are low-level actions. These are high-level actions.
4. The main objective of writing the test Writing the test scenario's main
case is to verify the test scenario by objective is a cover end to end
implementing steps. functionality of a software
application.
5. It takes more time as compared to test It takes less time as compared to
scenarios. test cases.

10) What is Test Phases in Test planning?

Test planning process should identify each test phase and make each phase known to project
team. This process helps the entire team and understand the overall development model.

11) What are entrance and exit criteria?

 The Entry criteria are the conditions that must be met before you can start the test. For a simple test,
this section of the test plan would list the hardware and software that needs to be operational.

The Exit criteria, the conditions that must be met before the test is completed. Exit criteria apply more
to function tests than to other types of tests.

PART B & C

1. Explain about Test Planning in detail?

2. Explain in detail High-level Expectations?
3. Briefly explain Test Strategy and Test Planning?
4. Explain about Resource Requirements in Software testing?
5. Explain about Test Schedule :
6. Briefly explain about Test cases and Test scenario with example.