B.

Tech CSE & IT, Batch(2020-24)-VII

Lecture-5
Software Testing Tools

By
Prof. Shubhangi Deokar
Department of Computer Science and Engineering
Symbiosis Institute of Technology, Lavale
Test Bed
The test execution environment configured for testing.

Test bed consists of specific hardware, software, Operating system, network configuration, the product under
test, other system software and application software.
Test Bed Configuration:

It is the combination of hardware and software environment on which the tests will be executed. It includes hardware
configuration, operating system settings, software configuration, test terminals and other support to perform the test.
Example:A typical test bed for a web-based application is given below:
Web Server - IIS/Apache
Database - MS SQL
OS - Windows/ Linux
Browser - IE/FireFox
Java version : version 6
Test Bed
Traceability Matrix
Ability to display a relationship to groups of entities through an interactive matrix
view, called the ‘Traceability Matrix.’
The ‘Traceability Matrix’ displays an entity’s relational hierarchy to other entities
in your database.
Different levels of documentation
● Test Script: A line-by-line description of all the actions and data needed to
perform a test.
● Test Case: Describes a specific idea that is to be tested, without detailing the
exact steps to be taken or data to be used.
● Test Scenario: It is a simple description of an objective a user might face
when testing.
Test Scenario
A test scenario also called as Test Condition or Test Possibility is a document that specifies all the
functionalities that need to be tested for a software application to deliver what it is meant to.

Exactly defining what should be tested as part of a particular feature or application, a test scenario calls for the
tester to identify himself as the end-user.
Test Cases
A test case is a defined format for software testing required to check if a particular
application/software is working or not.

A test case consists of a certain set of conditions that need to be checked to test an
application or software i.e. in more simple terms when conditions are checked it checks
if the resultant output meets with the expected output or not.

A test case consists of various parameters such as Id, condition, steps, input, expected
result, result, status, and remarks.
● After test scripts, test cases are the second most detailed way of
documenting testing work.
● They describe a specific idea that is to be tested, without detailing the exact
steps to be taken or data to be used. For example, in a test case, you
document something like ‘Test if coupons can be applied on actual price‘. This
doesn’t mention how to apply the coupons or whether there are multiple ways
to apply. It also doesn’t mention if the tester uses a link to apply a discount, or
enter a code, or have a customer service apply it. They give flexibility to the
tester to decide how they want to execute the test.
Test Case Management Tools Used
● JIRA
● JunoOne
● Klaros-Test management
● QACoverage
● Qase
● SPIRATEST by Inflectra
● TestFLO for JIRA
● Testpad
● XQual
● Xray
● Zephyr Scale
● Zephyr Squad
EX.Test Case Management Tools Used
● Testpad is a simple tool that makes test case management easier.
● Few features of Testpad include manual testing, reports of the test cases and
software, dragging and dropping to make testing easier, inviting guest testers
by email, building custom templates, and much more.
● TestCaseLab: TestCaseLab is easily manageable for the test cases and
could swiftly integrate them with bug trackers.
● The features of TestCaseLab include Custom test cases, Test Runs,
Integrations of test cases, Test Plans, tags and priority for test cases, search
by name of test cases, description and tags, etc
Types of Test Cases…
Test cases can be categorized based on the purpose they serve in testing. As a quality assurance
professional, knowing the difference between them helps focus your efforts and choose the right test
format.
● Functionality test cases: These are the most basic and obvious test cases to write. They ensure
that each feature of your system works correctly.
● Performance test case: This test ensures that the system runs fast enough. It makes sure that all
system requirements work as expected regarding speed, scalability, or stability.
● Unit test cases: Software developers usually write unit tests for their code to check individual
units, for example, modules, procedures, or functions, to determine if they work as expected.
● User interface (UI) test cases: It’s important to remember that the user interface is part of the
overall system and not just a shell where functionality appears. UI test cases check that each UI
element works correctly, displays, and is easy to use.
● Security test cases: Security test cases help ensure that a product or system functions properly
under all conditions, including when malicious users attempt to gain unauthorized access or
damage the system. These test cases safeguard the security, privacy, and confidentiality of data.
Types of Test Cases

● Integration test cases: These ensure that the application components work together as expected. These test cases check whether
modules or components integrate seamlessly to form a complete product.

● Database test cases: These test cases ensure that the database meets its functional and non-functional requirements. They make sure
database management systems (DBMS) support all business requirements.

● Usability test cases: Usability test cases help check if users can use the application successfully. These
determine whether users can easily use the system without difficulty or confusion.
They also verify if users can navigate the system using common procedures and functions.

● User acceptance test cases: User acceptance test cases verify that an application satisfies its business requirements before users accept
it. These determine whether users accept or reject the output produced by a particular system before release to the live environment.

● Regression testing: Regression test cases verify that changes made during development don’t cause any existing functionality to stop
working.
Regression testing happens after changes have been made to existing code to test that all existing or legacy
functionality continues to work as expected after making the changes.
Why Test Cases?
● Documentation means you can guarantee the coverage of your tests.
● You can reduce software maintenance and bug fixes and support future
costs.
● Test cases can be used again in current and future projects.
● You can improve the quality of the software and the user experience.
● A higher quality product means more satisfied customers and higher profits.
 Test Parameters
● Module Name: Subject or title that defines the functionality of the test.
● Test Case Id: A unique identifier assigned to every single condition in a test case.
● Tester Name: The name of the person who would be carrying out the test.
● Test scenario: The test scenario provides a brief description to the tester, as in providing a small overview to know about what needs to be performed

and the small features, and components of the test.

● Test Case Description: The condition required to be checked for a given software. for eg. Check if only numbers validation is working or not for an age

input box.
● Test Steps: Steps to be performed for the checking of the condition.
● Prerequisite: The conditions required to be fulfilled before the start of the test process.
● Test Priority: As the name suggests gives the priority to the test cases as in which had to be performed first, or are more important and which could be

performed later.
● Test Data: The inputs to be taken while checking for the conditions.
● Test Expected Result: The output which should be expected at the end of the test.
● Test parameters: Parameters assigned to a particular test case.
● Actual Result: The output that is displayed at the end.
● Environment Information: The environment in which the test is being performed, such as operating system, security information, the software name,
Test Case Templates
● Test Case Template - Bing images