Challenge Overview
Overview:
The Hercules Player is an application that allows customers to download videos to their computer or device for offline playback, along with streaming playback of videos for online playback.
We have forked a new version of the app for VOD (Video on Demand) that will allow people to select videos for playback in the app, and view live TV.
The new version of the app will be used on browser-based versions of the application, as well as wrapped in native code and used as the iOS, Android versions, leading to a single HTML5 codebase that covers all platforms. This bug hunt will only test the streaming site, which is the browser based version of the application.
Contest Scope
The goal of this competition is to clearly identify the limitations of the provided application and ensure the functionality of the app works as expected, specifically focusing on the new search functionality, although the rest of the application is still in scope.
Things to test:
- Functionality without Flash installed. Flash is key to the application, so users should be redirected to install the plugin
- The functionality works desktop browsers.
- The display is correct
- Navigation works
- Scrolling works
- Closed captioning (CC button on playback)
- Parental controls
- SAP (SAP button on playback)
- Different OS's and browsers, including IE, FF, Chrome, and Safari
 |
Please ensure performance is good. SAP, CC, and parental controls are of particular interest to the client, and there are bugs there, so please make sure to test those items fully |
Known issues:
Do NOT log issues for these:
- Missing periods or tooltips are not in scope
- Login page is not in scope
Final Submission Guidelines
Platform
This bug hunt will only test the browser based version of the app. Please use different browsers to test, primarily IE 9+, FF, Chrome, and Safari.
Screenshots
Note that for every bug you assign to a specific OS, you MUST provide a screenshot for that platform. This is a requirement to ensure proper test coverage on each platform. For instance, if you assign a bug to Windows and OS X, but you don't provide a screenshot for OS X, the bug will be rejected.
Parental controls
Parental controls are used to restrict access to videos for parents of children. The parents can choose to enter a pin and then restrict specific TV or movie ratings. If a parent wants to view a show or channel that has been restricted, they can enter the pin and will be allowed access. Note that on the "Guide" page, shows can be recorded without the pin, even if the show is not allowed by parental controls. Shows can also be downloaded to a device that may be outside the restrictions on the parental controls, but the user shouldn't be able toplay the downloaded or recorded resource without entering the parental control pin.
Users
Login with the user accounts found in the forum.
The parental control pins should be set for these already to 1597 or 2222
Scope
The login page is out of scope. Also, any tooltip or minor punctuation errors won't be accepted.
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
5) OS version (Mac, Windows)
6) Browser type and version
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 and don't provide a crash log, the bug will be rejected |
|
If 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.
NOTE: There will be simultaneous bug hunts running at once for the different platforms. You must not duplicate the same issue for multiple platforms. Just select multiple components (ie. Windows Client and OS X client) on the single ticket. Duplicates logged without doing this will be ignored. |
You will log your tickets here: https://apps.topcoder.com/bugs/browse/HPBU
You must select the "University Web Client" component for each logged issue or it may not get counted during review.
|
For scoring, the submitter with the most pints will win. The submitter with the second most points will receive second place. For submitters who submit but don't take first or second, if they submit bugs that aren't covered in the first or second place submission, they will receive $5 for each unique bug reported up to a maximum of the 2nd 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. |
OR Submission
You MUST submit a file with a list of your reported bugs into OR during the submission phase, for review purposes. If you do not do this, you will not get credit for any logged bugs!