Software Testing and Validation Report for ProMax Application

This report provides an overview of software testing methodologies applied to the ProMax application, a software solution for automotive dealerships. It discusses both white box and black box testing techniques, including unit testing, memory leak testing, functional testing, non-functional testing, and regression testing. The report focuses on several key components and scenarios within the ProMax application, such as dealer login, online training, and technical assistance contact forms. Test cases are presented for each scenario, detailing the test steps, expected results, and actual outcomes. The analysis identifies areas where the application's validation and error handling can be improved to prevent invalid data submission and enhance overall system reliability. The report concludes by highlighting the importance of thorough testing in ensuring the quality and security of software applications.

Running head: TESTING ON PROMAX
TESTING ON PROMAX
Name of the Student:
Name of the University:
Author Note:

1TESTING ON PROMAX
Overview
Software testing is done in order to identify the defects in the implemented software and
finding the scopes for modifications. Testing can be done using the testing software or manual
process. The main objective of the software testing is to identify the bugs in the system. Apart
from that testing is also done to understand the functionalities of the different modules in the
software (Rathi and Jain 2019). The testing can be done through the user’s end or it can be done
from the technical perspective by the software developer. The testing can be done in two ways.
Tools can be used for the testing purpose. Apart from that the manual testing can be done for
both white and the black box testing (Garousi et al. 2018). The white box testing is done in order
to understand the internal functionality of the software. Regarding this the evaluation and the
analysis of the .There are two types of testing- white box testing and black box testing. In this
context, the manual testing will be used.
Introduction
ProMax is a well-known name in the field of the automotive software for 20 years. The
organization offers complete solutions to the dealership. The main functioning of the
organization is to provide desktop and CRM modules (Prabhakar et al. 2019). Apart from that
the compliance and the prescreen products are also available through this organization. In order
to communicate with the consumers in a proper way, the organization has a website (Jan et al.
2016). Through this website, the deals along with the register consumers can connect with the
organization. There is a different login section for the users who are operating the website form
the mobile which is known as the ProMax mobile login (Perrouin, Devroey and Cordy 2017).
Apart from that there are ProMax dealer login and ProMax login for the users.

2TESTING ON PROMAX
Application pages
Dealer login (using Google Chrome)
Dealer login (Using specific browser)
Online training for dealership

3TESTING ON PROMAX
Contact to the technical service department:
Testing
Testing is the process through which the evaluation of the software can be done in a
proper way. Through the testing the analysis of the gap between the required system and the
existing system can be done (Chopra 2018). Apart from that the areas for the modifications can

4TESTING ON PROMAX
be identified through the system. There are two types of testing- white box testing and black box
testing.
In white box testing, the testing of the codes for the software system is required. On the
other hand in the black box testing, the end users tests the software through providing the inputs.
The main objective of the testing is to understand the errors and gaps along with finding
the missing requirements in the software (Mishra et al. 2017). Apart from that the detection o the
bugs those can be responsible for making the constraints during running of the software is also
detected through the testing.
White box testing:
White box testing are used in order to find the bugs and the inconsistency in the code
written for the software. It will indicate the gap between the existing code and the ideal code. In
order to do the white box testing, the knowledge of the coding is needed to be maintained (Khatri
et al. 2019). Apart from that the branch coverages are also examined through this testing
(Garousi and Mäntylä 2016). The main objective of the white box testing is to understand the
branch coverage of the codes and the evaluation of the condition statements used in the coding.
White box software testing can be considered as the low level testing (de Oliveira et al. 2015).
This testing is also known as glass box testing, clear box testing or transparent box testing. There
are different kinds of white box testing like unit testing, testing for memory leak.
Unit testing: This type of testing is done on the application. Unit testing is performed on
the unit or the block of the codes in the project. This type of testing is done by the programmer
or software developers (Garousi and Mäntylä 2016). It is the responsibility of the software
developer to continue the testing developing a few lines of codes or a single function. It has been

5TESTING ON PROMAX
seen that through the use of the unit testing the identification of the bugs in the software
application can be done at the early stage of the software development lifecycle.
Testing for memory leaks: The memory leaks can cause the slow running of the application. The
responsibility of the quality specialist is to detect the memory leaks for the selected cases.
Black box testing: The black box testing is done by the end users. In this case, test data
are provided to the end users (Cashman et al. 2017). Using those data the end users tests the
boundary of the functionality of thing. The comment regarding the each testing of the
components is done through the information provided to the users (Haller 2017). There are
different types of black box testing like regression testing. Boundary testing, functional testing,
non-functional testing.
Functional testing: The software tester will test the functional requirements of the
software application.
Non-functional testing: This type of testing is not related to the testing of a specific
functionality. However, nonfunctional requirements like performance, scalability, usability
Regression testing: This type of testing is done after fixing of the codes and the upgrade
of the system (Melo, Souza and Souza 2016). The main objective of running this code is to
check if the code is running in a proper way after the fixes.
Components and scenarios:
The scenarios are the test cases on which the testing is needed to be done. In this case, three
scenarios have been selected. The chosen software is ProMax. The three scenarios are- Dealer
login, online training for the dealership and filling up the form for the technical assistance.

6TESTING ON PROMAX
1. Login
2. Support
 Technical support
 Contact Dealer Technical Service
 Customer support
 Dealership training
Test cases
Component 1: Login
Scenario 1: User login without dealer id
Test case ID P_1
Test Priority High
Test Designed by Please insert name
Description of test To check whether a dealer can login with out
dealer ID
Pre-condition The dealer is not registered, hence, no valid
dealer ID , email address and password.
Test steps i) Open the web browse mentioned
ii) Go to the website of Promax
iii) Click on dealer login
iv) Enter the invalid details
Test Data [e-mail]
dealer id: 45

7TESTING ON PROMAX
password: 8976
Expected Result Page will reload showing “Authentication
failed”
Post-condition The login cannot be done by the dealer
Status Pass
Comments The page is reloading stating that the
authentication is failed in the session.
Component 2: Support
Scenario 1: Contact technical service department:
Test case ID P-2
Test Priority Medium
Test Designed by Please insert name
Description of test To check if the technical service department
can be contacted without using the dealership
ID
Pre-condition The dealer has no valid e-mail and the dealer
ID as the dealer is not registered.
Test steps i) Open ProMax through the
mentioned browser.
ii) Go to “Support: tab.
iii) Choose “Technical Support”

8TESTING ON PROMAX
iv) Choose “Contact Dealer Technical
Services”
Test Data Email: [e-mail]
Dealer id: 45
Expected Result The data will be not accepted as all the data
are invalid.
Post-condition The data is accepted even it is wrong. In the
next page it is showing “ Thank you For Your
Request”
Status NA
Comments While giving the invalid dealer ID as input
and the system should detect that the ID and
the phone number is not valid. However, it is
accepting the data and redirected to the new
page. This increase the invalid requests to the
system of the organization which is not
desirable.
Component 2: Support
Scenario 2: Online training of the dealers.
Test case ID P-3
Test Priority Medium
Test Designed by Please insert name

9TESTING ON PROMAX
Description of test To check whether the online dealership
training can be conducted without a valid
dealer ID.
Pre-condition There is no valid dealer ID and the registered
phone number as the dealer is not valid.
Test steps i) Open the ProMax through the
mentioned browser.
ii) Go to the “Support” tab.
iii) Go to the “Customer Service”
iv) Go to dealership training.
v) Go to the “Online training”
vi) It will redirect to a new page.
From there selection for the
particular training is needed to be
done.
vii) After the selection of the training
from the options,
Test Data Email: [e-mail]
Dealer id: 45
Expected Result With invalid and irrelevant data the
registration will not be completed. Apart from
that, the deal ID will be asked as the part of
the registration.

10TESTING ON PROMAX
Post-condition The first name , last name and the email
address is needed to be registered. Apart from
that, if the invalid data is entered the page is
accepting the data and the message is showing
that “ You are registered”.
Status NA
Comments The dealer ID should be included in the
section. There is a chance that the users can
enter invalid data. In that case, the false
request forms will be generated from the
organization’s side which is not acceptable.
Apart from that there is no way for the
verification of the data entered by the users.
Component 2: Support
Scenario 3: Contact Sales
Test case ID P-4
Test Priority Medium
Test Designed by Please insert name
Description of test To check if the consumers and the dealers can
contact the organization after inserting right
data.

11TESTING ON PROMAX
Pre-condition There is no valid dealer ID and the registered
phone number as the dealer is not valid.
Test steps i) Open the ProMax through the
mentioned browser.
ii) Go to the “Support” tab.
iii) Go to the “Contact Sales”
iv) It will redirect to a new page. In
this page the details are needed to
be provided by the users so that
the organization can make contact
with them.
v) The selection of the category is
needed to be done from the section
“Product or Service You are
interested in”
Test Data Email: [e-mail]
Dealer id: 45
Expected Result With invalid and irrelevant data the
registration will not be completed. Apart from
that, the deal ID will be asked as the part of
the registration.
Post-condition The job position and the name of the service