Challenge Overview
The new [topcoder] site has done some series of challenges that refactored the site to to use angular/javascript instead of some calls happening in PHP and some in and some in javascript in the current implementation. One of the already refactored page is the Challenge Listing pages, and we would like to compare this page against the pages currently in the production.
Challenge Objective
We want to check for bugs and figure out where the behaviors of the page differ from the current challenge listing pages in significant ways.
You need test the challenge listing pages on both list view and grid view against the refactored pages, these are:
1) All Challenges
- http://www.topcoder.com/challenges/ vs http://tcqa1.topcoder.com/challenges/
2) Design Challenges
- http://www.topcoder.com/active-challenges/design/ vs http://tcqa1.topcoder.com/challenges/design/active/
- http://www.topcoder.com/past-challenges/design/ vs http://tcqa1.topcoder.com/challenges/design/past/
- http://www.topcoder.com/upcoming-challenges/design/ vs http://tcqa1.topcoder.com/challenges/design/upcoming/
3) Development Challenges
- http://www.topcoder.com/active-challenges/develop/ vs http://tcqa1.topcoder.com/challenges/develop/active/
- http://www.topcoder.com/past-challenges/develop/ vs http://tcqa1.topcoder.com/challenges/develop/past/
- http://www.topcoder.com/upcoming-challenges/develop/ vs http://tcqa1.topcoder.com/challenges/develop/upcoming/
4) Data Science Challenges
- http://www.topcoder.com/active-challenges/data/ vs http://tcqa1.topcoder.com/challenges/data/active/
- http://www.topcoder.com/past-challenges/data/ vs http://tcqa1.topcoder.com/challenges/data/past/
- http://www.topcoder.com/upcoming-challenges/data/ vs http://tcqa1.topcoder.com/challenges/data/upcoming/
Browser Requirements
The refactored page must be tested in all mainstream browsers.
- IE10
- IE11
- Latest Safari
- Latest Firefox
- Latest Chrome
- Browsers in phone and tablet (like iPhone, iPad etc)
Ticket Logging
We will be using GitLab as the issue management, here's the outline of the process:
- You will need to create an account in GitLab if you haven't had yet
- Once you register for this challenge, send us GitLab login to nhastings@appirio.com and to jamesmarquez@gmail.com
- We will add you to the developers group on a repo in GitLab. This will give you access to work on issues, create branches, and pull requests.
- We will send you the "rules of the road" outline below in a response email.
Scoring
- [topcoder] will compensate members with first submissions.
- The winner will be the member with the most accepted reports of valid bugs.
- For non-winning members, there will be a $5 prize for each valid bug found that isn't in the winning submission.
- 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.
Final Submission Guidelines
For each significant differences, we need the following information:
- Detailed description of the bug or at least a description that make sense
- Steps to reproduce, including any needed information
- Screenshots or screencasts
- Expected results
- Current results
- Browser and 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.
- You need report your issues in GitLab and you MUST submit a text file with a list of your reported bugs into OR during the submission phase, for review purposes. If you do not do this, you will not get credit for any logged bugs!