Challenge Overview
A Large IoT and Power Management Company would like to consolidate all of their employee technical competency into a single tool which can be used to track at multiple levels. The goal is to have an application that allows CoE leaders to define roles with their competency requirements, and actions or trainings which prove each competency level. Managers and Directors will be able to track profiles with roll-ups of competency in specific sections of the workforce.
** This Challenge is a Bug Hunt Challenge **
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 to thoroughly test the app's features using both backend and electron application. Please register to see details about the app so you can test it effectively.
Technical Stack
- Fronted: Electron app
- Backend: Node.js + MSSQL (will provide URL in forum)
Contest Guidelines
1. As issues are identified they need to be logged on gitlab, you can find link to the gitlab page in the forum once you register (after the 24h registration period).
2. Issues must include clear descriptions, test cases and steps to reproduce and expected vs. actual results in order to be counted.
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 bugs, 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 thoroughly test the app and find all kinds of issues, however we’ll award different prizes for different types of issues (see scoring section for details), the reviewer will decide which type each belongs to during 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 are that they will report bugs on different browsers/ platforms under same ticket, if they have means to test it. Member should not be creating separate tickets for the same repeating bugs for separate platform/ browser. In such 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 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. GitLab 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 electron app) and backend
2. Requirement documents and deployment guide
3. Backend url
Contest Prize Eligibility
The submitter with the most accepted bugs will win the contest. The second submitter with most accepted bugs will receive 2nd place.
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. Screen shots (required)
3. Expected results after the bug is fixed
4. Current results, before the bug is fixed
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.
Ticket Logging
You will log your tickets in the specified GitLab repo.
Scoring
For scoring, the submitter with the most accepted bugs will win 1st place. The second submitter with most accepted bugs will win 2nd place.
For submitters who submit but don't take the top places, 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 2nd place prize.
Important Notice:
If two submitters submit the same bug report, the submitter who submitted the report first into GitLab 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 GitLab. Please submit a text file contains the bugs you reported to OR.
Final Submission