Key Information

Register
Submit
The challenge is finished.

Challenge Overview

For this challenge, we'd like to do functional testing for Update Challenge API.

Background
Previously, we have updated the Update Challenge API to be able to update the needed field for existing challenges. the purpose of the challenge is to make sure the Update Challenge API is still functioning properly for various inputs.

Preparation For Test
The testing environment of dev environment, so you need to do the followings in order to prepare for testing.

1. Have an account in dev environment, if not please register a new account by visiting https://accounts.topcoder-dev.com/member/registration
2. After activating the account in dev environment, visit https://www.topcoder-dev.com/direct  to make sure you can create projects and challenges 
3. Get the v3jwt token which is needed when calling API from cookies - visit https://www.topcoder-dev.com/my-dashboard, if you are using Chrome, you can open the Developer Tools, and you can find the v3jwt token set for domain -  accounts.topcoder-dev.com

How To Test

- To be fair for all competitors, the real hunt will be started 24hrs after registration starting.
- An Swagger UI For testing against the Update Challenge API will be posted in forum, when the real hunt starts 

Bug Hunt Rules

For each of the issues you find, create an issue in github and make sure to follow the default issue template and include:

  • Steps to reproduce the issue, please provide the exact input to call the API
  • Expected results after the issue is fixed
  • Current results, before the issue is fixed
  • Screenshots or Video if needed

Before reporting, please re-check the existing issues to avoid duplicated reporting.  If there are duplicated reporting, the timestamp of the issue will be used to determine who owns the valid reporting.

Only verified issues will be counted. Entries logged for enhancements or non-bug issues will not be counted. Duplicate entries will be flagged and not counted. Log issues according to the guidelines above - issues that do not follow these guidelines may be rejected due to lack of information.

For challenge scoring, the user with the most verified issues will be selected as the winner. Submitters that do not take 1st place will be paid $5 for each non-duplicate and verified issue up to a maximum of the 1st place prize. If two users submit the same issue, the user that submitted the issue first will receive credit.
 

Final Submission Guidelines

-- Submit all issues into the GitHub issue tracker.
-- For completing the challenge, submit a text file containing your github account (so we can easily find the match with Topcoder handle and the github handle) and the list of reported issue.

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30058555