Live Well Android Mobile App Testing Challenge

Welcome to the “Live Well Android Mobile App Testing Challenge”. This is a Bug Hunt style competition focused on unstructured testing for “Live Well Android Mobile App”, an Android mobile application. This challenge will have a 24 hours pre-registration period so you can read and check the specifications before competing.

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.

Prizes:

This challenge has more than one prize placement! Prizes will be awarded to the top 3 scorers as follows:

Bonus:

- We will give $5 for unique bugs raised by each member if not in top 3.

ABOUT THE PROJECT

Live Well Android mobile app has been built and will be launched to all our customers to access cooking recipes, record fitness activities, etc.

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

 

Scope:

In this challenge you have to test the different functionalities featured on “Live Well”, an Android mobile application. There will be user stories provided as input in the challenge forum, but we expect testers go beyond user stories to do out of the box testing.

We are looking to concentrate on usability, i.e. all the normal things that should come out of User Acceptance Test, like spelling, font differences, pages not rendering, etc. Think yourself as the end user of the product and provide all suggestions to improve the usability, with little/no help from the client on the usage of the application.

Both Landscape and Portrait mode are in scope.

OUT OF SCOPE:

• Test case design/writing

• Performance testing (Concurrent users, Load testing)

• Mobile App-Certification testing like (Interruption testing, Low battery, Low memory, network switching, Multi tasking)

 

PRIMARY TARGET DEVICE(S):

• Android 7+ (Phone only)

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/pages, (for instance, Same validation issue of a form can be found in different pages/sections) you will likely get credit for the original bug report only. 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 competitors.

• DON'T RE-OPEN the issues in the review phase and anyone who RE-OPENS a ticket will be disqualified from the challenge.

• DON'T EDIT OR ATTACH FILES to the issues in the review phase and anyone who is doing this will be disqualified from the challenge.

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

• You must specify the test data you have used in the 'Reproduction Steps', All the issues will be marked as 'Incomplete', if the correct test data is not provided.

• There will be no appeals phase. The decision of PM/co-pilot for validity and severity of each filed issue will be final.

ISSUE WEIGHTS

• Functional Issues - 10 Points

• User Interface Issues - 4 Points

• Usability/UX Issue - 2 Points

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

FINAL SUBMISSION GUIDELINES

Submit all your bugs directly to Gitlab. When you are done with your submissions please submit a .txt file to Topcoder Online Review using the Submit to this Challenge button BEFORE the Submission phase ends. In this file include:
 - Your email address used for testing
 - Your topcoder handle
 

ALL THE SUBMISSIONS WITHOUT ABOVE INFORMATION WILL BE REJECTED AND WON'T BE PAID.

IMPORTANT: Submit the above details before the Submission Phase ends. If you can't submit due to technical difficulties within the Submission Phase please email your submission with above details to support@topcoder.com

- Participants who haven't submitted will not be paid

- DON'T use any other link to create new issues OR submit as document, they won't count and won't be paid.