Liberty Unstructured/ Exploratory Bug Hunt Challenge

Hello Topcoders! Welcome to the Liberty Unstructured/ Exploratory Testing Challenge. This is a Bug Hunt style competition.

If this is your first competition on Topcoder do not fear - we have all the instructions, you need to participate in this challenge specification and in the challenge forums.
Click the register button on this page to sign up, and then you’ll be granted access to the challenge forums where you can find documentation and ask questions.

IMPORTANT - This challenge has more than one prize placement! Prizes will be awarded to the top 3 scorers as follows:
1st place: $600 | 2nd place: $300 | 3rd place $200

ABOUT THE APPLICATION

Liberty is a web application focused on providing financial solutions for individuals, families, and businesses. In this web application, there are various types of tools and info about how customers can get those facilities and services. 

Most of the users who use the site have knowledge of Insurance domain and generic users who have Insurance policies.

Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!

 

WHAT TO TEST

Perform the testing as best you see fit. Approach the application as if you were an end user. The list below contains some types of issues you may want to search for:

In this test cycle, you have to identify the valid UI and functional issues of the application. We are accepting UX suggestions for scoring. But UX suggestions will not be paid.���

• Test URL: http://www.liberty.co.za
• Scope: Pages to be tested are only that are within the main domain (eg: liberty.co.za). Pages apart from the main domain will be rejected.
• Primary target device: Desktop, All mobile and tablet testing are in scope
• Browser Requirements: Latest Google Chrome, Firefox, Safari and Internet Explorer (Edge) on Windows/macOS.
• IE11 and below versions are out of scope.  
• Important: Because you are testing a live website DO NOT send data via contact forms.

HOW TO LOG TICKETS

1. Create an account on GitHub (if you do not already have one): http://www.github.com
2. You can get access to the GitHub repo using ‘Self Add to repository’ tool specified in the challenge forum thread to create new bugs.
3. There is an issue template whenever you click New Issue in Github. Please use this template. Log issues here: https://github.com/topcoderinc/liberty-life-qaas/issues
4. Please label issues with the appropriate browser type and mode, bug type, and platform type.  The labels can be viewed here: https://github.com/topcoderinc/liberty-life-qaas/labels

ISSUE REPORTING GUIDELINES

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

1. URL where the bug is occurring. (You can copy paste the URL from the browser address bar)
2. Steps to reproduce, including any needed information
3. Current results before the bug is fixed
4. Expected results, after the bug, is fixed
5. Screenshots/Videos/Console Logs
6. Attach the high-level labels. 
7. Attach detailed platform, device, operating system, Frequency and browser version information in the issue detail.  The high-level labels aren’t sufficient for issue replication and diagnosis.  

ISSUE WEIGHTS

1. Functional Issues - 10 points
2. User Interface Issues - 2 points
3. UX Issue - 1 point

IMPORTANT NOTICE

• Follow the standard Topcoder Bug Hunt Rules
• If you do not properly document your bug reports, they will likely be rejected due to lack of information or documentation. If you submit the same bug in multiple areas, for instance, you will likely only get credit for the original bug report. The others will all be closed as duplicates.
• If you duplicate an issue on a platform or browser that hasn’t been tested yet, you should create a new issue and add a link/reference in the issue description to the existing issue number. Our copilot will review these items and consolidate them later. Please don’t make adjustments or change labels of existing issues logged by other developers.
• You must not edit the bug report once created, so make sure you enter all the details at the time you create the issue, otherwise, your issue will be moved to the end of the queue. If you really need to edit an issue you must use the comments section for this (i.e. add a comment to describe any changes you want to make to the issue), and we'll decide whether the changes are major enough to move the issue to the end of the queue. You are allowed to add screenshots in the comments section though, assuming your issue report contains all the details when created.

SCORING

• Scoring will be based on the number of bugs by weight.  Be sure to correctly attach a weight to your bug.  The delivery team has the right to change a severity at their discretion.
• Scoring is directly proportional to weight:  Weight 1 = 1 point, Weight 10 = 10 points.
• The participant with the highest score will win the 1st place - $600 the member who gets the 2nd most points will win $300 and third place will win $200.
• Only verified issues will be counted.  Tickets logged for enhancements or non-bug issues will not be counted. Duplicate issues will be closed 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, 2nd, or 3rd place will be paid $5 for each non-duplicate and verified issue up to a maximum of the 3rd place prize. If two users submit the same issue, the user that submitted the issue first will receive credit.

TIPS

Some of the tips helpful for the contest:

• 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.
• Keep an eye on the issues being submitted by other participants 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 the creation of any necessary data.

Final Submission Guidelines

Submit all your bugs directly to Github. When you are done with your submissions please submit a .txt file to Topcoder Online Review using the Submit to this Challenge button. In this file include:

• Your name

• Email address

• topcoder handle

• Github handle used to raise the issues.