Bug Hunt for a Mobile centric project

Challenge Objectives

• We have a React Native custom themed components with a website that serves as the documentation. For this contest, you will be testing if the custom components have any bugs and if the documentation is right.

• You will be carrying out unstructured testing. We don’t have any test cases and we are looking for bugs with the documentation as well as the custom components itself.

 

About the Application

There is no “app” to test. Instead, what you will be testing is

• Set of custom theme React Native components - A bunch of components that developers can use to create mobile apps in React Native.

• Documentation for the custom components - Developers will use this documentation and understand how to use the custom components to create mobile apps in React Native.

 

Assets

• A single code base that contains the custom theme components as well as the documentation for them

• Designs for the custom theme component. You can cross check the components in the code base against the designs and raise issues about design mismatch

 

What to test / What’s in scope

• There are two parts of the code base. One is a React Native custom theme components. The other is documentation for the components.

• For the custom theme components, you will follow the instructions on how to include the components in your React Native app in the documentation. You will have to go through each component individually, implement them, test them on an actual mobile device and report any issues you discover with the components. The issues that you raise could be:

  • Components not displaying properly. Any mismatch with the design can also be reported here.

  • Props of the components not working as documented

• For the documentation itself, you can report issues related to:

  • Spelling mistakes. Please create a single ticket for this - kindly do not raise multiple typo issues in multiple tickets.

  • Mismatch between the designs and the documentation website.

• Only iOS and Android devices will be supported for the custom theme components. Additionally, you can use Expo to test the components in your devices.

• The documentation website itself can be viewed on Google Chrome and IE11+ browsers.

 

How to create a Bug Report

• The repository where you will raise new issues is located here.

• Create new issue only in the link mentioned above. There is a template provided when you create a new issue. Follow the template and provide as much info as you can for us to reproduce the bug.

• It is strongly recommended that you share your code that resulted in the bug. You don’t have to share the entire code base, just a snippet of the main code will be enough

• Provide screenshots of the issue as much as you can.

 

Important Note

• Unlike other Bug Hunts, for this project, you will have to actually write code yourself and report bugs. This is because what you are testing is similar to a SDK and thus, only on implementing it, you will be able to come across bugs

• Incomplete information in a ticket or instructions and information provided in a ticket that does not help us reproduce the issue reported will result in that ticket being closed and considered invalid.

• Only bugs to be raised. Kindly do not raise any enhancement tickets.

• Duplicate bugs will not be considered. Only the ticket that first raised the bug will be valid.

• Only create issues until the submission phase. After that, any issue logged will not count.

 

Issue Scoring

• There are no weights for tickets. We welcome them all. We will check the severity of the issue reported and decide if a ticket is valid or not. It is at our discretion only whether to consider a ticket as valid or invalid.

• First place will be awarded to the member with the highest number of valid tickets. Second place to the member with the second highest number of tickets.

• Members that don’t get the first or second place but have raised valid tickets will be paid $7 per ticket with the total payment made to a member not exceeding the payment awarded to the second place member.

Final Submission Guidelines

Submit all your bugs directly to GitLab. When you are done with your submissions please submit a .txt file using the “Submit” button before the submission phase ends. In this file include:

• Your topcoder handle
• Your gitlab handle, which you used to raise the issues.

Submit the above details before the Submission Phase ends. 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.