Challenge Overview
Welcome to the "CRM - Billing Application Bug Hunt". This an application with both backend and frontend. Both of them will need to be verified for issues.
Note: this challenge will have 24h for registration (during this phase no one will see details) and then 48h for bug hunting.
Contest Objective
The purpose of this challenge is to thoroughly test the app's features on the required browsers. Please register to see details about the app so you can test it effectively.
IMPORTANT NOTICE:
- The following types of issues are being looked for:
- Bugs in frontend
- Bugs in integration
- UI/UX improvements
- Please tag as appropriate
Browser Requirements
- Desktop: Microsoft Edge, IE11 and Chrome Browsers (Mac & Windows). Minimum width for the frontend application is 1248px.
Contest Guidelines
1. As issues are identified they need to be logged on Github, you can find the link to the Github page in the forum once you register.
2. Issues must include clear descriptions, test cases and steps to reproduce and expected vs. actual results in order to be counted.
3. The 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 bugs, duplicated bugs cost your work time and the reviewer's time.
6. We'll decide whether a bug is valid or n`ot based on our knowledge about the app, it's totally up to us.
7. Please thoroughly test the app and find all kinds of issues, however, we’ll award different prizes for different types of issues (see the scoring section for details), the reviewer will decide which type each belongs to during the review phase.
8. Functionality testing must be based on the requirements, all bug reports based on your own assumptions will be rejected.
9. Our expectation from Members is that they will report bugs on different browsers/ platforms under the same ticket if they have means to test it. Members should not be creating separate tickets for the same repeating bugs for separate platforms/browsers. In such a case it's totally up to us whether to accept the bug or not.
10. 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 moved to the end of the queue. If you really need to edit an issue you must use the 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 the submission phase is open. Github will allow you to file issues before and after the submission phase, but these will NOT be counted.
Provided Resources
The following documentation will be available in the contest forum:
1. Source code for both frontend and backend
2. Requirement documents
Contest Prize Eligibility
The submitter with the most accepted bugs will win the contest.
Final Submission Guidelines
1. Bug Report ProcessBug 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 Screen Capture (required)
3. Expected results after the bug are 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 a 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.
2. Ticket Logging
You will log your tickets in the specified Github repo.
3. Scoring
For scoring, the submitter with the most accepted bugs will win 1st place.
For submitters who submit but don't take the top place, if they submit bugs that aren't covered in the top 2 place submissions, they will receive a prize of $5 for each unique bug reported up to a maximum of the second-place prize.
If one member tests and report issue in one OS, the member is supposed to test the same issue in all mainstream browsers in that OS, specifically:
- Windows: Edge / IE11 / Chrome
- Mac OS: Chrome
Our expectation is this member should file bugs for all the remaining platform/browser, if he has means to do it. (Assumption is member filing the repeating bug, has not filed any matching bug for separate platform/ browser already. In such a case we will reject it.)
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.
4. Tips
a) 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.
b) 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.
c) Double-check your steps to reproduce and test cases to make sure they are clear. Make sure your steps include the creation of any necessary data.
5. Submission Deliverables
You need to report your issues in Github. Please submit a text file contains the bugs you reported to OR.
6. Final Submission
For each member, the final submission should be uploaded via the challenge detail page on topcoder.com.