Challenge Overview
Project Overview
The Goal of this application is to render the new record retention policy information in a matter consistent with a newly devised records retention schedule (RRS) currently in a MS Access format. Part of the scope of this project will include the translation of the a data model as reflected in the above referenced Access DB into a Salesforce compatible logical model that will ultimately drive the functionality and facilitated the maintenance of the above referenced schedule.
Finally the app requested will to provide a more intuitive user experience for any company employee who needs to search, access and consume any IAM related information specifically records retention data, selected “admin” users will have the ability to create new record retention categories as well as modifying retention periods per legal requirements.
Contest Objective
The goal of this competition is to clearly identify the limitations of the provided assemblies and ensure the requirements as they were described have been met. You can find the documents describing the applications in contest forum.
Things to test in the current competetion are:
- Make sure the application works as describe in the requriements document
- Make sure all features on the UI works properly
- Make sure the application works on different browsers
Browser Requirements
The given application must be tested in all mainstream browsers.
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.
- Pay attentions to issue granularity, for example: if you find 5 typos on UI and report them as 5 different issues, only one will be considered valid.
- 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
- Salesforce.com
- Apex
Provided Resources
Documentation Provided
The following documentation will be available in the contest forum:
- Requirements Document
- Deployment Guide
- 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 (if applicable)
- 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://apps.topcoder.com/bugs/browse/SROSBH
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.
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.
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.