Challenge Overview
Project Overview
LightSpeed is an Excel based VBA application and in this project we are converting this application to a web based app to make it much easier to use. The web app will be an HTML5 app with offline capabilities.
Contest Objective
The goal of this competition is to test some specific features of the app and see if there are bugs in these areas.
Things to test in the current competetion are:
- The new project forecasting tab:
- Make sure all columns from the excel app are implemented in this web app
- Make sure edits in this new tab are captured by the "Edits Summary" pop up
- Make sure notes and comments are saved to the server instead of browser cache (i.e. you can clear browser cach, login again and still see the data)
- Please focus on functionality testing, we don't need reports of really trivial issues like typos, spelling errors, etc...
- No unexpected errors occur
- Test both online and offline mode
- Works in different browsers (see below for a list)
Browser Requirements
The given application must be tested in IE 10+, latest version of Firefox / Chrome / Safari (Mac Only).
Users
Please log in with your own handle as a normal user (you must enter all files to login). To change permissions login as "admin". But please only use "admin" to test admin only features.
Contest Guidelines
The guidelines for this contest are given below:
- As issues are identified they need to be logged in GitLab.
- 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.
- The copilot / reviewer will make the decision whether a bug is valid or not
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.
Technologies
- Java
- Angular.js
- HTML5
- Postgres
- Javascript
Provided Resources
Documentation Provided
The following documentation will be available in the contest forum:
- Requirements
- Source code
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:
- Steps to reproduce, including any needed information
- Screen shots (required)
- Expected results after the bug is fixed
- Current results, before the bug is fixed
- Browser 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.
Ticket Logging
You will log your tickets here: https://gitlab.com/huangqun/lightspeed/issues and when creating a bug you MUST select the Project Forecasting label. Bugs will not be counted if a selection is not made.
Scoring
- For scoring, the submitter with the most accepted bugs will win.
- For submitters who submit but don't take first, if they submit bugs that aren't covered in the first or second place submission, they will receive $5 for each unique bug reported up to a maximum of half of the 1st 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
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.
Submission Deliverables
You need report your issues in GitLab. 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.