Perform the final checks and the User Acceptance Testing (UAT)
Make sure P4 works as expected or flag issues to get them fixed before go-live.
The UAT
If you already have your staging site and have done the initial setup, its time to do some user acceptance testing!
Why?
Performing a user acceptance testing assures the platform can handle specific tasks in real-world scenarios. Its objective during the implementations is to get a confirmation or approval from you that the functionality of the site you got works as expected. Any issues you find during testing should be addresses by the development team and prioritised accordingly.
Where?
The testing needs to happens on your staging site and the reporting of results happens in JIRA, our product management platform. If you don’t have an account please request it to the implementation coordinator.
Who?
Each NRO P4 team should select a representative to perform UAT in their P4 instance. Ideally it should be someone who has admin rights to your platform and has the knowledge to identify if some feature is not working as expected or interferes with your NRO engagement strategy.
How?
In JIRA you will find the testing scripts that will guide you step by step through each scenario to be tested. It is recommended to watch the following 13 min JIRA training video prior to execute the tests.
Video Demo of UAT
UAT training
The final content check
Additional to the User Acceptance Testing it is recommended to do a content check before launch. This content check ensures a smooth navigation on the site and a better user experience. Some of these you might also take as recommendation.
Verify:
- Header links redirect to correct content
- Links on slides redirect to correct content
- Footer links redirect to correct content
- Slider images are displayed with high quality
- Posts shown in the articles block have a featured image
- There are no empty breaks between blocks causing empty spaces
- Engaging network forms set up correctly in happy point block
- Happy point block has a background image
- 404 page is set up correctly
- Cookie text is set correctly
- Tag pages have a background image
- Publications in tag pages have a features images
- All strings are translated (if needed)
- Include text about Organization structure in your terms and conditions page (or similar)
The Go / No-go Checklist
To ensure overall quality, consistency and security, a few key stakeholders need to say “YES” before the Actual switch is made and the PROD website replaces Planet 3 as the official new Greenpeace website. This document must be completed after the User Acceptance Test (UAT) is passed and one day before the planned launch at latest.
No approval in one of the functional areas de facto blocks the P4 go-live. Escalation and corrective meeting to discuss the next steps (postpone? cancel?) are the options.
Here’s a template of what this document looks like:
An electronically signed-off copy of the Go/No-Go checklist must be included in each NRO Planet 4 Implementation Drive.
- Go / No-Go template – Public
- GP Greece P4 Go/No-Go – Accessible to Greenpeace Staff only (Privacy reasons)
- GP New Zealand P4 Go/No-Go – Accessible to Greenpeace Staff only (Privacy reasons)
- GP India P4 Go/No-Go – Accessible to Greenpeace Staff only (Privacy reasons)
- GP Netherlands P4 Go/No-Go – Accessible to Greenpeace Staff only (Privacy reasons)
- GP Canada P4 Go/No-Go – Accessible to Greenpeace Staff only (Privacy reasons)
- GP Brazil P4 Go/No-Go – Accessible to Greenpeace Staff only (Privacy reasons)
Links & Resources
- Handbook