Testing on ProMax

This document provides an overview of software testing on ProMax, including the different types of testing such as white box testing and black box testing. It also explores various scenarios and test cases for ProMax application pages. The document discusses the importance of testing in identifying defects and finding areas for modifications in software.

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

12TESTING ON PROMAX
is needed to be mentioned during filling up
the form. Apart from that the mobile phone
number is needed to be of 10 digits and the
email id is needed to be of the right format.
Status NA
Comments The dealer ID is not required for filling up the
form which is not a desirable attribute. Apart
from that, only the mobile number has to be
of 10 digits and the email id is needed to be in
right format. In case this situation, these two
columns can be considered as filter. However,
the wrong information can easily be provided
in this section maintaining the right format in
these two columns and there is a chance that
organization can receive the false
applications.
Component 2: Support
Scenario 4: Contact Dealer Technical Service
Test case ID P-5
Test Priority Medium

13TESTING ON PROMAX
Test Designed by Please insert name
Description of test To check if the dealer can contact the
organization for technical support after
entering the wrong data.
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 Dealer
Technical Service”
iv) It will redirect to a new page.
v) The form in the window is needed
to be filled with the information.
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 dealer ID will be asked and the mobile
number and email address should be in the
right format.

14TESTING ON PROMAX
Status NA
Comments One of the good feature that has been seen in
this section is that, this section is connected
with the “contact sales” section. The data
entered in the contact sales section are
automatically fetched in this section. This can
be regarded as user friendly feature of this
software. However, in this section also the
form can be submitted by giving the wrong
information.
Component 2: Support
Scenario 5: ProMax Support Team
Test case ID P-6
Test Priority Low
Test Designed by Please insert name
Description of test To check if the details of the support team can
be accessed with respect to different states.
Pre-condition The information is needed to be accurate.
Test steps i) Open the ProMax through the
mentioned browser.

15TESTING ON PROMAX
ii) Go to the “Support” tab.
iii) Go to the “ProMax support team”
iv) It will redirect to a new page with
a map of USA.
v) By clicking on the different states
the support team of that state can
be seen.
Test Data Email: [e-mail]
Dealer id: 45
Expected Result The relevant information regarding the
support team can be accessed.
Post-condition Any user can access the information
Status Pass
Comments The idea of representing the information
through the map is an innovative idea. Apart
from that all the information are relevant.
Timeline (Gnatt Chart)

16TESTING ON PROMAX
ID Task
Mode
Task Name Duration Start Finish
1 Testing of the Software8 days Mon 12-10-09Wed 21-10-09
2 Selection of the
software to be
tested
2 days Mon
12-10-09
Tue
13-10-09
3 Testing for the
Scenario 1
1 day Wed
14-10-09
Wed
14-10-09
4 Testing for the
Scenario 2
1 day Thu
15-10-09
Thu
15-10-09
5 Testing for the
Scenario 3
1 day Fri
16-10-09
Fri
16-10-09
6 Testing for the
Scenario 4
1 day Mon
19-10-09
Mon
19-10-09
7 Testing for the
Scenario 5
1 day Tue
20-10-09
Tue
20-10-09
8 Testing for the
Scenario 6
1 day Wed
21-10-09
Wed
21-10-09
9 Making proper
recommendatios
1 day Thu
22-10-09
Thu
22-10-09
10 Conclusion 1 day Thu 22-10-09Thu 22-10-09
F S S M T W T F S S M T W T F S
04 Oct '09 11 Oct '09 18 Oct '09
Recommendations on the effective use of this IT system:
It has been seen that the login has to be done with the help of the user name and dealer id.
The use of the dealer ID and the password for the login purpose is effective as it will prevent the
other people to access all the details regarding the dealership. However, it has been seen that in
some sections like scheduling for the seminars and the training do not need dealer ID. After
filling some of the general information, the user can successfully send the request for the
scheduling the training. However, it can be said that there will be chance many irrelevant
requests with the wrong information can be submitted through this section. It will increase the
overhead processing cost for the processing of the requests. In this case, it is recommended to
add more filter while feeling up the requests for the scheduling of the training sessions.
Plans on business continuity plan:

17TESTING ON PROMAX
The business continuity plans involves the analysis of the organizational threats. Apart
from that the list of the primary tasks for the further development of the website can be done
through this plan (Garousi and Felderer 2017). Apart from that backup of the data and the
relevant branching of all the information is needed to be done through the business continuity
plan. Through the business continuity plan the expansion of the business can be happened. In this
case, the role of the website can be significant.
Conclusion
The discussion is regarding the testing of the software. In this context, the white box
testing and the black box testing have been mentioned. In this context different tabs present in
the software is examined. The output of the test has been described for each of the test case. It
can be said that the software is robust and delivers the proper functionality. In some cases, the
software has shown some of the innovations and the user friendly feature of the software makes
the access easy. However, there is a need for certain improvisation of the ProMax software
needed. It has been seen in some cases, the forms can be submitted even after providing the
wrong information. It can be said that the proper modification and improvisation of the system
will enhance the functionality of the overall application.

18TESTING ON PROMAX
References
Cashman, M., Catlett, J.L., Cohen, M.B., Buan, N.R., Sakkaff, Z., Pierobon, M. and Kelley,
C.A., 2017, May. BioSIMP: using software testing techniques for sampling and inference in
biological organisms. In Proceedings of the 12th International Workshop on Software
Engineering for Science (pp. 2-8). IEEE Press.
Chopra, R., 2018. Software Testing: A Self-Teaching Introduction. Stylus Publishing, LLC.
de Oliveira Neto, F.G., Torkar, R. and Machado, P.D., 2015, May. An initiative to improve
reproducibility and empirical evaluation of software testing techniques. In 2015 IEEE/ACM 37th
IEEE International Conference on Software Engineering(Vol. 2, pp. 575-578). IEEE.
Garousi, V. and Felderer, M., 2017. Living in two different worlds: A comparison of industry
and academic focus areas in software testing. IEEE Software.
Garousi, V. and Mäntylä, M.V., 2016. A systematic literature review of literature reviews in
software testing. Information and Software Technology, 80, pp.195-216.
Garousi, V. and Mäntylä, M.V., 2016. When and what to automate in software testing? A multi-
vocal literature review. Information and Software Technology, 76, pp.92-117.
Garousi, V., Felderer, M., Karapıçak, Ç.M. and Yılmaz, U., 2018. What we know about testing
embedded software. IEEE Software, 35(4), pp.62-69.
Haller, I., 2017. adapting software testing techniques to enhance software security.
Jan, S.R., Shah, S.T.U., Johar, Z.U., Shah, Y. and Khan, F., 2016. An innovative approach to
investigate various software testing techniques and strategies. International Journal of Scientific
Research in Science, Engineering and Technology (IJSRSET), Print ISSN, pp.2395-1990.

19TESTING ON PROMAX
Khatri, S.K., Kaur, K. and Datta, R., 2019. Applying Statistical Usage Testing Along with White
Box Testing Techniques. In Software Engineering (pp. 457-475). Springer, Singapore.
Melo, S.M., Souza, P.S. and Souza, S.R., 2016, November. Towards an empirical study design
for concurrent software testing. In 2016 Fourth International Workshop on Software
Engineering for High Performance Computing in Computational Science and Engineering (SE-
HPCCSE) (pp. 49-49). IEEE.
Mishra, D.B., Mishra, R., Das, K.N. and Acharya, A.A., 2017. A systematic review of software
testing using evolutionary techniques. In Proceedings of Sixth International Conference on Soft
Computing for Problem Solving (pp. 174-184). Springer, Singapore.
Perrouin, G., Devroey, X. and Cordy, M., 2017, September. Testing Variability-Intensive
Systems. In Proceedings of the 21st International Systems and Software Product Line
Conference-Volume A (pp. 255-255). ACM.
Prabhakar, N., Singhal, A., Bansal, A. and Bhatia, V., 2019. A Literature Survey of Applications
of Meta-heuristic Techniques in Software Testing. In Software Engineering (pp. 497-505).
Springer, Singapore.
Rathi, M. and Jain, S., 2019. A Review on Software Testing Techniques. Available at SSRN
3372981.