PANGASINAN STATE UNIVERSITY BS COMPUTER ENGINEERING

CpE116 Software Design Laboratory Report No. 09

LABORATORY REPORT NO. 09

Testing and Validation of Software Design

OVERVIEW

The objective of this laboratory session is to explore the principles and techniques for
testing and validating software designs. Testing and validation play a crucial role in software
development as they ensure that the software meets the desired requirements, functions
correctly, and behaves as expected. In this lab, we will delve into the key concepts,
methodologies, and tools for effectively testing and validating software designs, with a focus
on ensuring quality and reliability.

OBJECTIVES

• Understand the importance of testing and validation in software development.

• Explore various testing methodologies and techniques.
• Gain practical experience in designing and implementing test cases.
• Analyze the impact of testing and validation on software quality and reliability.

ABSTRACT

The majority of the technical work in the software development process is spent on
software testing. Regardless of the kind of software you create a strategy for systematic test
planning, execution, and control starts by taking into account the smallest details of the
program and works its way up to the entire thing. The strategy for testing object-oriented
software begins with tests that exercise the operations within a class and then moves to
thread-based testing for integration. A group of classes called a thread reacts to an event or
input. Use-based tests concentrate on classes that do not interact with other classes
frequently.

Hetzel [Het84] defines white-box testing as "testing in the small," by which he means
that the white-box tests that have been discussed in this chapter are frequently used to test
small software components (such as modules or small groups of modules). Comparatively,
black-box testing broadens your perspective and is sometimes referred to as "testing in the
large."

PANGASINAN STATE UNIVERSITY 1

PANGASINAN STATE UNIVERSITY BS COMPUTER ENGINEERING

CpE116 Software Design Laboratory Report No. 09

Finding the most errors with the least amount of effort is the overarching goal of object-
oriented testing, which is the same as the goal of traditional software testing. However, there
are considerable differences in OO testing strategy and tactics. The assessment of the
requirements and the design model is now viewed as part of testing. Furthermore, the
emphasis of testing shifts from the procedural element (the module) to the class. Testing (in
the form of technical reviews) starts while the modeling activity is still in progress since the
OO requirements and design models and the generated source code are semantically
connected. For this reason, it is possible to think of the evaluation of the CRC, object-
relationship, and object behavior models as the initial stage of testing.

Each quality factor is exercised in the WebApp testing strategy by first reviewing
"units" of content, functionality, or navigation. After individual units have been validated, the
emphasis moves to tests that put the WebApp through its paces. Many tests are derived from
the user's perspective and are driven by information provided in use cases to do this. A
WebApp test plan is created, which includes testing steps, work deliverables (such as test
cases), and techniques for evaluating test results. There are seven main types of testing in
the testing process.

DISCUSSION

Software testing has typically been separated from the rest of the development
process. It is frequently carried out later in the software development life cycle, after the
product build or execution stage. A tester may only have a short window to test the code,
sometimes shortly before the application is released to the public. If problems are discovered,
there may be minimal time for recoding or retesting. It is not uncommon for software to be
released on schedule but with bugs and repairs required. Or a testing team may fix issues
yet miss a release date. A good testing approach encompasses the application programming
interface (API), user interface and system levels. Also, the more tests that are automated,
and run early, the better. Testing can be time-consuming. Manual or ad hoc testing may
suffice for minor builds. However, tools are routinely employed to automate work in larger
systems. Automated testing assists teams in implementing various scenarios, testing
differentiators (such as shifting components into a cloud environment), and fast receiving
feedback on what works and what doesn't.

PANGASINAN STATE UNIVERSITY 2

PANGASINAN STATE UNIVERSITY BS COMPUTER ENGINEERING

CpE116 Software Design Laboratory Report No. 09

Unit testing begins at the vortex of the spiral and concentrates on each unit (e.g.,
component, class, or WebApp content object) of the software as implemented in source code.
Testing progresses by moving outward along the spiral to integration testing, where the focus
is on design and the construction of the software architecture. Taking another turn outward
on the spiral, you encounter validation testing, where requirements established as part of
requirements modeling are validated against the software that has been constructed. Finally,
you arrive at system testing, where the software and other system elements are tested as a
whole. To test computer software, you spiral out in a clockwise direction along streamlines
that broaden the scope of testing with each turn.

We have developed this unit testing for the design of our project by means of using
the White Box Testing, this technique is used in testing the functional behavior of the system
by giving the input and checking the functionality output including the internal design
structure and code of the modules. Develop a testing plan that emphasizes “rapid cycle
testing.” Gilb [Gil95] recommends that a software team “learn to test in rapid cycles (2 percent
of project effort) of customer-useful, at least field ‘trialable,’ increments of functionality and/or
quality improvement.” The feedback generated from these rapid cycle tests can be used to
control quality levels and the corresponding test strategies.

White Box Testing is a software examining technique that involves testing the
product's underlying structure, design, and coding in order to verify input-output flow and
improve design, usability, and security. White box testing is also known as Clear box testing,
Open box testing, transparent box testing, Code-based testing, and Glass box testing since
the code is visible to the testers.

PANGASINAN STATE UNIVERSITY 3

PANGASINAN STATE UNIVERSITY BS COMPUTER ENGINEERING

CpE116 Software Design Laboratory Report No. 09

White box testing in software engineering aims to make sure that all decision
branches, loops, and statements in the code are correct. White Box test cases would be used
to put the statements in the preceding white box testing example to the test.

CONCLUSION

To sum up, designing and implementing these test cases and validating
designs plays a bigger role in order to uncover errors of the software. Experienced software
developers often say, “Testing never ends, it just gets transferred from you [the software
engineer] to your customer. Every time your customer uses the program, a test is being
conducted.”

And also, with the help of applying test-case design, you can achieve more complete
testing and thereby uncover and correct the highest number of errors before the “customer’s
tests” begin. These tests are then conducted to uncover errors associated with each possible
configuration. Testing focuses on content, function, structure, usability, navigability,
performance, compatibility, interoperability, capacity, and security.

PANGASINAN STATE UNIVERSITY 4

PANGASINAN STATE UNIVERSITY BS COMPUTER ENGINEERING

CpE116 Software Design Laboratory Report No. 09

REFERENCES

Pressman, R. S. (2010c). Software Engineering: A Practitioner’s Approach. McGraw-

Hill Science, Engineering & Mathematics.

GeeksforGeeks. (2023). Unit Testing Software Testing. GeeksforGeeks.

https://www.geeksforgeeks.org/unit-testing-software-testing/

PANGASINAN STATE UNIVERSITY 5