Challenge Overview
Project Overview
Lycoming Engines is seeking a redesign of the existing website (http://www.lycoming.com). The goal is to refresh the design, modernize the home page, and focus on usability. A key focus of the site should be the support and technical publications, while maintaining focus on the main products - engines and parts.
We have properly recreated the new Lycoming Engines website based on DotNetNuke Framework.
Contest Objective
The goal of this competition is to clearly identify all issues for the new Lycoming Website.
Things to test in the current competetion are:
- Verify the page layout in the required browsers
- No Spelling or Grammar problems need to report, the content is not finalized.
- Please take the Storyboards as Reference
- Please cross reference content to the real Lycoming website - http://www.lycoming.com/
- Odd behavior to the testing . This falls into user experience testing and is just as vital as other issues. This is a very loose form of testing and we will evaluate on a per case basis.
- Please keep a journal or a matrix of what they tested/reviewed, and submit in Online Review.
Browser Requirements
The given application must be tested in all mainstream browsers as following:
- IE7+
- FireFox 5+ Mac & PC
- Safari 5+ Mac & PC
- Chrome (latest) Mac & PC
VM to Test
A Demo VM is created for readonly access, the VM IP will be posted after contest start. Please visit http://vm-ip-address/ to access the DNN.
To do sofisticate testing, each member can request there own VM with Lycoming website setup, so you can access the admin panel for changes,
for adminitration, plese use host / B3anC0uN73r to login via http://vm-ip-address/login.aspx. The latest submission is provided in forum for reference.
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.
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.
Technologies
- .NET
- DotNetNuke Framework
- HTML
- JavaScript
- CSS
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 (if applicable)
- Expected results after the bug is fixed
- Current results, before the bug is fixed
- Browser version
- Because of the language barrier at times, you take a movie showing the issue at hand If needed for better understanding.
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/LWRBH
Scoring
The Scoring guidelines followed for the contest are given below:
- For scoring, the submitter with the most accepted bugs will win. The submitter with the second most accepted bugs will receive second place.
- For submitters who submit but don't take first or second, 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 the 2nd place prize.
- In order to get the full place prize, submitter should have 5 accepted bugs at least.
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.
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.
Final Submission Guidelines
Submission Deliverables
You need report your issues in JIRA. Please submit a text file contains the bugs you reported to OR.
Final Submission
- 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.