DoubleClick QA employs numerous tests that vary based on the format and features of each creative. These tests are meant to demonstrate the technical integrity of the creative, without assessing or judging any aspect of its design. Such questions are for the client to decide.
When you publish creatives in QA, DoubleClick tests them. But it's important for you to test them first!
1. Access the QA Console and Preview tab
The DoubleClick Studio QA Console interacts with the Studio Web UI to let quality assurance specialists review and test completed creatives and efficiently approve or reject them.
There are four lists of creatives in the side panel of the QA Console:
- Development: being developed
- Published: ready for QA processing
- Approved: okayed by the QA specialist
- Rejected: rejected by the QA specialist
You should test creatives with a status of Development before you publish to QA.
To view a creative in the Preview tab
- Click a creative in the Development list.
To navigate among roadblocks (if applicable), click . In the Roadblock options dialog box, use the drop-down to find a roadblock, then click a linked creative within it to go to the workflow for that creative.
2. Open the Output Console
Click Output Console to view events specific to the creative you're previewing. Toggle between Simple mode, which logs only custom events, and Advanced mode, which separates unfiltered events as follows:
- Events triggered - logs standard and custom events.
- Events logged - shows run-time logs for cumulative standard and custom events.
Click Clear console to clear out the list and start over.
3. Test creatives for basic functionality using test scripts
These checklists include basic tests and test cases, along with detailed checklists, specific to the format1 and features of each creative.
1Availability of creative formats varies, depending on your level of support.
2If you're building to DoubleClick specs or if you don't have a spec sheet but want to check against general guidelines, use the DoubleClick Best practices (LCDs) checklist (more below).
4. Test creatives agains site specs (LCDs)
Many publishers provide their own creative specifications that you should use, if available, as QA guidelines. These specs can include file size, dimensions, video length, and frame rate.
If you don't have the publisher's specs for a creative, there's a set of recommended creative specs--also known as lowest common denominator specs (or LCDs)--unique to each creative that most publishers accept. These differ for the North America (NAM) and Europe, Middle East and Africa (EMEA) regions based on publisher practices. You can use these test scripts to verify DoubleClick's best practices (LCDs).
5. Test your creative in multiple browsers
The Rich Media QA team doesn't test on every browser version listed in the supported browsers article, but we do test on the most commonly used browsers, operating systems, and Flash versions based on market penetration. We stay current with releases of new browser versions and test on the latest live versions to report possible bugs in our components.
See also QA requirements and tools.