This section is dedicated to the acceptance testing of:
- onboarding project milestones
- new modules and features you choose to subscribe to.
Acceptance Testing: Onboarding Projects and Critical Path Modules
At the conclusion of each project milestone, Emersion will send you a Notice of Completion. This document means that Emersion warrants that the deliverables as per the Schedule of Works contain no Severity 1 or 2 defects, the system is fit for use and deployed into the Production (live) environment. The system is ready for operations and is now considered “live”.
Upon receiving this notice, the project sponsor (or representatives) must ensure it is 'fit for purpose' as stated in the Emersion Services Agreement by performing an acceptance test of the services.
Below are instructions on how to conduct the User Acceptance testing for each of the main milestones for all onboarding projects. Each includes test plans for modules and features included in the core subscription of Emersion are on the critical path to go-live with billing in Emersion. These test plans focus attention on the minimum requirements that need to be met to get the system configured enough to send invoices to your customers.
Milestone 1 - Base System and Service Types
Acceptance Testing: Core Modules
Start here if you are looking for test plans for modules and features included in the core subscription of Emersion, but are not on the critical path to going live.
Acceptance Testing: Optional Modules
Start here if you are looking for test plans for optional modules,
Acceptance testing should only ever be conducted by staff users with adequate permissions, such as Administrator Full Powers, or any user with a role group where all module permissions and Base Power is enabled.
How Do I Test?
See this article for guidance on setting up test accounts and services.
