Chapter 7

Data Visualization
Software Testing:
It gathers all of the pieces in a dedicated testing area, where they are examined for bugs, pests,
and interactions. The process of testing software products is known as software testing. Effective
software testing will result in higher-quality software products, happier users, lower repair costs,
more accurate results, and more dependable results. Ineffective testing, on the other hand, will
result in low-quality items, dissatisfied users, growing storage costs, and unreliable and direct
outcomes. Testing is the most common method of quality control in software development. Its
primary purpose is to discover software flaws. It's an extremely expensive process, costing one-
third to one-half of the average development project. Testing is the process of creating a
programme (or a component of a programme) with the goal of discovering errors; nevertheless,
testing cannot verify the absence of faults, but it can indicate that errors do exist.

"Errors can be found in even the most thoroughly tested software."

This was not the purpose of the programme developers, who should have created the software
with the goal of generating it error-free. Software testing is becoming more critical in the early
stages of the software development life cycle, with the goal of detecting mistakes before they get
deeply established in systems. The earlier in the software's life cycle the first problems are
discovered and corrected, the lower the cost of correcting them. The most dangerous faults are
those that go undetected during testing and so continue once the system is turned on.

Testing requires the detection of faults in software by developers. It's quite tough for a software
developer to spot flaws in his work. A good test is one that has a high chance of uncovering an
undiscovered flaw. A successful test case uncovers an inaccuracy that was previously
undetectable. This means that the test will look for problems created not just during the coding
process, but also in preceding stages. The goal of the test is to find the required flaws, construct
the systems, and encrypt them.

White Box Testing:

The white box test is a form of software testing in which the tester is aware of the system internal
structure and implementation. The tester chooses the input for which the methods in the code
will be applied, and then determines the proper results. Information about the system and how it
is used is critical. From the end to the preceding amount, this is done and checked for each field
entry (Database). It is completed at the planning stage. There are necessary improvements made
to ensure that the modules in the system perform efficiently in terms of the expected module
departure.

All of the choices were thoroughly examined. The White Box exam is more user-friendly and
focuses on the system's details. This method is named after the software system's resemblance to
a white / visible box in the eyes of the tester; within which one can clearly see.
Black box Testing:
Black Box Testing is a type of software testing in which the functionalities of software
applications are tested without knowledge of the internal code structure, implementation details,
or internal routes. Black Box Testing is a type of software testing that focuses on the input and
output of software applications and is totally driven by software requirements and specifications.
Behavioral testing is another name for it.

The following categories of errors are targeted by this method:

1. Jobs that are invalid or missing

2. Data structure errors or external access to data
3. Errors in behaviour or performance

Unit Testing:
Unit testing is a type of software testing that examines specific software units or components.
The goal is to make sure that each software unit works as intended. The smallest component that
may be tested in any software is the unit. One or a few inputs are frequently present, with one
being the most common. The module is independently tested and is usually done at the same
time as the module coding in our team. The goal is to discover encoding issues by using various
parts of the module code. We test each table field and it works well according to unit intelligence
testing.

Integration Testing:
Individual modules are integrated and tested as a team during integration testing, which is a type
of software testing. The goal of this test level is to find communication issues between integrated
units. It's utilised in Integration testing to help with test drivers and test tubes. Modules are
gradually incorporated into subsurface systems, and finally the complete system is integrated.
Integration testing focuses on testing the links between our project elements in order to uncover
design problems.

System Testing:
System testing is a type of testing that verifies that a software product is complete and integrated.
The system test's goal is to determine the system's final state. Software is frequently only one
component of a larger computer-based application. The programme is finished once it has been
compiled. The system is reviewed based on its requirement to see if all of the requirements have
been met and if the system is performing as expected.

Test scenario:
Login Test Scenario:
Expected
Scenario Username Password Results
Outcome
Login Null Password Redirect to login Same
Ambiguous Null Redirect to login Same
Null Ambiguous Redirect to login Same
Correct Ambiguous Redirect to login Same
Ambiguous Correct Redirect to login Same
Redirect to
Correct Correct Same
Dashboard
Table: Test Case Login