ERP Programme Testing — testing enterprise systems in NZ
Oracle Fusion, Microsoft Dynamics 365, Salesforce, and SAP dominate the enterprise software landscape in New Zealand.
When a government agency migrates to Oracle or a bank rolls out Dynamics, the QA team must understand both the testing discipline AND the platform. A misconfigured chart of accounts, a broken approval workflow, or an untested FBDI import can cost hundreds of thousands in remediation — and that cost lands on the test team that missed it. This track teaches you both the ERP testing methodology and the platform specifics for NZ’s most common systems.
From ERP fundamentals to platform-specific testing
ERP Testing Fundamentals
Configuration testing, module architecture, data migration, and the procure-to-pay workflows that every ERP implementation lives or dies by.
~30 min read · ~65 min with exercises · ERP Testing
Lesson 2Oracle Fusion Cloud Testing
The dominant ERP in NZ government. Module architecture, FBDI imports, ESS jobs, OTBI reports, and Oracle Test Manager — tested end to end.
~30 min read · ~70 min with exercises · ERP Testing
Lesson 3Microsoft Dynamics 365 Testing
D365 Finance & Operations and Business Central. RSAT automation, 3-way match, Power Automate integration testing, and configuration-first methodology.
~30 min read · ~70 min with exercises · ERP Testing
Lesson 4Salesforce Testing
Flows, Apex triggers, permission sets, and integrations. Provar and Copado Robot for automation. Why running tests as admin is the most dangerous habit in Salesforce QA.
~30 min read · ~65 min with exercises · ERP Testing
Lesson 5Data Migration Testing
ETL verification, reconciliation by count and sum, mock migration runs, and the cut-over testing that prevents post-go-live financial surprises.
~25 min read · ~60 min with exercises · ERP Testing
Lesson 6UAT Design for ERP
Business-process-based UAT scenarios, role-based test execution, parallel run design, and the sign-off gate that actually means the system is ready.
~25 min read · ~60 min with exercises · ERP Testing
Lesson 7Multi-Vendor ERP Testing
Testing Oracle Fusion + Salesforce + middleware integrations. Silent failure patterns, integration test matrices, and defect ownership across vendor seams.
~25 min read · ~55 min with exercises · ERP Testing
ERP defects are expensive — more than most software failures
Most enterprise software projects overrun. ERP projects overrun more than most, and a significant share of that cost comes from defects found late — or not found until after go-live. A payroll run that credits 3,000 employees to the wrong cost centre, an inventory valuation method set to the wrong algorithm, a claims routing rule that locks out an entire Wellington office: these are not cosmetic bugs. They are process failures that trigger manual remediation, audit findings, and executive escalations.
The testing challenge in ERP is that the software itself is usually not the problem. Oracle, SAP, Dynamics, and Salesforce are mature, proven platforms. What fails is the configuration — the 10,000 decisions made during implementation about how the platform is set up for this organisation. Testing configuration requires a different mindset from testing bespoke software. You are not asking “does this feature work?” You are asking “is this feature set up correctly for this business?”
This track teaches that mindset, then applies it to the four platforms that dominate the NZ market. By the end you will be able to design and execute a configuration test suite, plan and run data migration testing, coordinate UAT on a large ERP programme, and test the platform-specific elements — FBDI imports, RSAT scripts, Salesforce Flows, D365 3-way match — that trips up teams who treat ERP like any other application.
Other specialised tracks
API Testing
Contract testing, status codes, and idempotency — the foundation under every ERP integration interface.
SpecialisedDatabase Testing
SQL, schema validation, and referential integrity — critical for ERP data migration verification.
SpecialisedBDD & Three Amigos
Specification by example techniques that translate business rules into ERP acceptance criteria.