QA for Lifecycles
Once you've finished building your lifecycle version, it's time to send it for QA.
As Lifecycle projects incorporate many components, it's never been more important to thoroughly check; the entry conditions, the structure of the lifecycle and the set-up of each and every player engagement.
➡ Sending a Lifecycle for QA
Open the lifecycle version from In-Dev that you want to send for Quality Assurance and navigate to Define Activities view. Click Send to QA in the top right. The lifecycle version will automatically be sent to the QA status, ready to be reviewed.
💡 How to QA a Lifecycle
From the QA status of the lifecycle, select the lifecycle version that you wish to Quality Assure for the QA window to open.
Just like when quality assuring an activity, you need to check each component of the activity slot and sign-off. Once the activity slot has been signed off, the blue box will turn green to let you know that it has already been approved.
Tip: It is important to QA, not only the activity slots but also; the structure of the lifecycle, the entry conditions, the ending event(s) and the trigger and segment of each event.
Note: You will not be able to Approve the lifecycle version until all of the activity slots have been signed off and have turned green.
Once all the activity slots for each event have been signed off, the event track will also change to green.
✅ When to Approve
Once you're satisfied with all the components of the lifecycle version, you can approve it. This means that no further changes need to be made and the lifecycle version is ready to go live.
By selecting Approve Now, the version will move to Ready status to wait to be launched into production.
Note: Players will not be able to enter the lifecycle version when enabled and in Ready. Once approved, the version will wait to be launched before it is live.
For more information about how to prepare the lifecycle version for launch, check here.
🚫 When to Reject
If you notice anything that needs fixing or changing inside the lifecycle event, it should be rejected.
Rejecting a lifecycle version will send it back to In Dev status.
Good to Know: Any components of the lifecycle version that have been signed-off as part of the QA process before being rejected, and that were not changed whilst In Dev, will retain their signed-off status when the lifecycle is sent back to QA.
That means you won't have to repeat the QA process on parts of the lifecycle that were already signed-off 👍