Challenge Overview
Welcome to the Android Testing Automation Tool Ideation challenge!
This challenge is related to the Code Coverage ideation challenge we’re running in parallel.
In this challenge, we need your creativity and expertise to come up with an idea of an automation tool that will automate the testing of a large amount (5000+) of Android applications with an acceptable code coverage using the Code Coverage tool from our challenge that’s running in parallel (https://www.topcoder.com/challenges/30062408/?type=develop&noncache=true).
The acceptance criteria for the code coverage will be determined by the results of the Code Coverage tool.
We prefer a custom implementation for this tool but open source tools are also welcome as long as they meet all requirements.
We are running an ideation challenge for the Code Coverage in parallel.
Check it out here: https://www.topcoder.com/challenges/30062408/?type=develop&noncache=true
Feel free to ask on the challenge forum if you have any question.
Target audience
-
Developers
-
Technical architects
Judging criteria
-
You will be judged on the quality of your ideas, the quality of your description of the principle(s) of the ideas, and how much benefit it can provide to the client.
-
You will also be judged on how clearly you describe your idea. The winner will be selected by the client, not the Topcoder review board.
The client will choose the winner with the most logical and convincing reasoning as to how and why the idea will meet the objective.
Note that since this is an ideation challenge, we are using the ideation scorecard and there will be no Appeals phase.
Organizing Your Submission
Your submission should be primarily or entirely textual, containing a detailed description of your idea, assumptions and use case scenario(s). Preferably one document, with three (3) sections:
-
Idea Details
-
Assumptions
-
Use Case Scenario(s).
My Idea: this section will detail your idea on how to solve this problem. Be sure to write up as much detail as possible, including (if applicable) technologies and devices used.
My Assumptions: this section will list the assumptions that you have made, in order for this system to work.
My Use Case Scenario: this section will detail at least one (1) use case scenario. A use case scenario is a walk-through example of how the idea would work in real life.
Note: we will buy any idea we like beyond the first three places for $250.