Testing Strategy

You Are Viewing Archived Content

The Financial Information System (FIS) went live on July 1, 2020. Visit the current Financial Management information and support page for more.

Why did the system undergo testing?

The system testing validated that the future state design, setup, and configurations met the business requirements. The intent of testing is to analyze and evaluate whether the system is:

Functioning as designed
Produces results according to policy
Protected from unauthorized access and has necessary safeguards to protect sensitive data
User-friendly and intuitive
Reliable and performs well under duress

What was tested?

Scope

Oracle Financial Cloud application: including the GL, AP, AR, PPM and Procurement modules
Enterprise Planning and Budgeting Cloud
Data conversion from current systems to Oracle Financial Cloud and Budgeting Cloud
Integrations with campus-wide systems
Oracle BI reporting (OTBI and custom reporting)
Infrastructure that supports the integrations
User roles and related access.
Workflows and approval processes

Levels of Testing

Unit Testing
Data ConversionTesting
Integration Testing
Security and User Profile Testing
Functional Testing
Business Process Testing
System Integration Testing
User Acceptance Testing

The basic approach was to test individual parts/units of the application, building up to perform an End-to-End test of the system in a production-like setting.

Each level had an individual plan that outlined the test objectives, assumptions, scope and criteria as well as test cases with associated testing processes that encapsulate design, development, execution and test/defect management.

Who is testing the system?

Testing Team	Member	Role
Test Team	William Sweetman	Solutions Architect
	Harini Sundaram	Testing Lead
	Reza Khorrami	Integrations/Conversion Test support
	Erika Szewczyk	Configuration Lead
	Maruthi Alamuri	Business System Analyst
Design Teams	Melissa Navarro	Campus General Ledger Lead
	Michelle York	Health General Ledger Lead
	Kierstin Sykes	Foundation General Ledger Lead
	Kevin Wong	Accounts Payable Lead
	Susselys Virgil	Accounts Receivable, Cash & Banking Lead
	Irene Chen	Procurement Lead
	Marissa Prough	Project Portfolio Management (PPM) Lead
	Design Teams	For each module
Integration Team	Martin Krolik	Integration Lead
Integration Team	Kurt Griskonis	Business Systems Analyst
Conversion Team	Tim Morse	Conversion Lead
	DC Binod	PPM Conversion Lead
	Jianjun Li	PO Conversion Engineer
Subject Matter Experts	Volunteers (Subject Matter Expert Recruitment)

When did testing happening?

Each level of testing listed below includes at least two phases:

Phase 1

Identify any blocking or high-severity defects and use work-arounds to execute all the test cases in the cycle.

Phase 2

Confirm resolutions to previously identified defects and execute test cases that previously required work-arounds.
Corrects gaps in the test cases that were identified during execution of the first test cycle.

Level of Testing	Status	Description	Phases	Testers
Unit Testing	In Progress Dec. 2019	Proves an individual unit of work functions as expected. This is often associated with technical object testing, although it can also be applied to a configuration unit of work.	Ongoing	Technical Teams
Data Conversion Testing	In Progress Dec. 2019	Determines the accuracy of data converted from the IFIS and other campus financial systems to OFC. Validation will include running BI reports in oracle to view the transformed data and comparing them against data from source systems based on mapping documents	Phase 1	Conversion Team Test Team SMEs
Functional Testing	In Progress Oct. 2019- Nov. 2019	Conducted to test OFC application modules against the functional requirements. Functional testing is not expected to test every discrete permutation of possible values. The Test Team will perform this testing by running through identified steps to achieve a desired functionality and recording the results. Discrete test scenarios will be executed to validate existing and new functionality are working as designed.	Phase 1 Phase 2	Design Leads Test Team
Business Process Testing	Planned Dec. 2019	Verifies all necessary business functions are incorporated into the OFC solution.	Phase 1 Phase 2	Design Leads Test Teams Design Teams
System Integration Testing	Planned Jan. 2020- Mar. 2020	Verifies the End-to-End flow of data within OFC and between integrated systems. This would involve executing End-to-End Business Use cases in a production like Setup. SIT will also validate the flow of data between the OFC and systems and the conversion.	Phase 1 Phase 2	Design Teams Test Teams Technical Teams SMEs
User Acceptance Testing	Planned Apr. 2020	Will be focused on confirming the functional requirements and business processes documented have been met by OFC solution. This testing will also focus on the identified business flows and processes that the integrated systems will support, including the inbound and outbound exchange of data and the smooth and timely flow of information. The level of testing undertaken in Functional Test and SIT should ensure that UAT demonstrates a fully working system in a way that builds the confidence of the end users and achieves final sign off.	Phase 1	Design Leads Test Team Design Teams