Software Testing and Debugging Report: Parking Garage Automated System

This report focuses on software testing and debugging, specifically addressing the "Parking Garage Automated System." The report details the process of testing the system, including the registration page, login page, homepage, reservation page, and add vehicle module. It highlights various issues encountered during testing, such as validation problems, password reset issues, and interface design concerns. The report also outlines the importance of acceptance testing before deployment and emphasizes the need for error correction to ensure a secure and functional application. Furthermore, the assignment brief required testing of a Software Requirements Specification (SRS) document, development of test scenarios, and review using an inspection checklist. The provided solution includes a summary of the testing results and test scenarios for acceptance testing based on the functional requirements of the system.

Running Head: SOFTWARE TESTING 1
Software Testing and Debugging
Affiliate Institution
Student
Date

Running Head: SOFTWARE TESTING 2
Introduction
Software Testing and debugging is the process in which the application is tested and any form of
a bug present in the system will be cleaned. This gives the system to be genuine and unnecessary
errors which might be caused by the system functionality will be removed. Every software that
has been developed will required to be tested before deploying for first use by the clients.
The purpose of the Report
This report provides an assurance to the customers that the application developed is out of errors
and is secured to use. Every part of the application is being examined so that minor errors can be
obtained and corrected. Errors which may be present in the system can be field validations and
performance system errors.
System Acceptance Testing
The system was tested for its acceptance before it was deployed for first use by the clients. The
application is a packing system that is supposed to allow customers to logging to the system
using the correct credentials such as passwords and the correct email address. The name of the
tested project is, “parking garage automated system.”
The following are some of the test cases which were carried out in the testing process where each
of the modules were screened to check whether they contain bugs or not;
a) Registration page
From the registration there are quite a number of issues which had to be checked while the
system is being deployed for use. In this regard all the fields were checked and validation was
also checked. Validation includes the system user integrity in which every field that was

Running Head: SOFTWARE TESTING 3
provided does not need to be null and void. Some fields such as the email field will require a
valid email address and does not accept any other text apart from the correct email address.
Also the field must be able to understand some features such as matching the passwords with the
original one so as to allow the customer to register. Having trouble matching of the passwords in
the passwords fields provided will lead to a failure in the registration of the customer.
b) Login Page
When the customer is logging into the system, he or she must provide the correct credentials.
The user must be able to login to the system using the email address and the password.
Therefore, email validation is important. However, the system is having an issue with the
logging in in the case of the user forgetting his or her password. Therefore, the programmer will
have to adjust this issue so that a reset password button is added and can allow the user to reset
the password using the email address link.
c) Homepage
On the homepage of the system application is having some minor issues such as not showing the
links that leads to the parking load. The application needs to be self-guiding and should allow the
user to access all the available parking lots in orders to help the customers to identify the sites
that are near in wherever they are. Also, it is supposed to show an interface as a list of places
together with the prices such that new users can peruse all the parking lots and are prompt to
register before booking.
d) Reservation Page

Running Head: SOFTWARE TESTING 4
The reservation is set to show up a pop up calendar which is making the system to look too much
wordy. This is at all not pleasing to the customers as it causes the web application to become too
much shroud.
Reservation should also allow only admins to perform editing after the confirmation by the
client. This is because for integrity purposes, once the user has register and book the parking one
can only dispute it but not allowed to cancel the parking lot.
The customer can also be allowed to make the bookings and update it at any time he or she
wants. Since the application is online, updates can only be allowed to be performed on some
system features such as extending the dates of reservations and will require an approval by the
admin.
e) Add Vehicle
This module of adding a vehicle will have to apply to the site of the customer such that the
requirements include the plate number. This means that the user can make up to more than one
parking. This idea seems not to have been considered in the system under a single user. This may
bring an error when it comes to the payments made by the owner.
References