The goal of the challenge is to bug hunt Verigames website against IE browsers.

Read more about Verigames in this page https://www.verigames.org/about-us

Challenge Task Overview

The goal of this challenge is to identify all issues in the pages and functionality affected by this change.

The website to test is : http://www.verigames.org

Testing

• You should test the website against IE browser version 9, 10, and 11 in both “http” and “https” protocols.

• You are provided with test scenarios of the website, you will use them to test website pages, ui and functionality.

  • Some scenarios are outdated, please ask for confirmation about conflicts in forums.

• You need to register new accounts to use it for testing.

• You need to verify emails sent to users are rendered properly and the links are rendered correctly.

• Blocked and mixed content in https should be reported, i.e. all content should be loaded in https protocol when accessing website in https protocol.

This is staging website so we might have some misconfiguration that affect some functionality, you can report that to forums and Copilot will fix it so you can properly test.

Browsers in Scope

IE browser versions 9, 10, and 11

Website Link

Staging website link is : https://www.verigames.org

The games (to play a game) and the following minisites are out of scope :

• circuitbot.verigames.org

• xylem.verigames.org

• flowjam.verigames.org

• ghostmap.verigames.org

• stormbound.verigames.org

Conflicts

If there are any test scenarios that conflict with the deployed staging website application, we will follow the staging website, not the scenario. It will be better if you confirm conflict in challenge forums.

Existing Documents

Test scenarios are provided in challenge forums.

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.

• Members who submit duplicate reported bugs will lose 1 point/duplicate bug from their overall points.

• 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.

• Issues will be classified via points system :

  • 4 points for functionality issue.

  • 2 points for UI and styling issue.

  • 2 points for Content issue (i.e. mixed content)

  • -1 point if you submit a duplicate issue

  • -1 point for irrelevent and out-of-scope issue.

• The member who get most points will win first place prize plus $2 per point, others will get $2 per point.

Bug Report Format

For each report of a limitation or bug, we need the following information:

• Title must have a prefix tag with requirement name and case number.  i.e. [Home Page][29] <title of bug>

• Body of the JIRA should contain the following :

  • Test scenario number/name.

  • Protocol (https or http)

  • 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

Ticket Logging

You will log your tickets here: https://apps.topcoder.com/bugs/browse/CSFV and when creating a bug you MUST select the "IE Bugs" Bugs will not be counted if a selection is not made.

Scoring

The Scoring guidelines followed for the contest are given below:

• Issues will be classified via points system :

  • 4 points for functionality issue

  • 2 points for UI and styling issue.

  • 2 points for Content issue (i.e. mixed content)

  • -1 point if you submit a duplicate issue

  • -1 point for irrelevent and out-of-scope issue.

• For scoring, the submitter with the most accumulated points will win.

• All submitters will receive $2 per point for each point.

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 O

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.