Key Information

Register
Submit
The challenge is finished.

Challenge Overview

Project Overview

Video surveillance cameras show what is happening in a scene from a remote location. Cameras are connected to digital video recorders (DVR) to allow for the recording of the scene.
Cameras and DVRs have many features available such as pan / tilt / zoom (PTZ), capturing images, and motion detection.
The project will be a cutting edge mobile application camera viewing system. The main goal of the project will be to view live video in H.264/MJPEG format from multiple cameras and recording devices. User will be able to view video from mobile devices like:

  • Smartphones
  • Tablets

The purpose of this project is to develop an interface library for the graphical front end.  The library will serve as layer of abstraction between the user interface and the underlying device logic for video.  
Application will initially support one Interlogix brand recording device (LNVR) and needs to be architected in a way to allow for addition of different brand DVRs.

Contest Objective

The goal of this competition is to test the app built in this contest: http://community.topcoder.com/tc?module=ProjectDetail&pj=30040703

This is an ipad app and you'll need to have xcode and a device to actually test this. We'll provide the code in forum.

The app is supposed to implement the following from the application spec:

  • 3-Multi Camera View (Home Screen)
  • 3.1-Close Video
  • 3.1.1-Multi View Activity
  • 3.5-Opening Live Video
  • 3.5.1-Opening Live Video Activity
  • 3.6-Device Drag & Drop (Tablet)
  • 3.6.1-Device Drag & Drop Activity
  • 3.6.2-Camera Drag & Drop (Tablet Only)
  • 3.7-Tile Selection (Phone & Tablet)
  • 3.8-Multi-View Tile Layouts
  • 3.10.1-Close Video Activity
  • 3.13-Single View Layout
  • 3.14-Functional Menu Strip
  • 3.16-Capture Snapshot
  • 3.21-Close All Video
  • 4-Playback Layout

Contest Guidelines

The guidelines for this contest are given below:

  • As issues are identified they need to be logged in JIRA.
  • Issues must include clear descriptions, test cases and steps to reproduce and expected vs. actual results in order to be counted.
  • First competitor to find an issue gets credit, duplicates will not be counted.
  • Reviewers will accept, reject or mark the issues as duplicate.
  • Please DO take a look at the reported bugs, duplicated bugs cost your work time and the reviewer's time.
  • Please focus on funtional testing. We don't need bug reports on typos, spelling errors and any trivial issues like this, all such issues will be rejected and will not count

Important Notice:

You must also be the first person to report the issue and submit it while submission phase is open.  JIRA will allow you to file issues before and after the submission phase, but these will NOT be counted.

Technologies

  • iOS 7
  • iPad
  • xcode 5

Provided Resources

The following documentation will be available in the contest forum:

  • Test Scenarios
  • Application Spec
  • Source code


Final Submission Guidelines

Bug Report Process

Bug Report Format

For each report of a limitation or bug, we need the following information:

  • Steps to reproduce, including any needed information
  • Screen shots (if applicable)
  • Expected results after the bug is fixed
  • Current results, before the bug is fixed
  • iOS version / Device model

 Important Notice:

  • 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.

Ticket Logging

You will log your tickets here: https://apps.topcoder.com/bugs/browse/STYXBUGS and when creating a bug you MUST select the Styx Video App 2.0 iOS component. Bugs will not be counted if a selection is not made.

Scoring

  • For scoring, the submitter with the most accepted bugs will win. There's no second place winner.
  • For submitters who submit but don't take first or second, if they submit bugs that aren't covered in the first place submission, they will receive $5 for each unique bug reported up to a maximum of half the 1st place prize

 Important Notice:

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. 

Tips

Some of the tips helpful for the contest are:

  • Submitting what is obviously the same issue multiple times with small variations will only annoy the reviewer that has to sort through all the issues and will only count as one issue anyway. If it's less obvious if it is the same issue or not, use your best judgment and the reviewers will do the same.
  • Put an eye on the issues being submitted by other members to minimize the time you may be spending on duplicate efforts. Knowing what has already been reported will allow you to better focus your time on finding yet undiscovered issues.
  • Double check your steps to reproduce and test cases to make sure they are clear. Make sure your steps include creation of any necessary data.

Submission Deliverables

  • For each member, the final submission should be uploaded to the Online Review Tool.
  • You must not include any identifying information, such as your handle, in your submission. Your submission should be anonymous and you will be scored down in screening for not complying.

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30040704