Scribd
Upload
10 views4 pages

Chapter 5

Chapter 5 discusses the software testing process within the Software Development Life Cycle (SDLC), emphasizing the importance of ensuring software meets its purpose and usability. It covers three types of testing: Unit Testing, Integration Testing, and User Acceptance Testing (UAT), detailing test cases and expected outcomes for each. The chapter highlights the systematic approach to identifying defects and validating functionality through various testing stages.

Uploaded by

aveshgopal Jonnadula
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
10 views4 pages

Chapter 5

Chapter 5 discusses the software testing process within the Software Development Life Cycle (SDLC), emphasizing the importance of ensuring software meets its purpose and usability. It covers three types of testing: Unit Testing, Integration Testing, and User Acceptance Testing (UAT), detailing test cases and expected outcomes for each. The chapter highlights the systematic approach to identifying defects and validating functionality through various testing stages.

Uploaded by

aveshgopal Jonnadula
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

CHAPTER 5

TESTING

41
5. TESTING
As software testing is within SDLC, defects in the program do not get ignored.
Your main aim is to make certain the software fulfil’s its purpose, looks
professional and can be used easily. Testing happens at distinctive moments,
matched to each part of the software.

5.1 Unit Testing

Each portion or module here is evaluated separately using unit tests. We are
checking whether each unit is constructed according to the design’s specifications.
Most of the time, they are functions, methods or classes. Many developers run unit
tests automatically as a regular part of what they do.

Test Expected
Module Description Input Result
Case ID Output

Username: Redirect to
Valid login
TC_U1 Login admin, admin Pass
credentials
Pwd:12345 dashboard
Username:
Show error
TC_U2 Login Invalid password admin, Pass
message
Pwd:wrong
Show
Missing required Name = '',
TC_U3 Registration validation Pass
fields Email = valid
error
Entering
Attendance Student ID = Attendance
TC_U4 attendance for a Pass
Entry 1002, Present marked
student
Adding a new
Course Code = Course saved
TC_U5 Add Course course with all Pass
CS101 in database
fields

Table 5.1.1 Unit testing

42
5.2 Integration Testing

The thought is that the software you’ve tested successfully can function together
with other application areas. We want to ensure our technology is working well and
our data can be shared easily. Most commonly, organizations are run following the
top-down style, from the bottom-up or with both styles combined.

Test cases for Integration Testing

Test
Modules Expected
Case Description Input Result
Involved Output
ID

Test role-based Student


Login → Login as
TC_I1 dashboard dashboard Pass
Dashboard student
access displayed

Ensure Student
Student Reg
registered Register new shown in
TC_I2 → DB → Pass
student reflects student admin's
Admin View
in admin panel student list

Check
Present status
Attendance → attendance Mark
TC_I3 shown in Pass
Reports reflects in attendance
report
reports

Math101
Course Assign Faculty sees Assign
listed on
TC_I4 → Faculty only assigned "Math101" to Pass
faculty
Panel courses Prof. A
dashboard

Result Entry Enter result and Input: Marks shown


TC_I5 → Student check student Student ID, in student Pass
View report card Marks report section

Table 5.2.1 Integration Testing

43
5.3 User Acceptance Testing

At the end of the testing process, UAT is carried out by users or stakeholders to
check if the software both matches their needs and functions properly in real use
cases. The goal of UAT is to verify that the system can be used in real work settings.
A lot of times, the entire system is tested using data that reflects real situations.

Test Case
Role Scenario Description Expected Behavior Status
ID

View daily attendance Summary report displays


TC_UAT1 Admin Pass
summary class-wise stats

Marks are saved and


TC_UAT2 Faculty Enter student marks Pass
shown in student view

View own timetable Displayed properly with


TC_UAT3 Student Pass
and course list days and times

Submit feedback for a Feedback saved and seen


TC_UAT4 Student Pass
faculty by admin

Export student list to CSV/Excel file generated


TC_UAT5 Admin Pass
Excel for download

Test cases for Running User Acceptance Testing

Table 5.3.1 User Acceptance Testing

44

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy