Unit Testing for Universal Project: Risks, Issues, and Mitigation Strategies

This article discusses the risks and issues involved in unit testing for Universal Project, a project management tool for risk management and project execution. It also provides mitigation strategies for each issue.

Running head: PROJECT MANAGEMENT
PROJECT MANAGEMENT
Name of the Student
Name of the University
Author Note

1
PROJECT MANAGEMENT
Unit Testing
Unit testing refers to the testing of different components of software design before all the
components are integrated to develop the actual and final software to deliver to the clients.
Here the focus is to find the issues in the components rather than actual functionality of the
system.
Here in this context the software that will be tested is ‘Universal Project’, a project
management toll for risk management and project execution
Test Risks / Issues
In this sections the risk issues regarding the testing of the ‘Universal Project’ has been
discussed
Testing Impact Mitigation strategy Contingency
planning
Schedule for testing is
not adequate
It becomes difficult to
identify problem with
the ‘Universal Project’
software as test is not
done as per schedule.
Hence testing is not
proper
Effective
management to
ensure development
and testing is
executed side by
side
Start testing in
advance so problems
are easier to identify
and rectify

2
PROJECT MANAGEMENT
Environment and
tools are not sufficient
for testing of
‘Universal Project’
Software testing is poor Arrangement for
proper tolls and
testing environment
Prior evaluation of
testing environment
and tools by expert
Poor integration of
testing with
engineering processes
put forward for
‘Universal Project’
Components of
‘Universal Project’ are
tested even before they
are compatible for
testing. Hence provides
false implication about
testing and the system
Insists testing team
to review
extensively about
the maturity of the
components so that
the components are
tested accordingly
Create proper
schedule with
reference to actual
timeframe of the
project so that cross
verification of test
result is possible
without delay in the
actual project
Mindset for the
testing is not proper
Emphasis is put on the
system functionality of
‘Universal Project’
rather than the effort
put forward for
identifying the fault in
the system which results
in poor testing and
inefficient software
development
Team leader has to
make sure that the
purpose of the
testing is to find the
faults in the system,
not how it should
work
Other than the actual
tem leader someone
else should be
identified within the
team itself who
would be able to
take responsibility
of the team leader if
required

3
PROJECT MANAGEMENT
Items to be Tested / Not Tested
The items that will be tested for the ‘Universal Project’ has been explained along with test
date and test description
Item to Test Test Description Test Date Responsibility
Initial setup time It will test what is the initial setup
time for the ‘Universal Project’
software along with loading time
across different platform and
devices
29/11/2018 System
designer
Interface of the system It will review the interface through
which user will interact
30/11/2018 User interface
designer
Features offered and
what was actually asked
for
It will test if the software offers
the features as asked by the
customer. This will particularly
look for how easily the budget are
created, how efficient the schedule
management feature is like how
easy it is to create as well track
schedule for effective project
execution
1/12/2018 Team leader
and manager
Security of the system It will test what is the level of
authentication the software offers
2/12/2018 System
architect

4
PROJECT MANAGEMENT
Test Pass / Fail Criteria
Item to Test Pass criteria
Initial setup time Should be low as much as possible and uniform across
different platforms
Interface of the system Should be intuitive and as per the requirement
Features offered and what was actually
asked for
Should exactly match
Security of the system Provide security with proper authentication
Test Deliverables
After the test is conducted a test summary report is generated in the form of chart including
the test result.

5
PROJECT MANAGEMENT
initial setup time
interface
features offered
security and
authentication
0% 2% 4% 6% 8% 10% 12%
defects imapct and status
Testing summary report for ‘Universal Project’:
Test id Test objective Step Result
TC_MI_01 Successful login
to the system
1. Provide
login
Speed was slow and
authentication was not also proper
initial setup time interface features offered security and
authentication
0%
2%
4%
6%
8%
10%
12%
defect distribution module wise

6
PROJECT MANAGEMENT
details
2. Enter login
button
as in one or two instances it
allows to login to the system
with wrong login details
TC_MI_02 Creation of
Budget
1. Provide
information
about
resource
2. Allocate
cost per
resource
Performed well during testing, but
some time budget dos not
synchronizes with no of resources
TC_MI_03 Effective
resource
planning
1. Enter
resource
details,
2. set
schedule
and assign
time frame
for each
resources
Performed well during testing as
resource planning was easy and
effective with the software
TC_MI_04 Project tracking
with individual
tracking for each
and every tasks
Enter project
details,
project schedule
Does not show clearly which task
has been completed and which
has been not. Process is not
intuitive
TC_MI_05 Successful setup
and
Install and run the
software across
perfomed well on windows
OS,and MAC OS but ram

7
PROJECT MANAGEMENT
compatibility
across different
platforms
different OS management of the software is
not optimized on Chrome OS