Testing and Delivery

This section outlines the testing procedures, acceptance criteria, deployment processes, and content delivery requirements for all digital and interactive experiences developed for Auckland Museum. Rigorous testing ensures that all experiences are technically robust, visitor-ready, and meet the Museum’s operational and research standards.

Types of Testing Required

To ensure high-quality, reliable digital experiences, the following types of testing are required at a maximum and are required to be addressed in the timeline of any new digital experience at Auckland Museum.

Audience Research and Impact Testing

Testing with real visitors to assess usability, engagement, and experience quality, conducted in collaboration with Auckland Museum’s Audience & Impact Research (A&IR) team.

Software and Bug Testing

Identification and resolution of functional bugs, performance issues, and software inconsistencies.

Hardware Functional Testing

Verification that all hardware components operate correctly on the actual devices to be used in-gallery.

Operational Testing

Simulation of gallery conditions (e.g., using Q-SYS control) for at least one additional week post-soak testing.

Soak Testing

Prolonged testing (minimum one week) to confirm stability during continuous use in a gallery-like environment.

Analytics and Logging Validation

Ensures all visitor interactions are accurately captured and logged per the Museum’s analytics standards.

Accessibility and compliance testing

Confirms compliance with accessibility, privacy and legal requirements.

Testing Timeline and Process

  • Pre-Launch Testing Window

Completed digital experiences must be delivered to Auckland Museum no less than six weeks prior to public launch to allow adequate time for internal testing. This timeline may vary based on project complexity and will be confirmed during contract negotiations. 

  • Hardware for Testing

All digital experiences must be tested on the same hardware intended for in-gallery use. The Museum will procure and provide this hardware to vendors early in the project where necessary.

  • Parallel Testing at Auckland Museum

In some instances, Auckland Museum will replicate the experience setup internally for parallel testing. If full replication is not feasible, alternative testing arrangements will be discussed and agreed upon.

  • Deployment Procedures

All updates and bug fixes post-launch must be versioned and submitted for testing individually. Each deployment requires a completed Request for Change (RFC) form, approved by the appropriate Auckland Museum staff. Deployments must be conducted outside of Museum opening hours

Audience Research & Impact (AI&R) Testing

Audience research is a critical part of development and helps guide decision-making.

Planning

  • Testing needs are agreed upon by the project team and AI&R team on a case-by-case basis

  • Testing sessions must be scheduled in advance and aligned with the A&IR team's availability.

  • Vendors must supply well-developed, test-ready files that are representative but allow room for iteration. 

Execution

  • The DX team will test files on correct hardware one week prior to testing with visitors. 

  • A&IR will coordinate recruitment and data collection, typically beginning one hour after opening and ending one hour before closing to respect visitor experience.

Reporting

  • AI&R will deliver a summary report with findings and recommendations usually within one week of testing. 

  • Follow-up discussions with vendors will determine actionable changes.

Acceptance Criteria

  • Review and Approval

The Museum will review each delivery as scheduled, conducting technical, user, and visitor acceptance testing.

  • Test Case Development

Vendors must propose acceptance test cases; Auckland Museum reserves the right to add additional cases.

  • Testing Constraints

Testing space within the Museum is limited, especially for large-scale experiences. Access to gallery spaces during fit-out may be restricted and must be factored into the project schedule.

Delivery and Ownership Requirements

Intellectual Property

By default, all digital experiences become the property of Auckland Museum upon delivery, with a perpetual, royalty-free, and irrevocable license unless otherwise specified in the contract.

Requirement

Priority

Deliver content in source code/source file format (artwork excepted)

MUST

No reliance on third-party digital rights management

MUST

No requirement for visitor onboarding without Auckland Museum’s written approval

MUST

License source files for modification and reuse in perpetuity unless otherwise agreed

SHOULD

Deliver in a way that allows Auckland Museum to build, update, and deploy the experience for its entire lifespan

MUST

Deliver source files to an Auckland Museum GitHub repository

SHOULD

Deployable on staging and production networks

SHOULD

No reliance on external data sources without prior agreement

SHOULD