Testing Protocols

The following is a breakdown of important things to remember when QA testing, attempting issue replication, or doing demos in our testing firms. These include Demo Broadcasting/Telecasting, Your Radio Stations, My Radio Stations, Your Prod Service, and others that we may create in the future.

For vPro specifically, please remember to not use Your Radio Stations and other "legacy" firms that were created for vPPO testing and copied over. Demo Broadcasting is vPro's only testing firm. Demo Telecasting is ONLY for Demo/Training.

You can find a Google Spreadsheet with Testing Accounts and more on this link.

1. Only use fictional Client Names
   1. Ctrl+Alt+R will insert one if you use the vCreative Support Helper application (Windows only)
   2. If you are a Mac user, you can download the Fictional Client Names list
2. Never use words like TEST or DEMO
   1. These accounts should look like real stations
   2. This applies to Ad Types, File Types, and blog messages, use realistic-looking names/messages
   3. Role-play like you were a user.
3. Use the right accounts
   1. The abilities of an account should match its real-world versions
   2. Our testing firms should show actions that make sense
4. Complete the workflow
   1. Keep things moving along by actually processing the requests
   2. Schedule Liners, Complete Voice parts, Cart/Scheduled/Dub checks should all occur regularly
   3. Revise, Extend, and Copy as well.
5. Future Dates
   1. Things back up quickly if everything is due or runs in the next week
   2. Choose Due/Start/End/Promotional dates farther out than tomorrow and next week
      1. Text replacement shortcuts with the vCreative Support Helper are:
         1. duedate# 
         2. startdate#
         3. enddate#
   3. Mix things up (especially vPromotions)
6. Clean Up
   1. If you see a backup of unapproved PRFs, Past due, and old Revision/Extend Dates - take care of them
   2. Don't wait for someone else to sweep up
7. For UNIT/Bug Testing: Incognito is better than Clear Cache
   1. For the easiest/best testing environment, just use Incognito
      1. Start QA/Unit/Bug/Feature testing in a Chrome Incognito tab.
      2. When you need to change users or tests, close and re-open a new Incognito tab.
      3. If needing 2+ accounts, user another computer/device or Edge InPrivate window
   2. Ctrl+Alt+Num+ will easily open up Incognito Chrome windows provided the JIRA Key and that you use the vCreative Support Helper application (Windows only)
   3. Otherwise, you may need to frequently Clear Cache
      1. Done to make sure you are testing fresh code with nothing cached locally. The Clear Cache Chrome Extension can simplify this.
      2. Our users should not have to clear cache or have it cleared for them (often at least)
   4. SMOKETEST prior to a release is the exception
      
      1. We need to ensure our users aren't finding the need to clear cache, and using Incognito would work around that discovery
8. DevTools
   1. In Chrome, press Ctrl+Shift+I
   2. A window or panel will open up with "DevTools"
   3. You can detach or resize this panel. If you are using multiple monitors, move it to a side monitor.
   4. The "Console" tab should be screen-shot in its entirety if you see any "ERROR" messages while testing to add to your notes.
   5. This is INVALUABLE to the developers. 
9. EXTRA MILE
   1. If you REALLY want to knock some socks off, have OBS recording as many tests as you can as you go through them
   2. If you don't need the file, no need to save
   3. If you DID find something, save and you don't have to go back through to recreate