HootVID QA
When a template is added into production, it will initially be in a “draft” state. While in this state, the template will appear in the library, but will only be visible to anyone in Hoot with super-admin privileges. Additionally, our team will be able to create ads using these templates in order to QA them. The QA process must be followed before setting templates live.
It is a best practice to keep a local folder of media files (audio, images, videos, etc.) that can be easily accessed for QA purposes. Please contact Justin or any video team member if any assets are needed, as we have an internal packet available to download.
QA Test iterations must be created under the QA Advertiser in the Hoot Interactive account. There are multiple data sources available for a variety of data sources. Additional data sources can be added as well. The goal is to prevent draft ads from being distributed to clients until they pass QA. All ads must be labeled with the QA tester’s name and left as inactive.
For images, PNGs strongly recommended. SVG and WEBP files are not compatible and will return an error.
For video, MP4s are required.
For audio, MP3 or WAV files are recommended.
QA Checklist:
Ad Settings
Distribution can be left as Hoot VAST and any valid URL can be used for the Ad URL.
Toggle the template to active and specify both a start and end date.
Select a data source with sufficient records in order to fill out the Dynamic Elements. Filter functionality should be independent of the functionality of each individual template, so isn’t required for QA purposes.
Scene Content
Template Elements
Select a new color for both the Primary Color and the Accent Color.
Add both a Voice Over Track and a Background Track. While we have access to our library, please use an external audio file for QA.
Scene
The scene elements will vary from template to template based on design. However, the same QA process can still be followed regardless.
Text Elements
Each text field will need to be tested with a new color, as well as a long and short text string to ensure that they are formatted properly. For example, use “Hoot” as a short text string and “The Quick Brown Fox Jumped Over the Lazy Dog” as a long text string.
Media Elements
Each media element needs to be tested with their respective file type. For example, upload a video file as the video asset, and images for logos and QR codes, etc.
Dynamic Elements
Add a dynamic variable from your data source for each available element and adjust the colors. It is a best practice to test the variables as well as adding in additional text to the fields.
Rendering
After adjusting Ad Settings and Scene Content, it is time to Save & Render. The render process will identify any bugs/errors with the data integration, as they would result in a failed Render error. The final render will also help iron out any bugs related to asset scaling.
Form
If the initial QA is done by someone other than a video team member, and adjustments are required, please use the following form to identify the adjustments. The form can be sent to Shane or Justin C.
https://docs.google.com/spreadsheets/d/10DDsqE8MAwZkiPYCUAzLrDqn2M0r3KtfxRBu8PeNlp8/edit?usp=sharing
Template Activation:
If a template passes through the checklist outlined above, contact Justin or a video team member for activation. This will make the template available for client use in the production environment and the state will change to “In Production”.
Post Activation:
After a template is activated, a live QA test of the template must be completed. While no template functionality should be affected by simply activating it, we need to ensure that is the case.
Follow all the steps listed in the QA Checklist above.