Basic QA test checklist

Purpose: To introduce the different types of Rich Media basic testing.

Click here to download a clickable checklist version of this table in spreadsheet form.

Test case Test Expected result
User interface testing (cosmetic)    
Testing the look and feel of the creative.
  • Match the creative with the original asset provided by the client, if applicable.
  • The creative should match the original asset provided or with special notes mentioned in the client note, if applicable.
  • Check for inconsistencies in the creative and across the creatives in a campaign.
  • There should be no inconsistencies in the creatives.
  • Verify font quality, font shift.
  • Verify that the fonts aren't blurred and there's no font shift.
  • Check for image quality, image shift.
  • Verify that the images aren't blurred and there's no image shift.
  • Check for animation glitches.
  • Verify that there is no animation glitch in the creative.
  • Check for the audio/video quality.
  • The audio/video quality should be good. There should be no pixelation, and aspect ratio should be maintained.
  • Check for the Call To Action (CTA).
  • The CTA should match the purpose it was designed for (for example, click-through, panel switching, etc.)
Performance testing    
Testing that a creative meets the basic performance requirements specified in the test checklist. (Sometimes, in absence of a test checklist, this section covers exploratory testing of how fast or efficiently the application performs.)
  • Clean Testing - Clear the cache before testing the creative. Look for the files loaded in the cache as part of the creative load and execution.
  • The creative should run without errors at the time of checking with the cache cleared. The cache should not have any high volume or any unexpected files, other than the defined standard or unexpected files loaded as part of the creative execution.
  • CPU Utilization Testing - Check CPU utilization on the initial load of the creative and while the creative is running.
  • The creative should not affect CPU utilization. At the very least, during creative load or execution, CPU utilization should be normal (less than 40%).
Crash testing    
Testing what causes the creative to crash.
  • Based on the ad type and functionality, try different ways to crash the creative.
  • The creative shouldn't crash in any cases. If the creative crashes within a specific scenario, please report the bug.
Compatibility/platform testing    
Testing how well the creative performs in a particular environment: browser, software, Flash version, operating system, etc.
  • Test the creative across different browsers-software-Flash version-OS combinations.
  • The creative should run smoothly and as required by the client across different browser-software-Flash version-OS combinations.
Click-through functionality testing    
This tests to see if the creative is clicking through.
  • Click on the creative to verify that it's clicking through. Also, verify the click-through URL against the creative brief.
  • There should be at least background click functionality implemented in the creative. And the click-through URL should match the URL provided in the brief.
  • Verify that the click-through URL opens in a new window or the same window.
  • All exits should open in a new window. They should open in the same window only if the client has asked for a special case.
  • Verify that the click-through URL isn't blocked by the pop-up blocker.
  • Pop-up blocker shouldn't block the exit (click-through) URL.
Usability testing    
Testing for user friendliness
  • Check the user friendliness of the creative.
  • The creative should be user-friendly. The creative should match the original asset provided. In addition, it should be judged in terms of its ability to attract more users.
  • Example: Check how quickly and accurately the ad responds to user interaction (how long it takes for the ad to expand when you click it).
  • If the creative matches the original but you don't find it user-friendly, please add a note in the task when you send it to the client.
Regression testing    
Retesting after revision fixes or modifications of the software or its environment.
  • Retest the creative after each revision cycle and look for bugs that may be generated as you fix other revisions.
  • There should not be any cases where one functionality or part of the creative is affected while you're fixing another revision. If you encounter new bugs, please resend the QA revision and apply the regression testing again.
Backup image testing    
If there's a problem with the Rich Media creative, the backup image must be implemented as a temporary replacement until the problem is resolved.
  • Check the backup image.
  • There should be a backup image associated with each creative and it should match the creative. In case of a date swap, we may need to provide different backups for different dates.
  • Check the backup image click-through URL.
  • The backup image click-through URL should match the one provided in the creative brief or on the progressive unit.
  • Check the backup image call to action. For example, verify the backup image for the creative that says "Rollover..." or "Click..."
  • The backup image should match any of these calls to action, independent of the calls that the ad uses. For example, If the Rich Media ad says "Roll over here," the backup image should still say "Click here" and not "Roll over here."
Tracking event testing    
This is testing to see if events are firing off properly. We always do this testing as part of our "full-serve" model. For "QA only," we do this if the client or CM asks us to.    
Counters: The number of times that a user interacts with any part of an ad in a specified way (mouse-over, mouse-out, click-in, data loading, keyboard entry, etc.). Anything that can be captured by Flash can be recorded as a counter event.
  • Interact with the ad to verify that each counter event is logged and tracked. (Please follow the creative brief notes for the special tracking requirement.)
  • The counter event should be logged and the count (tracking) should increase from 0 to 1. The counter event is capped at 1 unless the client asks specifically for uncapped events.
Exits: The number of click-throughs generated by the creative.
  • Click on the exit area to verify that the exit event is logged and tracked every time you click on it.
  • The exit event should be logged and the count should increase by 1 each time the user clicks on it. Also, the exit should not open in the same window. It should always open in a new window or tab unless specifically requested by the client. The click-through should fire on release and not on press.
Timers: The time during which a user views and interacts with a specified part of the creative. A creative can have multiple timer events, each one timed independently.
  • Interact with the ad to verify timer start and timer stop events. Also, look for the time increment while the timer event is going on.
  • The timer should start and stop every time you interact with the timer event. The timer shouldn't register any interaction after the event associated with the timer is stopped.

Always follow the creative brief notes for any special tracking requirement. And always follow the client specific notes for any client-specific tracking requirements.
Android-style image of the author of this page

Sarah is a DoubleClick Studio expert and author of this help page. Help her improve this article by leaving feedback below.

Was this article helpful?