Hercules Personal Content DVR iOS Unit Tests - Album tests

The Hercules Personal Content DVR application will be used to expand the Hercules Player app, allowing users to upload their own video content they recorded on their iPhone or iPad camera into their DVR for playback on their TV and syncing with other devices.

This competition will implement Kif tests for the standalone version of the app.

This is the first test case competition for this particular application, so it will lay the groundwork for future competitions.

Test scenarios

The forum contains test scenarios and an ARS.  We are going to implement functional test cases listed below.

Note that the test cases must cover iPhone / iPad

https://developer.apple.com/library/ios/documentation/ToolsLanguages/Conceptual/Xcode_Overview/UnitTestYourApp/UnitTestYourApp.html

Simulator testing

Changes have been made to the codebase to ensure it runs in the simulator.  The app in the simulator is configured to login with "test/test" - anything else will show an invalid username and password.  Once logged in, the app in the simulator will display information and albums for cdvrfox3.

Existing tests

If any existing tests are failing, this contest must fix them up to comply with the latest code, where appropriate.  If a failing test is a bug, not just a change in the functionality, please report it in the forum.  You won't be expected to fix the test case in that instance.

Required test cases

• 53
• 34
• 55
• 56
• 57
• 58
• 63
• 64
• 65
• 66
• 67
• 68
• 71
• 72
• 73
• 74
• 75
• 76
• 77
• 78
• 79

 

Versions

Please target OS X server 10.9 and XCode 5.

KIF

We use the KIF framework for the tests:

https://github.com/kif-framework/KIF

Naming convention

Please make sure the name of the test includes the test scenarios number and a short description so we can easily see and reference what scenario exactly is failing during regression testing.

Conflicts

If there are any test scenarios that conflict with the existing code, we will follow the existing code, not the scenario.  Note that the login process has changed dramatically since the test scenarios were completed.  The app now has a native login screen and there are no longer the 3 welcome screens referenced in the scenarios.

Code modifications

You are allowed to modify the code to include accessibility elements to make unit tests easier, but you are *not* allowed to edit any functionality without approval in the forum.

Documentation

Step by step deployment documentation is critical for this application.  Your deployment documentation must be thorough and include clear setup information to aid the copilot and reviewers.

Test structure

Don't make any assumptions about existing data.  Your setup and teardown code should handle everything you need.  Running your tests should leave no residual data and you should randomly generate names for things to avoid conflicting with other tests that may be running on the same account.

Final Submission Guidelines