Challenge Overview
Challenge Objectives
-
Unstructured Test
-
Desktop site
About the Application
CFO forecasting app is used to display the historical and forecasted data and allow the user to drill down through the available data sets using various filters.
Assets
App url is posted in the forums - you don’t need to deploy it locally. User credentials are also posted in the forums.
What to Test (Scope)
In this challenge you have to test the login and forecast details and favourite pages. Edge is the primary browser for the application - we will accept Chrome & Firefox bugs too, but the primary focus is on Edge.
-
Exploratory testing should be done around all features of the forecast page - various groupings, date filtering, drill down selection filters.
-
Test the values displayed in the charts - forecast data (json) is posted in the forums. Note that for all dates, year reflect a fiscal year - starting April 1st and ending March 31st (also, first quarter is April-June, while fourth quarter is Jan-Mar). Also, note that all the values in the charts are simply the sum of all values in the period (all historical & forecast data is monthly data, so displaying yearly figures would be sum of all monthly values for the given fiscal year). Only exception to this are Closing base (value in the charts should be the value in the last month of the period) and Opening base (value in the charts should be the value in the first month of the period).
-
Accepted types of bugs: Functional, UI, UX
-
Primary target device(s): Desktop
-
Browser requirements: Latest Edge, Google Chrome, Firefox Windows. IE11 and below versions are out of scope. Safari on Windows is out of scope.
-
Content Bugs are OUT OF SCOPE
How to Create New Bug Report
1. Create an account on GitLab (if you do not already have one): https://gitlab.com.
2. You can get access to the GitLab repo using the url posted in the challenge forum thread to create new bugs OR If you are still getting 404 error, request access to the repo using correct forum thread.
3. There is an issue template whenever you click New Issue in GitLab. Please use these template to report your issues.
4. Issues/Bugs found in this application/App must create here:https://gitlab.com/cfo-qa/talaria-forecasting-qa/issues . DON'T use any other link to create new issues OR submit a document, they won't be counted and won't be paid.
5. Please label issues with the appropriate type (functional, UI, UX)
Issue Reporting Guidelines
For each report of a limitation or bug, we need the following information:
-
Steps to reproduce, including any needed information (Must list all the steps that need to reproduce the bug, DON'T list only the URL without test data)
-
Current result(s) before the bug is fixed
-
Expected result(s), after the bug is fixed
-
If it is a UI bug attach a Screenshots (Mark the area where the bug is) | Functional Bug - Videos (You can attach videos directly on GitLab, if not use services like www.screencast.com Don’t use www.youtube.com to host the videos) | Crash - Console/Crash Logs. | Performance testing - Support documents
Issue Weights and 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.
-
Only verified issues will be counted. Tickets created for enhancements or that are not bugs 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 reject due to lack of information.
-
For challenge scoring, the user with the most points will be selected as the winner. If two users submit the same issue, the user that submitted the issue first will receive credit.
-
Please focus on functionality/UI testing based on the requirements, all bug reports based on your own assumptions will be rejected.
-
Functional Issues - 10 Points
-
User Interface Issues - 5 Points
-
Usability/UX Issue - 2 Point
Submitters that do not take 1st place will be paid $5 for each non-duplicate and verified issue up to a maximum prize of $100, limited to top 3 members. There will be no payment for 4th+ place.
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.
-
If Mobile and Tablet testing are available DON'T create the same issue on different platforms; instead, merge them into one; All the others will be marked as Duplicate.
-
If you see multiple broken links on the same page combine them into one ticket. Others will be marked as DUPLICATE.
-
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 screen shots 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.
-
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.
-
There will be no appeals phase. The decision of PM/Copilot for validity and severity of each filled issue will be final.
Final Deliverables
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:
-
topcoder handle (The one displayed in the top right corner near the Profile picture)
-
GitLab handle used to raise the issues.
- 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.