IHT - Interaction History Tracker - Bug Hunt

Challenge OBJECTIVES

Welcome to the "IHT - Interaction History Tracker - Bug Hunt". This is an application with both backend and frontend. In this challenge, we are going to identify and log defects on this application.

Note: this challenge will have 24h for registration (during this phase no one will see details) and then 48h for bug hunting.

What to Test (Scope)

Tech stack: Typescript, Nodejs 12, NestJs, Angular

Application type: API and Angular

Repo:

• https://github.com/tc-wellmark/cim-iht-presentation-api (master)
• https://github.com/tc-wellmark/cim-iht-ui (master)

Accepted types of bugs:

• Bugs in frontend
• Bugs in integration
• Bugs in backend

Frontend issues should be reported in cim-iht-ui
Backend issues should be reported in cim-iht-presentation-api

Browser Requirements

• Desktop: Microsoft Edge and Chrome Browsers (Mac & Windows).

The backend codebase comes from client's starter code, so there are many files not really used in backend api. Those files are out of scope.

The application has been deployed in heroku. The link will be shared in the forum after 24h along with the access link to github repo.

Provided Resources

The following documentation will be available in the contest forum:

1. Access url to both fronend and backend

2. Requirement documents

3. Heroku link

Issue Reporting Guidelines

For each report of a 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 bug without test data)
• Current results before the bug is fixed
• Expected results, after the bug, is fixed
• Attach screenshots, videos directly in Github & Crash - Console/Crash Logs and sample payloads (request body / query) that will be helpful to understand the bug.

IMPORTANT NOTE:

• Please DO take a look at the reported bugs, duplicated bugs cost your work time and the reviewer's time.
• Missing or Incorrect details to ANY of the above fields will mark the bug report as INCOMPLETE. For example, Incorrect Steps, Missing Screenshot/Screencast, Incorrect Actual and Expected results etc.

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 copilot has the right to change a severity at his 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 from verified issues 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 testing based on the requirements, all bug reports based on your own assumptions will be rejected.

In addition to the first and second place prize, we will be awarding the following prize money to all competitors.

• Blocker/ Critical: $10 [10 Points]
• Major: $8 [8 Points]
• Minor: $5 [5 Points]
• Enhancement: $2 [2 Points]

P1 - Blocker: This bug causes the app to fail. No workaround exists. E.g. app crashes, app freezes.

P2 - Critical: This bug causes the app to fail for some specific cases. No workaround exists.

P3 - Major: This bug causes the app to fail, but there’s a workaround to prevent that issue.

P4 - Minor: This is an annoyance, but won’t prevent the app from running normally.

P5 - Enhancement: Something noticed by testers that should be fixed, but isn’t considered a bug.

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.
• DON'T RE-OPEN the issues in the review phase and anyone who RE-OPENS a ticket 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.
• 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 Copilot for validity and severity of each filled issue will be final.

Final Submission Guidelines

Submit all your bugs directly to GitHub. 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 (The one displayed in the top right corner near the Profile picture)

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

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