Challenge Overview
You should be able to browse categories and load videos according to what's in the UI.
Test browser
In the forum, you will find a QTBrowser application for both OS X and Windows. You must test using this browser. Instructions on how to load the site will be found in the forum with the executables. This browser simulates the embedded device environment. Ideally, you should set your screen resolution to 1280x720 to simulate the embedded device as well, since the QTBrowser doesn't support resizing very well.
Bugs submitted for other browser will not be accepted - we are only targeting the QTBrowser
Keyboard navigation
The embedded device where this runs in production does not have mouse support. That means that we should expect to be able to navigate the UI with these keyboard:
* Up
* Down
* Left
* Right
* Enter
* Esc (to go back)
Please test using your keyboard.
You can select an option from the main menu, and during playback of a video, if you press "Left" on the keyboard, you'll get a navigable side menu that allows you to select other videos. During playback, pressing "Up" on the keyboard will show an info panel with a progress bar.
Content
Note that the individual videos shown in the app may change. We refresh the data on a regular basis, so don't expect the exact same videos to show at all times for all the different menu options.
Format
For each report of a limitation or bug, we need the following information:
1) Steps to reproduce, including any needed information
2) Screenshots (if applicable)
3) Expected results after the bug is fixed
4) Current results, before the bug is fixed
Only actual bugs will be counted. Tickets logged for enhancements or issues that aren't bugs won't be counted.
When in doubt, always provide a screenshot. Screenshots are very helpful due to the graphical nature of the application and help clarify bugs. If you don't provide a screenshot, there's a good chance your bug will be rejected.
If you log a crash or Javascript error and don't provide Javascript console output the bug will be rejectedIf you do not properly document your bug reports, they will likely be rejected due to lack of information or documentation. Also, make sure your bug reports are reasonably general. If you submit the same bug that is seen in multiple screens, for instance, you will likely only get credit for the original bug report. The others will all be closed as duplicates.
You will log your tickets here: https://apps.topcoder.com/bugs/browse/HPBU
You must select the "TV Web Apps" component for each logged issue or it may not get counted during review.
For scoring, the submitter with the most points will win. For submitters who submit but don't win, if they submit bugs that aren't covered in the first submission, they will receive $5 for each unique bug reported up to a maximum of the 1st place prize
If two submitters submit the same bug report, the submitter who submitted the report first into JIRA will get credit for the bug. The second submitter will not.