SOFTWARE TESTING AND

QUALITY ASSURANCE (STQA)

MINI PROJECT – 1
ASHWINI MADAVI
SAYALI MAKAR
INDEX 1. TITLE
2. PROBLEM DEFINITION & SCOPE
3. OBJECTIVES
4. HARDWARE & SOFTWARE REQUIREMENTS
5. BRIEF OVERVIEW OF CONCEPTS USED
6. APPLICATION TO BE TESTED
7. TEST PLAN
8. IMPLEMENTATION
9. CONCLUSION/(S)
TITLE

 Design and Develop a Hospital patient data storage

system and perform Unit and Integration tests on the
application using the Junit library in Java.
PROBLEM DEFINITION & SCOPE

Problem Definition :
Create a small application by selecting relevant system environment/platform and programming languages.
Narrate concise Test Plan consisting features to be tested and bug taxonomy. Prepare Test Cases inclusive of Test
Procedures for identified Test Scenarios. Perform selective Black-box and White-box testing covering Unit and
Integration test by using suitable Testing tools. Prepare Test Reports based on Test Pass/Fail Criteria and judge the
acceptance of application developed.

Scope :
To design and develop a small application and perform unit and integration tests on the application by using
relevant testing tools and frameworks/platforms.
OBJECTIVES

1. Learn how to prepare test cases inclusive of test procedures for identified test scenarios.
2. Perform selective Black-Box and White-Box testing covering Unit tests and Integration tests by
using suitable testing tools.
HARDWARE AND SOFTWARE
REQUIREMENTS
 Hardware Requirements :
 Personal Computer (PC)

 Software Requirements :
1. 32/64-bit Operating System.
2. Java
3. Junit 5
4. VS Code, Eclipse IDE
CONCEPT : TEST PLAN FOR
APPLICATION TESTING
The Test Plan document is derived from the Product Description, Software Requirement Specification SRS,
or Use Case Documents. The focus of the test is what to test, how to test, when to test, and who will test.
Test plan document is used as a communication medium between test team and test managers.
A standard test plan for Application Testing should define following features :
1. Define the scope of testing
2. Define objective of testing
3. Approach for testing activity
4. Schedule for testing
5. Bug tracking and reporting
UNIT TESTING

A unit test is a way of testing a unit - the smallest piece of code that can be logically isolated in a
system.
The purpose is to validate that each unit of the software performs as designed.
A unit is the smallest testable part of any software. It usually has one or a few inputs and usually a
single output.

Example : Submit button in a form is clickable and performs the desired action.
INTEGRATION TESTING

 Integration testing is the second level testing performed after unit testing in which we test the interfacing
between the modules along with the end-to-end testing of the integrated components.

 Why perform Integration testing?

1. A module may work perfectly in isolation but can have integration issues while interacting
with another module.
2. There can be data type or valid data range issues between the modules.
3. In large teams where the modules are created by different developers or even teams, it
becomes very necessary. As there can be a mismatch in the understanding of the different
developers.
BLACK-BOX TESTING

 Black-Box Testing, also known as Behavioral Testing, is a software testing method in

which the internal structure/design/implementation of the item being tested is not known to
the tester. These tests can be functional or non-functional, though usually functional.
 This method is named so because the software program, in the eyes of the tester, is like a
black box, inside which one cannot see. This method attempts to find errors in the
following categories:
1. Incorrect or missing functions
2. Interface errors
3. Errors in data structures or external database access
4. Behavior or performance errors
5. Initialization and termination errors
 Black-Box testing is generally done by Independent Software Testers.
WHITE-BOX TESTING

 White-Box Testing (also known as Clear Box Testing, Open Box Testing, Glass Box
Testing, Transparent Box Testing, Code-Based Testing or Structural Testing) is a software
testing method in which the internal Structure/Design/Implementation of the item being
tested is known to the tester.
 During White Box Testing, the tester chooses inputs to exercise paths through the code and
determines the appropriate outputs. Programming know-how and the implementation
knowledge is essential. White box testing is testing beyond the user interface and into the
nitty-gritty of a system. This method is named so because the software program, in the
eyes of the tester, is like a white/transparent box; inside which one clearly sees.
 White-Box testing is generally done by Software Developers.
APPLICATION TO BE TESTED

The application under test is a GUI based application developed in Java using the Junit
library.
The application is a Student Marks/Data Storage system. The Data collected by the
application is a Student’s name, age, gender and marks obtained.
SQLite database is used for storing the data.
The application has the following main functionalities :
1. Add a patient’s data.
2. Allot a room to patient.
3. Admin login page.
TEST PLAN

 The basic aim of performing these tests is to check if we get the correct and expected output for
each input and the test gets executed correctly.
 Initially, we store patients data in the system and check if the results are as expected.
 Then, we perform unit tests on individual components of our application such as validation of a
patient’s name (if it is a null value or not).
 Finally, we perform integration tests on the application where different components/modules of an
application combine to execute an operation.
 After conducting the tests, a test report is prepared consisting of successful and failed tests and
overall performance of tests.
IMPLEMENTATION
Graphical User Interface (GUI)
CONCLUSIONS

 Successfully performed unit and integration tests on a simple CRUD application

used to store student data.
 While performing unit tests. 2 out of 7 test cases failed, whereas 5 out of 7 test
cases passed.
 While performing integration tests. 1 out of 4 test cases failed, whereas 3 out of 4
test cases passed.