Challenge Overview
Our client wants to build new application named "Lock My Laptop" which will leverage Bluetooth pairing on a mobile or other Bluetooth device, and automatically lock the workstation when the Bluetooth signal is lost. In simpler terms, the user can walk away from their workstation and know that it will lock automatically once their device is out-of-range. The device can be any Bluetooth device already paired with their computer (wearables, smartphone, tablet, wireless headphones, etc). The application will be a desktop application for multiple operating systems.
The goal of this challenge is to test "Lock My Laptop" Java application. You will also need a device with Bluetooth.
You may test the application on Windows 7 and (Unix) RHEL6.x , Ubuntu 14.04.
The application is used to lock the laptop if the user goes away from the computer. The user will start the application, start Bluetooth on his device and pair it with the computer, then enable locking in the application. If the user goes away from the computer with his device, the Bluetooth connection will be lost and the application will lock the computer. This is the basic usage of the application. Because our initial documentation is quite out of date, the application should be tested based on common sense.
You can find in application's FAQ section more information about how the application should work.
Contest Guidelines
The guidelines for this contest are given below:
- As issues are identified they need to be logged in JIRA.
- Issues must include clear descriptions, test cases and steps to reproduce and expected vs. actual results in order to be counted.
- First competitor to find an issue gets credit, duplicates will not be counted.
- Reviewers will accept, reject or mark the issues as duplicate.
- Please DO take a look at the reported bugs, duplicated bugs cost your work time and the reviewer's time.
- Please focus on functional testing with the actual device interaction, also testing scenarios when the application is closed and started again. The bug reports on typos, spelling errors and any trivial issues like this will be merged into one issue for every competitor. Note that the anti-aliasing problems are known, so don't report issues about this aspect.
Important Notice:
You must also be the first person to report the issue and submit it while submission phase is open. JIRA will allow you to file issues before and after the submission phase, but these will NOT be counted.
Final Submission Guidelines
Bug Report Format
For each report of a limitation or bug, we need the following information:
- Steps to reproduce, including any needed information
- Screen shots (if applicable)
- Expected results after the bug is fixed
- Current results, before the bug is fixed
- Please log only one issue per JIRA ticket.
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 here: https://apps.topcoder.com/bugs/browse/LMLBH.
Scoring
- For scoring, the submitter with the most accepted bugs will win. There's no second place winner.
- 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 JIRA will get credit for the bug. The second submitter will not.
Some of the tips helpful for the contest are:
- 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.
- 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.
- 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.
- For each member, the final submission should be uploaded to the Online Review Tool.
- 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.