Test Case Identifier: TC-01

Use Case Tested: UC-01

Pass/Fill Criteria: The test will pass if the user is able to successfully log in to the system. The test
will fail if the user inputs an invalid username or password.

Input Data: username, password.

Test Procedure Expected Result

Step 1: User types in an invalid Database server denied the log-in attempt. Message
username and/or password. pops up, instructing the user to try again using a
valid log-in.
Step-2: User types in a valid Database Server allows the log-in attempt.
username and password. Depending on the user type, the system allows the
user to access the specified
interface.

Test Case Identifier: TC-02

Use Case Tested: UC-01

Pass/Fill Criteria: The test will pass if the user is able to successfully view the profile system. The test
will fail if the user is unable to access their profile.
Input Data: request to access profile data from database server.
Test Procedure Expected Result

Step-1: The user will tap the profile button.
Step-2: User doesn’t select any
Button.
They are able to see their own database from the
database server where they input their own
information.
They are able to see the home page for each
category’s user.
 Test Case Identifier:TC-03

Use Case Tested: UC-02

Pass/Fill Criteria: This test will pass if the user puts a valid name of writer and book into the program
and it is recognized as a correct format and accepted if it is stored in database otherwise it will be
rejected.

Input Data: Books name, Writer’s name.

Test Procedure Expected Result

Step-1: Type in incorrect format for books name If the book name and the writers name match
then it will bring information like category,
Step-2: Type in correct format for writer’s name quantity and price from database.

Test Case Identifier: TC-04

Use Case Tested: UC-03

Pass/Fill Criteria: This test will pass the order function if the user puts a valid name of writer, book,
customer, contact, district and email into the program and it is recognized as a correct format and
accepted if it is stored in database otherwise it will be rejected.

Input Data: Books name, Writer’s name, customers name, contact, district, e-mail.

Test Procedure Expected Result

Step-1: Type in incorrect format for name If the book name and the writers name match
Of all Books name, Writer’s name, customers then it can be ordered by the given name,
name, contact, district, e-mail contact, e-mail.
Step-2: Type in correct format for all Books
name, Writer’s name, customers name, contact,
district, e-mail
Test Case Identifier:TC-05

Use Case Tested: UC-01

Pass/Fill Criteria: The test will pass if the owner is able to successfully log in to the system. The test
will fail if the user inputs an invalid username or password

Input Data: username, password

Test Procedure Expected Result

Step 1: owner types in an invalid Database server denied the log-in attempt.
username and/or password. Message pops up,
Step-2: owner types in a valid instructing the user to try again using a valid log-
username and password. in.
Database Server allows the log-in attempt.
Depending on the
user type, the system allows the user to access the
specified
interface.

Test Case Identifier: TC-06

Use Case Tested: UC-07

Pass/Fill Criteria: The test will pass if the owner is able to add successfully add manager/s to the
system

Input Data: username, password

Test Procedure Expected Result

Step-1:.Type in incorrect format for managers
name and password from managers list
Step-2: Type in correct format for managers name
and password from managers list
If the managers name matches then it will add
manager function in case of adding. And can
delete manager in case of deletion if
managers name matches with database.

Test Case Identifier: TC-07

 Use Case Tested: UC-05

Pass/Fill Criteria: The test will pass if the manager is able to add/ delete books successfully

Input Data: username, password

Test Procedure Expected Result

Step-1: Type in incorrect format for books name If the book name and the writers name match
with the database then it will be able to add or
Step-2: Type in correct format for writer’s name delete or update books by manager’s profile.

Test Case Identifier: TC-08

Use Case Tested: UC-08

Pass/Fill Criteria: The test will pass if the owner is able to delete successfully manager/s to the
system

Input Data: username, password

Test Procedure Expected Result

Step-1: Type in incorrect format for managers If the managers name matches then it will
name and password from managers list delete manager in case of deletion.
Step-2: Type in correct format for managers
name and password from managers list

8.2 Test Coverage

We already did some testing in our system which does not clarify that our system is 100% bug
free. Every system has some barriers. This one has some when we use this system. We will
know how much error the system has. All of our test cases include all of the classes that are
required for Turbo Yums to function properly. We'll continue to add and change test cases as
we build more of our classes and functions. Test coverage is the process we use to determine
whether we’re testing everything we’re supposed to test. It allows us to check the quality of our
testing. By finding areas that aren’t currently covered, test coverage helps us to develop tests
for those areas, increasing the overall quality of your test suite. In response to a user input, the
test processes for the classes will have a pass/fail structure. If a user input error causes the
test to fail, the system will prompt the user to try again and rectify the error. Testing the login
screen, where the user enters their username and/or password, is an example of a test. If the
user enters their password incorrectly, the system will prompt them to enter their information
again. This failure instance will keep repeating itself until the user gives up. After the person has
entered their right information, they will be able to login. We aim our software to be as effective
as possible with no mistakes, therefore we 'll have test cases to demonstrate that Hybrid Library
is functional and has been extensively tested.

8.3 Integration
Integration testing is the second level of the software testing process comes after unit testing.
In this testing, units or individual components of the software are tested in a group. The focus
of the integration testing level is to expose defects at the time of interaction between integrated
components or units. Unit testing uses modules for testing purpose, and these modules are
combined and tested in integration testing. The Software is developed with a number of
software modules that are coded by different coders or programmers. The goal of integration
testing is to check the correctness of communication among all the modules. After unit testing,
integration testing is the next step in the software testing process. Units or individual
components of the software are tested in a group during this testing. The integration testing
level focuses on exposing flaws that occur during the interaction of integrated components or
units. Modules are added one by one in ascending sequence or according to necessity in the
Incremental Approach. The modules chosen must be logically connected. To determine the
accuracy of functions, two or more modules are usually introduced and checked. The procedure
is repeated until all of the modules have been successfully tested. We are using our project
hybrid method or sandwich. Both Top-Down and Bottom-Up techniques are integrated for
testing in this strategy. Top-level modules are tested alongside lower-level modules, and lower-
level modules are tested alongside higher-level modules in this process. Because each module
interface is checked, there is a lower chance of a problem. Understanding the relationships
between the models in the system allows us to make better decisions. The hybrid method
combines the benefits of both the bottom-up and top-down approaches. It is the approach that
will help us to save the most time. It allows for comprehensive testing of all modules.