Challenge Overview
Note: this challenge will have 24h for registration (during this phase no one will see details) and then 24h for bug hunting.
For the submission page, it needs 3 files,
1- the submission file, a zip with a bunch of images inside, in whatever folder structure they want, up to 500 Mb
2- a Source file, which is usually a photoshop file, up to 500mb as well
3- a preview image
We are not going to prepare these files, you need to create fake ones for testing pupose.
Scope to Check With
This is going to test the general submission flow, anything related to UI will not be considered as valid issue.
for the general process,
#1 we open up and generate alternate images from it, so that is the most important one
#2 we don't do much, we just zip it inside a unified zip
#3 we also generate alternate representations, and we copy it in the unified zip
You need to check that
- people are supposed to receive 2 emails:
1- when the submission finishes uploading
2- after the processing is complete with either an success or error message
- they should be able to see the submission in OR if it was successful
- they should be able to see the submission in Studio if it was sucessful
Contest Guidelines
The guidelines for this contest are given below:
1. As issues are identified they need to be logged on github: https://github.com/appirio-tech/topcoder-app/issues, please label your issue using submission-service
2. Issues must include clear descriptions, test cases and steps to reproduce and expected vs. actual results in order to be counted, Please take screenshots or screencast when available, it is good for issue verification. you can attach images in issue or using www.screencast.com, For test files, if it is too big, you can upload to dropbox or google drive, and include these in your submission in Online Review.
3. First competitor to find an issue gets credit, duplicates will not be counted.
4. Reviewers will accept, reject or mark the issues as duplicate.
5. Please DO take a look at the reported issues, duplicated bugs cost your work time and the reviewer's time.
6. We'll decide whether a bug is valid or not based on our knowledge about the app, it's totally up to us.
7. Please focus on functionality testing based on the requirements, all bug reports based on your own assumptions will be rejected.
8. Please focus on functionality issues, see Scope section above, really trivial issues like typos, missing comma or period in sentences, very minor UI issues will likely get rejected.
9. You must not edit the bug report once created, so make sure you enter all the details at the time you create the issue, otherwise your issue will be move to the end of the queue. If you really need to edit an issue you must use comments section for this (i.e. add a comment to describe any changes you want to make to the issue), and we'll decide whether the changes are major enough to move the issue to the end of the queue. You are allowed to add screenshots in the comments section though, assuming your issue report contains all the details when created.
Important Notice:
You must also be the first person to report the issue and submit it while submission phase is open. github will allow you to file issues before and after the submission phase, but these will NOT be counted.
Contest Prize Eligibility
The submitter with the most accepted bugs will win the contest.
Final Submission Guidelines
Bug Report Process
Bug Report Format
For each report of a limitation or bug, we need the following information:
1. Steps to reproduce, including any needed information
2. Screenshots or Screencasts (required)
3. Expected results after the bug is fixed
4. Current results, before the bug is fixed
5. Browser version and OS version
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.
Scoring
For scoring, the submitter with the most accepted bugs will win.
For submitters who submit but don't take first place, 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 github will get credit for the bug. The second submitter will not.
Tips
1. 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.
2. 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.
3. 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
You need report your issues in github. Please submit a text file contains the bugs you reported to OR.
Final Submission
For each member, the final submission should be uploaded via the challenge detail page on topcoder.com.
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.