Challenge Overview
The Retail 360 iOS App is a tool used by Hercules employees in their retail stores. The app allows for looking up customer details and will eventually contain lots of functionality for managing customer accounts, making changes to their accounts, and adding notes, sending emails, etc...
We have released version 1 of the app to some employees, and version 2 is nearing completion. As we add more and more functionality, we need to ensure that the existing functionality isn't broken by any new changes.
This challenge will implement UI tests for the new Time Trade functionality in the "Check-In" tab.
Requirements:
Recently, we have implemented queue and appointment functionality on the "Check-In" tab. This challenge will implement UI unit tests to cover:
* Adding, updating, starting, and completing queue items
* Creating, rescheduling, updating, canceling, and checking-in appointments
Your tests should ensure proper flow through the UI using mock data, and they should ensure that validation exists for all required fields and that optional fields are truly optional. Your tests should use configured data but real service calls and should test that the data added matches the UI display.
Environment:
For this challenge, we will only use the Develop target in XCode. Please ensure that your tests and test data follow the existing structure for the other tests.
Coverage:
Proper coverage is required, of positive and negative test cases. The reviewers should ensure that the coverage report can be run and that the coverage % is appropriate for the functionality tested.
Any existing tests that fail are out of scope.
Helpful links:
* https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/testing_with_xcode/chapters/09-ui_testing.html
* https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/testing_with_xcode/chapters/07-code_coverage.html
* http://cleanswifter.com/measuring-swift-code-coverage/
* https://developer.apple.com/videos/play/wwdc2015/410/
* http://mgrebenets.github.io/mobile%20ci/2015/09/21/code-coverage-for-ios-xcode-7
A separate UNIT_TESTS_README.md exists in Git. It should be updated for this challenge.
Video
No video is required for this challenge
We have released version 1 of the app to some employees, and version 2 is nearing completion. As we add more and more functionality, we need to ensure that the existing functionality isn't broken by any new changes.
This challenge will implement UI tests for the new Time Trade functionality in the "Check-In" tab.
Requirements:
Recently, we have implemented queue and appointment functionality on the "Check-In" tab. This challenge will implement UI unit tests to cover:
* Adding, updating, starting, and completing queue items
* Creating, rescheduling, updating, canceling, and checking-in appointments
Your tests should ensure proper flow through the UI using mock data, and they should ensure that validation exists for all required fields and that optional fields are truly optional. Your tests should use configured data but real service calls and should test that the data added matches the UI display.
Environment:
For this challenge, we will only use the Develop target in XCode. Please ensure that your tests and test data follow the existing structure for the other tests.
Coverage:
Proper coverage is required, of positive and negative test cases. The reviewers should ensure that the coverage report can be run and that the coverage % is appropriate for the functionality tested.
Any existing tests that fail are out of scope.
Helpful links:
* https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/testing_with_xcode/chapters/09-ui_testing.html
* https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/testing_with_xcode/chapters/07-code_coverage.html
* http://cleanswifter.com/measuring-swift-code-coverage/
* https://developer.apple.com/videos/play/wwdc2015/410/
* http://mgrebenets.github.io/mobile%20ci/2015/09/21/code-coverage-for-ios-xcode-7
Submission format
Your submission should be provided as a Git patch file against the commit hash mentioned in the forum. MAKE SURE TO TEST YOUR PATCH FILE!
Your submission should be provided as a Git patch file against the commit hash mentioned in the forum. MAKE SURE TO TEST YOUR PATCH FILE!
A separate UNIT_TESTS_README.md exists in Git. It should be updated for this challenge.
Video
No video is required for this challenge