Quality Assurance for Lifecycles
Quality Assurance is the process of checking your lifecycles, in order to spot and prevent any errors, before activating and running with them.
The Quality Assurance, or QA process, works in the same way as with Projects and the QA Portal.
Once your lifecycle has been built, you'll need a member of your team to QA it. You will need to fulfill this step and sign-off the lifecycle in order to move it into Ready status.
➡ Send to QA
The first thing you'll need to do is move the lifecycle version from In Dev to QA.
From Define Activities mode, you'll find Send to QA at the top right of the screen. Once you select this, you'll be presented with the following message;
Here's a quick run through;
✅ QA the Lifecycle
From the QA status, select the lifecycle version that you wish to Quality Assure and it will open into the QA window.
As with quality assuring an activity, you need to check each component of the event and 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 slot's, but also; the structure of the lifecycle, the entry conditions, the ending event(s) and the trigger and segment of each event.
The entire event row will turn green once every activity box in that event has passed QA.
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.
Tip: Activity boxes or events that have been QA'd will remain green, even if you reject the lifecycle version, send it back to In Dev and work on another part of the version and return it to QA. As long as the QA'd event is not changed whilst back In Dev.
That means you don't need to start from scratch with the QA process if you spot a small mistake that only affects one activity.
👍 Approve Lifecycle
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.
Once you select Approve from the top right of the screen, you will be presented with the following message;
By selecting Approve Now, the version will move to Ready status and 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 goes live.
For more information about how to prepare the lifecycle version for launch, check here.
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 where it can be edited as required. By selecting Reject from the top right of the screen, you will be presented with the following message;
Tip: 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 👍