Test Plan v1 PMIS Agile

Philippine Council for Industry, Energy, and Test Plan for Agile testing of
Emerging Technology Research and Project Management Information System v4.0

Development - PCIEERD Phase 1
Test Plan
for
Agile Testing
of
Project Management
Information System v4.0
Version 1.0
Phase 1
Prepared by Rodelyn G. Lobo
March 06, 2020

Philippine Council for Industry, Energy, and Test Plan for Agile Testing of
Revision History
Name Date Reason for Changes Version
PMIS v4.0 Phase 1 – Test Plan

Page ii Version 1.0
Table of Contents
Revision History ............................................................................................................................ ii
Table of Contents ......................................................................................................................... iii
1. INTRODUCTION ................................................................................................................... 1
1.1 Purpose....................................................................................................................................... 2
1.2 Project Overview ........................................................................................................................ 2
1.3 Audience .................................................................................................................................... 3
2. TEAM ROSTER ..................................................................................................................... 4
2.1 Role Expectations....................................................................................................................... 5
2.2 IT Management Unit Head ......................................................................................................... 5
2.3 Information Systems Analyst – QA............................................................................................ 5
2.4 Development Team .................................................................................................................... 5
3. TEST STRATEGY .................................................................................................................. 6
3.1 Test Objective ............................................................................................................................ 7
3.2 Test Assumptions ....................................................................................................................... 7
3.3 Test Principles ............................................................................................................................ 8
3.4 Data Approach ........................................................................................................................... 8
3.5 Scopes and Levels of Testing ..................................................................................................... 9
3.5.1 Functional Testing ................................................................................................................. 9
3.5.2 Regression Testing ............................................................................................................... 10
3.5.3 User Acceptance Testing ..................................................................................................... 10
3.5.4 Security Testing ................................................................................................................... 11
3.6 Test Effort Estimate ................................................................................................................. 12
4. EXECUTION STRATEGY .................................................................................................. 13
4.1 Entry and Exit Criteria ............................................................................................................. 14
4.2 Test Cycles ............................................................................................................................... 15
4.3 Validation and Defect Management ......................................................................................... 15
4.4 Defect Tracking and Reporting ................................................................................................ 15
5. TEST MANAGEMENT PROCESS .................................................................................... 18
5.1 Test Management Tools ........................................................................................................... 19
5.2 Test Design Process ................................................................................................................. 19
5.3 Test Execution Process............................................................................................................. 20
5.4 Test Risks and Mitigation Process............................................................................................ 20
6. TEST ENVIRONMENT ....................................................................................................... 21
7. APPROVALS ........................................................................................................................ 22
8. References .............................................................................................................................. 23
9. OTHER REQUIREMENTS ................................................................................................. 24
Appendix A: List of Test Cases for Project Management role .............................................................. 25
Appendix B: List of Test Cases for Project Leader role ....................................................................... 26
Appendix C: List of Test Cases for FAD role ....................................................................................... 27
Appendix D: List of Test Cases for Admin role ................................................................................... 28
Appendix E: List of Test Cases for Super Admin role .......................................................................... 29

Page iii Version 1.0
1. INTRODUCTION

Page 1 Version 1.0
1.1 Purpose
The purpose of this Test Plan is to define the approaches and the testing methodologies to be
used in order to demonstrate the functionality of Project Management Information System
(PMIS) v4.0 in an Agile environment.
This is also for the purpose of detecting early defects or bugs as well as its severity that could
affect the operation of the said system.
1.2 Project Overview
The Information Technology Management Unit (ITMU) of Philippine Council for Industry,
Energy, and Emerging technology Research and Development (PCIEERD) council developed a
Project Management Information System (PMIS) v4.0 as part of the innovation of the existing
PMIS.
Project Management Information System (PMIS) is a web-based application system which aims
to automate the monitoring and evaluation process of research and development (R&D) projects
funded by the said council. The system also enables the project managers of PCIEERD to track
the status of research and development (R&D) proposals and projects submitted online or
personal.
Currently, PMIS has over five thousand proposals and more than one thousand projects been
monitored and evaluated.
The enhancement of the existing PMIS to PMIS v4.0 comprises of the following objectives:
• To improve the User Interface to more user-friendly environment
• To progress the financial monitoring functionality
• To grant project leaders or proponents the accessibility to their research and development
(R&D) proposals and projects.
The PMIS v4.0 is composed of 5 different roles namely: Project Managers, Project leaders, FAD
(Finance and Accounting Division), Admin, and Super Admin.
This application is available to all employees of PCIEERD and project leaders or proponents,
anytime, anywhere provided that the they have an existing PMIS account.
PMIS v4.0 should be ready for deployment once goals/objectives are achieved and able to pass a
series of test methodologies as defined on this document.

Page 2 Version 1.0
1.3 Audience
• Project Managers are PCIEERD employees who will monitor and evaluate research and
development (R&D) projects.
• Project Leaders or proponents, the owner of research and development (R&D) proposals
and projects.
• FAD/Finance and Accounting Division responsible for financial monitoring
• Admin has the capability to access modules except managing users, modules, roles and
permissions.
• Super Admin has the capability to access all modules in PMIS v4.0 including the
settings, user logs, permissions, etc.
• IT Management Unit Head plans the project schedule, reviews and approves testing
documents, and is responsible for overall outcome of the project.
• Information Systems Analyst – QA prepares testing materials and user manuals,

preforms testing methodologies, reports defects and bugs found in the system.
• Development Team responsible for the development of PMIS v4.0, responsible for
receiving and fixing issues reported by ISA-QA

Page 3 Version 1.0
2. TEAM ROSTER

Page 4 Version 1.0
2.1 Role Expectations
Roles Name Contact Information
1 IT Management Unit Head George Monroyo 837 2071 loc 2107

Maria Hershey Castro
Jhon Zylvin Ramos
2 Development Team John Keishner Romero 837 2071 loc 2107
Information Systems
3 Analyst – QA (ISA-QA) Rodelyn Lobo 837 2071 loc 2107
2.2 IT Management Unit Head

• Facilitates scrum for updates from development team and ISA-QA
• Schedules weekly deliverables for the team
• Reviews and approves test cases, test plan and related documentations
• Point of contact for Project Managers, Project leaders, FAD, Admin and Super Admin
roles
2.3 Information Systems Analyst – QA

• Responsible in creating and updating test cases and test plan for PMIS v4.0
• Responsible in making sure that no major defects or issues after each level of testing
• Ensure that the exit criteria are being followed
• Communicate with IT Management Unit Head and Development team for all the
changes need to be made.
• Responsible in performing re-testing and regression testing in the system after updates
by development team
• Provide list of bugs to developer team including failed test cases for reference
2.4 Development Team

• Responsible in coding and fixing reported bugs
• Provide list of available fixes or updates of the functionalities that could be tested to the
IT Management Unit Head.
• Responsible in meeting the deadlines for the development side until production.

Page 5 Version 1.0
3. TEST STRATEGY

Page 6 Version 1.0
3.1 Test Objective

The objectives of this Test Plan are the following:
• To ensure that modules and functionalities to be tested in an agile environment is

properly documented.
• To make sure that Test Plan and Test cases are updated based on the result of SPRINT
planning
• To produce Test Cases that could be reused for functional and UAT execution
• To ensure that all functionalities of PMIS v4.0 are working based on the objectives and
goals defined in Project Overview section of the same document
• To ensure that Business requirements and processes of the division are being met.
• To make sure that information of PCIEERD employees and proponents are always
secure and confidential.
• To produce a production-ready software (eliminate major defects that could affect the
production of the division)
3.2 Test Assumptions

General
• Created testing environment for functional testing with production-like data
• Testing will be performed by Information Systems Analyst – Quality Assurance (ISA-

QA)
• Testing is a black-box type, if the system shows correct information, it is assumed that
the database is working correctly.
• IT Management Unit Head will review and approve test cases by ISA-QA prior to start
test execution
• Defects will be reported to development team through failed approved test cases with
snapshots created by ISA-QA
• All Updates in the system will be subject to the creation of a new version of test cases
(that is also subject to approval)
• Updates coordinated to the IT Management Unit Head before applying to the test
environment
• Project team members have the adequate knowledge of the system
Functional Testing
• Functional testing will be done on Project Management Information System (PMIS) v4.0
only
• Tests will only be done in the Test environment

Page 7 Version 1.0
• PCIEERD Management provided documents for business requirements and processes

which will be the bases of functional testing
• Test Plans and test cases are updated based on the result of SPRINT planning
User Acceptance Testing (UAT)
• UAT will be performed by selected actual users with project managers, project leaders,
FAD, admin and super admin roles considered as end-users.
• Test Cases used in functional testing will be provided for end-users.
Non- Functional Testing
• Security testing will be done on Project Management Information System (PMIS) v4.0
only
• Risks and vulnerabilities of the system will be identified and fixed
3.3 Test Principles

• Testing will be done in an Agile Environment
• Testing will be focused on meeting the business requirements of PCIEERD council
• Test environment should reflect production environment as much as possible
• Testing will be divided to five user accounts, each with defined test cases
• Testing process will be well-defined with the ability to change as needed
• Testing will be a repeatable activity with approved test documents

• Testing must have an entry and exit criteria
3.4 Data Approach

• Test environment for Project Management Information System v4.0 must have pre-
loaded data for functional testing
• PCIEERD and proponents’ information must always remain secure and confidential

Page 8 Version 1.0
3.5 Scopes and Levels of Testing
3.5.1 Functional Testing
Purpose: The purpose of functional testing is to ensure the functionality of the system.
Ensure proper application navigation, data entry, processing, and retrieval. Test will serve
as a black box testing which will focus on inputting and validating the output of the
system.
Functionalities to be tested/Scope: Please see Appendix pages for List of Approved test
cases
Tester/s: Information Systems Analyst - QA
Method: Tester will perform a manual testing that will be based on the approved test
cases listed on Appendix pages of this document. Execute each test case using valid and
invalid data to verify the following:
• Expected results occur when valid data is used

• Appropriate warning messages are displayed when invalid data is used
• Each business rule is properly applied
Timing: After identifying all the level of complexity of all modules and defining the test
scenarios
Test Acceptance Criteria:
1. Test environment with an existing test data
2. Existing users with PM, PL, FAD, Admin and Super Admin roles
3. No issues reported for the functionalities to be tested

4. Approved and signed test cases and test plans
Sign-off Readiness
• Approved Test Cases • Application deployed in

testing environment
• Production like data with
existing users with PM, PL,
FAD, Admin and Super
Admin roles

Page 9 Version 1.0
Test Deliverables:
No. Deliverable Name Author Reviewer

IT Management Unit
1 Test Plan ISA - QA Head, Division Chief
IT Management Unit
2 Test Cases ISA - QA Head, Division Chief
Dev. Team, IT
3 Bug/Defect List ISA - QA Management Unit Head
3.5.2 Regression Testing
Purpose: Regression Testing phase will confirm if any code changes or update from
development team will not affect any existing working features.
Tester/s: Testing will be performed by Information Systems Analyst – Quality Assurance

(ISA-QA)
Method: Test cases for security testing will be created and executed using Black box
Timing: This testing will be performed after every code release
Test Deliverables:

Regression Testing Test IT Management Unit
1 Cases ISA - QA Head
3.5.3 User Acceptance Testing

Purpose: This testing phase will focus on meeting the business requirements of
PCIEERD council. This will serve as the final testing before system deployment.
Tester/s: Testing will be performed by actual end-users with Project Management, Project
leader, FAD, Admin and Super Admin role
Method: End-users will use the UAT test cases provided by the test team. End-users will
validate if the correct output is achieved from valid input.
Timing: This test will be performed after all levels of testing is done and before system
deployment to production
Test Deliverables:

IT Management Unit
1 UAT Test Cases ISA - QA Head

Page 10 Version 1.0
3.5.4 Security Testing
Purpose: The purpose of Security testing is to identify possible security risks in Project
Management Information System v4.0 and help developers fix these problems through
coding
Tester/s: Testing will be performed by Information Systems Analyst – Quality Assurance

(ISA-QA)
Method: Test cases for security testing will be created and executed using Black box
Timing: This test will be performed after functional testing
Test Deliverables:

Security Testing Test IT Management Unit
1 Cases ISA - QA Head

Page 11 Version 1.0
3.6 Test Effort Estimate
This test estimation is based from the schedule provided by the Information Technology
Management Unit (ITMU) Head as part of the deliverables for March 2020 listed below:
Date: February 26
Feb March
Task Assigned Status W3 W4 W5
W1 W2 9-13 16-20 23-27
Design Thinking Output George
Models Keish Done
PMIS UI Design
Project Interface Hershey Done
Login Interface Hershey
Account Page Hershey
Listing of projects/files/etc. Hershey
CRUD
View Project Profile Jhon
List of Project Profile Jhon
LIB Jhon
List of files/ Uploading of files Jhon
Accomplishment Jhon
QA
Test Plan Rods
Test Cases Rods
Regression Test Rods
QA ESTIMATION: (Week 3 – Week 4)

Testing Level QA Activities Man Hours Comments/Remarks
Test Case Design and Execution Phase:
Log-in Interface 1
Account Interface 0.5
View Project Profile 3
List of Project Profile 4
FUNCTIONAL TESTING
LIB 4
Uploading files/List of files 3
Accomplishments 3
Total Execution Hours 18.5
Defect Identification and reporting 8

RE-TEST Re-testing 8
Total UAT Hours 16
TOTAL ESTIMATED HOURS 34.5

Page 12 Version 1.0
4. EXECUTION STRATEGY

Page 13 Version 1.0
4.1 Entry and Exit Criteria
ITMU Division
Entry Criteria Head ISA-QA Dev. Team Chief
Development for all functionalities/modules specified from
SPRINT Planning
Test Environment with Production-like data
PM, PL, FAD, Admin, Super Admin test account
Business Requirements
Work Plan and Schedules
Test Plan is ready and approved
Test Case design is 100% completed
ITMU Division
Exit Criteria Head ISA-QA Dev. Team Chief
Test Cases executed 100%
All documentations are completed
No critical issues or defects
All defects have been reported
90% of defects have been fixed
All actual results are recorded in test cases with proper
versioning
UAT documents are completed
Clean up of test environment
Migration of new and live database
Production site is ready

Page 14 Version 1.0
4.2 Test Cycles

• Test will be done based on the first update from the development team. First cycle aims
to eliminate major defects that occurs in major modules for PMIS v4.0.
• Second cycle is to make sure that defects reported during first update /cycle is fixed and
make sure that no working modules are affected by the update.
• UAT will be guided by approved and passed test cases from functional testing
• Regression Testing will be performed every code release
4.3 Validation and Defect Management

• Defects will be reported to the Development Team by IT Management Unit Head from
ISA-QA
• A bug list in excel form will be provided with failed test cases attached (with snapshots
of the issue)
• Development Team will verify the issue reported, fix them and inform ISA-QA is it is
ready for re-test.
• Issues or defects will be identified based on the following categories:
Severity Impact
* Critical defect that could affect the whole operation of the system
* These critical defects that will lead to system crash.
High
* There is an error that could affect the system and other module to be
tested, but there are work-around to test the latter.
Medium
* Defect that has minimum impact to production

Low
4.4 Defect Tracking and Reporting

Below is the flowchart for Defect Tracking and Reporting

Page 15 Version 1.0

Page 16 Version 1.0

Page 17 Version 1.0
5. TEST MANAGEMENT PROCESS

Page 18 Version 1.0
5.1 Test Management Tools

• Manual testing based from the approved Test cases
• Microsoft Excel – to create test scripts, test cases, bug list and other functional testing
related documents
• Microsoft word – to create user manuals, test plans and other related documents
5.2 Test Design Process
• Requirements Gathering - This stage will be for PCIEERD management to relay the
business requirements of the council as well as the process and major roles that they need
to achieve from Project Management Information System v4.0.
• Review and Understanding Requirements – Development team and ISA-QA needs

to understand and be able to document the requirements provided by PCIEERD council.
• Preparation of Test Plan and Test Cases – ISA-QA will proceed with creating test
plan and test case design as well as the estimation of testing.
• Test Case Subject to Approval – at this stage, ISA-QA needs to submit the Test Cases
created for approval of IT Management Unit Head
• Incorporation of comments on test cases – Changes to Test cases from IT

Management Unit Head, Division Chief, and project team members will be applied to test
cases, then re-submit for final approval
• Conduct of Testing - This is the final stage of test design, when all test cases are
signed and approved, ISA-QA can now proceed to testing execution

Page 19 Version 1.0
5.3 Test Execution Process
• Execute Approved Test Cases – Once all test cases are approved, ISA-QA will
proceed with the test execution based on the test cases’ actual results.
• Mark Status (Pass/Fail) – Marked Pass if actual test results conform with the
expected results and Fail if non-conformance.
• Follow ‘Bug/Defect Reporting Flow’ – Report bugs/defects found during the

execution of test cases with snapshot of the issue experienced
• Send Report to the IT Management Unit Head regarding the result of testing –
ISA - QA will send reports including bug list to IT Management Unit Head.
• Complete test execution of all Test Cases – ISA-QA will complete all remaining test
cases.
5.4 Test Risks and Mitigation Process
Risks Impact Mitigation

Proceed with testing other
Delayed testing due to delayed High modules that will not be
updates from developers affected by the updates
Prompt coordination or
Defects were discovered late High notification with developers to
raise and fix defects.
Test Plan are divided to
different accounts to lessen the
Not enough resources Medium coverage of testing and the
need for resources
Team should have an advance

Natural disaster Low plan aiming to continue the
testing phase amidst the
occurrence of natural disasters

Page 20 Version 1.0
6. TEST ENVIRONMENT
Project Management Information System v4.0
IP Address: http://10.10.115.40/projects/
Google Chrome version 48.0 and above, Firefox version 69.0, Microsoft Edge, and other
browsers that are available to test the system.

Page 21 Version 1.0
7. APPROVALS
Signature
Name
Role
Date
Signature
Name
Role
Date

Page 22 Version 1.0
8. References
• IEEE 829 - Systeme Evolutif Limited. IEEE Test Plan Outline - Foundation Course in
Software Testing [PDF File].2014. Retrieved from
https://jmpovedar.files.wordpress.com/2014/03/ieee-829.pdf
• Hesham Alaqail. Shakeel Ahmed. Overview of Software Testing Standard ISO/IEC/IEEE

29119. February 2018. Retrieved from
https://www.researchgate.net/publication/323759544_Overview_of_Software_Testing_S
tandard_ISOIECIEEE_29119
• IEEE 829-1998 - Software Quality Engineering - Version 7.0. Test Case Specification
Template [PDF File]. 2001. Retrieved from
http://www.ufjf.br/eduardo_barrere/files/2011/06/SQETestCaseSpecificationTemplate.p
df
• Kumar, R.(2015, May 26). An Effort Estimation Model for Software Testing. Retrieved
from https://www.linkedin.com/pulse/effort-estimation-model-software-testing-rahul-
kumar
• Shiskin,V. and Gombos, A.Test Estimation Best Practices. Retrieved from

https://www.qualitestgroup.com/white-papers/test-estimation-best-practices/

Page 23 Version 1.0
9. OTHER REQUIREMENTS

Page 24 Version 1.0
Appendix A: List of Test Cases for Project Management role
Case Number Test Cases

TC_PMIS_PM_1.0 Test if PM user can log-in to PMIS v4.0 account using valid username and
password
TC_PMIS_PM_1.1 Test if PM user can log-in to PMIS v4.0 account using invalid username and
password
TC_PMIS_PM_1.2 Test if PM user can log-in to PMIS v4.0 account using BLANK username and
password
TC_PMIS_PM_1.3 Test if PM user can log-out of PMIS v4.0 using log-out button
TC_PMIS_PM_1.4 Test if PM user can log-out of PMIS v4.0 by closing the page
TC_PMIS_PM_1.5 Test if PM user can log-out of PMIS v4.0 by exiting the browser
TC_PMIS_PM_2.0 Test if PM user can view Dashboard Menu
TC_PMIS_PM_2.1 Test if PM user can view Project List Menu
TC_PMIS_PM_2.2 Test if PM user can view Project Details tab
TC_PMIS_PM_2.3 Test if PM user can view Task tab
TC_PMIS_PM_2.4 Test if PM user can view Evaluation tab

TC_PMIS_PM_2.5 Test if PM user can view Financial tab
TC_PMIS_PM_2.6 Test if PM user can view Technical tab
TC_PMIS_PM_2.7 Test if PM user can view Files tab

Page 25 Version 1.0
Appendix B: List of Test Cases for Project Leader role

TC_PMIS_PL_1.0 Test if PL user can log-in to PMIS v4.0 account using valid username and password
TC_PMIS_PL_1.1 Test if PL user can log-in to PMIS v4.0 account using invalid username and password
TC_PMIS_PL_1.2 Test if PL user can log-in to PMIS v4.0 account using BLANK username and password
TC_PMIS_PL_1.3 Test if PL user can log-out of PMIS v4.0 using log-out button
TC_PMIS_PL_1.4 Test if PL user can log-out of PMIS v4.0 by closing the page
TC_PMIS_PL_1.5 Test if PL user can log-out of PMIS v4.0 by exiting the browser
TC_PMIS_PL_2.0 Test if PL user can view Dashboard Menu
TC_PMIS_PL_2.1 Test if PL user can view Project List Menu
TC_PMIS_PL_2.2 Test if PL user can view Project Details tab
TC_PMIS_PL_2.3 Test if PL user can view Task tab
TC_PMIS_PL_2.4 Test if PL user can view Evaluation tab
TC_PMIS_PL_2.5 Test if PL user can view Financial tab
TC_PMIS_PL_2.6 Test if PL user can view Technical tab
TC_PMIS_PL_2.7 Test if PL user can view Files tab

Page 26 Version 1.0
Appendix C: List of Test Cases for FAD role

TC_PMIS_FAD_1.0 Test if FAD user can log-in to PMIS v4.0 account using valid username and password
TC_PMIS_FAD_1.1 Test if FAD user can log-in to PMIS v4.0 account using invalid username and
password
TC_PMIS_FAD_1.2 Test if FAD user can log-in to PMIS v4.0 account using BLANK username and
password
TC_PMIS_FAD_1.3 Test if FAD user can log-out of PMIS v4.0 using log-out button
TC_PMIS_FAD_1.4 Test if FAD user can log-out of PMIS v4.0 by closing the page
TC_PMIS_FAD_1.5 Test if FAD user can log-out of PMIS v4.0 by exiting the browser
TC_PMIS_FAD_2.0 Test if FAD user can view Dashboard Menu
TC_PMIS_FAD_2.1 Test if FAD user can view Project List Menu
TC_PMIS_FAD_2.2 Test if FAD user can view Project Details tab
TC_PMIS_FAD_2.3 Test if FAD user can view Task tab
TC_PMIS_FAD_2.4 Test if FAD user can view Evaluation tab
TC_PMIS_FAD_2.5 Test if FAD user can view Financial tab
TC_PMIS_FAD_2.6 Test if FAD user can view Technical tab
TC_PMIS_FAD_2.7 Test if FAD user can view Files tab

Page 27 Version 1.0
Appendix D: List of Test Cases for Admin role

TC_PMIS_AD_1.0 Test if AD user can log-in to PMIS v4.0 account using valid username and password
TC_PMIS_AD_1.1 Test if AD user can log-in to PMIS v4.0 account using invalid username and password
TC_PMIS_AD_1.2 Test if AD user can log-in to PMIS v4.0 account using BLANK username and
password
TC_PMIS_AD_1.3 Test if AD user can log-out of PMIS v4.0 using log-out button
TC_PMIS_AD_1.4 Test if AD user can log-out of PMIS v4.0 by closing the page
TC_PMIS_AD_1.5 Test if AD user can log-out of PMIS v4.0 by exiting the browser
TC_PMIS_AD_2.0 Test if AD user can view Dashboard Menu
TC_PMIS_AD_2.1 Test if AD user can view Project List Menu
TC_PMIS_AD_2.2 Test if AD user can view Project Details tab
TC_PMIS_AD_2.3 Test if AD user can view Task tab
TC_PMIS_AD_2.4 Test if AD user can view Evaluation tab
TC_PMIS_AD_2.5 Test if AD user can view Financial tab
TC_PMIS_AD_2.6 Test if AD user can view Technical tab
TC_PMIS_AD_2.7 Test if AD user can view Files tab

Page 28 Version 1.0
Appendix E: List of Test Cases for Super Admin role

TC_PMIS_SA_1.0 Test if SA user can log-in to PMIS v4.0 account using valid username and password
TC_PMIS_SA_1.1 Test if SA user can log-in to PMIS v4.0 account using invalid username and password
TC_PMIS_SA_1.2 Test if SA user can log-in to PMIS v4.0 account using BLANK username and
password
TC_PMIS_SA_1.3 Test if SA user can log-out of PMIS v4.0 using log-out button
TC_PMIS_SA_1.4 Test if SA user can log-out of PMIS v4.0 by closing the page
TC_PMIS_SA_1.5 Test if SA user can log-out of PMIS v4.0 by exiting the browser
TC_PMIS_SA_2.0 Test if SA user can view Dashboard Menu
TC_PMIS_SA_2.1 Test if SA user can view Project List Menu
TC_PMIS_SA_2.2 Test if SA user can view Project Details tab
TC_PMIS_SA_2.3 Test if SA user can view Task tab
TC_PMIS_SA_2.4 Test if SA user can view Evaluation tab
TC_PMIS_SA_2.5 Test if SA user can view Financial tab
TC_PMIS_SA_2.6 Test if SA user can view Technical tab
TC_PMIS_SA_2.7 Test if SA user can view Files tab

Page 29 Version 1.0

Test Plan v1 PMIS Agile

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Test Plan v1 PMIS Agile

Uploaded by

Copyright:

Available Formats

Philippine Council for Industry, Energy, and Test Plan for Agile testing of

Emerging Technology Research and Project Management Information System v4.0

Prepared by Rodelyn G. Lobo

March 06, 2020

PMIS v4.0 Phase 1 – Test Plan

PMIS v4.0 Phase 1 – Test Plan

PMIS v4.0 Phase 1 – Test Plan

1.2 Project Overview

• To improve the User Interface to more user-friendly environment

• To progress the financial monitoring functionality

PMIS v4.0 Phase 1 – Test Plan

• FAD/Finance and Accounting Division responsible for financial monitoring

• Information Systems Analyst – QA prepares testing materials and user manuals,

PMIS v4.0 Phase 1 – Test Plan

PMIS v4.0 Phase 1 – Test Plan

2.1 Role Expectations

Roles Name Contact Information

1 IT Management Unit Head George Monroyo 837 2071 loc 2107

2.2 IT Management Unit Head

• Schedules weekly deliverables for the team

2.3 Information Systems Analyst – QA

• Ensure that the exit criteria are being followed

2.4 Development Team

PMIS v4.0 Phase 1 – Test Plan

PMIS v4.0 Phase 1 – Test Plan

3.1 Test Objective

• To ensure that modules and functionalities to be tested in an agile environment is

3.2 Test Assumptions

• Created testing environment for functional testing with production-like data

• Testing will be performed by Information Systems Analyst – Quality Assurance (ISA-

• Project team members have the adequate knowledge of the system

• Tests will only be done in the Test environment

PMIS v4.0 Phase 1 – Test Plan

• PCIEERD Management provided documents for business requirements and processes

User Acceptance Testing (UAT)

• Test Cases used in functional testing will be provided for end-users.

Non- Functional Testing

• Risks and vulnerabilities of the system will be identified and fixed

3.3 Test Principles

• Testing will be focused on meeting the business requirements of PCIEERD council

• Test environment should reflect production environment as much as possible

• Testing process will be well-defined with the ability to change as needed

• Testing will be a repeatable activity with approved test documents

3.4 Data Approach

PMIS v4.0 Phase 1 – Test Plan

3.5 Scopes and Levels of Testing

3.5.1 Functional Testing

Tester/s: Information Systems Analyst - QA

• Expected results occur when valid data is used

Test Acceptance Criteria:

1. Test environment with an existing test data

3. No issues reported for the functionalities to be tested

• Approved Test Cases • Application deployed in

PMIS v4.0 Phase 1 – Test Plan

No. Deliverable Name Author Reviewer

3.5.2 Regression Testing

Tester/s: Testing will be performed by Information Systems Analyst – Quality Assurance

Timing: This testing will be performed after every code release

No. Deliverable Name Author Reviewer

3.5.3 User Acceptance Testing

No. Deliverable Name Author Reviewer

PMIS v4.0 Phase 1 – Test Plan