Welcome to GE Pledge Tool - Bug Hunt Challenge!

In this challenge you are asked to find bugs and defects in a java web application.

Note that access to the website URL to test will be granted Saturday 12:00AM EST.

Challenge Task Overview

In this bug hunt you will focus on catching any issue that affects  functionality or rendering Pages/Styling properly for the users.

How/What to Test

- Use this test scenarios document to test the solution https://docs.google.com/document/d/1FJpxhzV_zjWtS6_rjN57R5ncUq4Fd7YB7YHchRYOPTI/edit

- Use this document to get users credentials (admin and non admin)  https://docs.google.com/spreadsheets/d/1Z8b411BxGdPCRwNw8OWNVzkKwRUQujuAb5Yv_XB1ODg/edit#gid=865366616

- This document is the original requirements document for you to understand the full functioanlity implemented https://docs.google.com/document/d/1n2Z6rSvhxOcC2V0bDGHQ_s4iIkmvuV6Riz4YJ2SdoaM/edit#

- Post questions in forums if there is anything not clear

Prize Structure

- Admin will review and approve/reject bugs.

- The submitter with highest amount of valid bugs reported gets the 1st place prize.

- The submitter with 2nd highest amount of valid bugs reported get the 2nd place prize $150.

- Any other submitter that did not win 1st/2nd place will get $5 per valid bug reported.

Rules to Find Bugs

We need you to hunt for the issues and report these issues to Github 

Github url : https://github.com/topcoderinc/GE-Pledge-Tool/issues
Use this label in your reported issues : https://github.com/topcoderinc/GE-Pledge-Tool/labels/bh-30054860 

All defects must include the following:

1. Environment (i.e. iOS version and Device model)

2. Steps to reproduce

3. Outcome vs. Expected Outcome

4. Screenshot or Video

5. Clear title/description

This bug hunt follows the standard bug-hunt contest rules, the one logs the max number of valid bugs win, and you should try to merge the similar issues in one bug (e.g. input box one page1 & page2 validation error should be counted as one same bug).

1. First competitor to find an issue gets credit, duplicates will not be counted.

2. Reviewers will accept, reject or mark the issues as duplicate.

3. Please do take a look at the reported bugs & known bugs list, duplicated bugs cost your work time and the reviewer's time.

4. If you have any questions or confusions let us know, via the forums

Please note:

1. Assigning the bug you report to yourself, it will simplify reviewing issues.

2. You will focus on Functionality following the requirements document, UI/Styling issues, and spelling issues.

3. We will not pay for duplicate bugs.  We will accept the first submitted bug, based on time in Github.  Please do not submit slight differences to try and get accepted. This will get you banned.

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

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

Browsers In Scope

- IE 11 (this is the main client browser)

- Latest Microsoft Edge, Chrome, Safari and FireFox.

- Safari and Chrome on iPhone, Chrome on Android.

 

Final Submission Guidelines

Final Submission Deliverables

You need report your issues in Github. Please submit a text file contains your github handle to Online Review, this is needed so we can process payment if you win.

Final Submission

For each member, the final submission should be uploaded to the Online Review Tool.