Redis Manager Bug Hunt

In this challenge, we need to hunt for bugs in our Redis Manager App. For folks who haven’t followed our challenges to build this tool, our client has asked for us to build a clone of Redis Commander and Medis, only in Angular6 (see 'Scope' section) so they can add some custom components as needed.

• Hunt and report bugs in the Redis Manager app

Final Submission Guidelines

About the Application

Redis it is an in-memory data store that is most commonly used to support web apps that need fast and frequent access to key-value pairs. This technique commonly known as data caching leverages Redis, however, to manage Redis users must become familiar with the Redis command line interface (CLI). Since the end users do not use Redis enough to become proficient with the CLI, we’ve been asked to make a management app for them.
 

Assets

Please clone the repo here. https://github.com/topcoderinc/TC-redis-manager

Technology Stack

Frontend

• Angular 7 (see scope)
• Angular Material https://material.angular.io/
• Material Icons https://material.io/tools/icons/?style=baseline

Backend

• ioredis https://github.com/luin/ioredis
• Hapi.js
• NodeJS

What to Test (Scope)

We have run several challenges to build this app. Please go through all the challenges specifications and test that all the features are included and work.
Major Requirement: We need Angular updated to Angular 7. Run "ng update" and validate the results. Ensure that all the features still work on Angular 7. You may log bugs for features that are broken or need refinement after the update. 

1. First Feature Race: https://www.topcoder.com/challenges/30069625/

• Note: the repo readme will probably be more useful than this challenge spec

2. Second Feature Race: https://www.topcoder.com/challenges/30070887
3. Third Feature Race: https://www.topcoder.com/challenges/30072451
4. Previous Bug Bash: https://www.topcoder.com/challenges/30071658/
5. The ability to change themes was added in a private task.

 

How to Create New Bug Report

Issue Reporting Guidelines

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

1. 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)
2. Current result(s) before the bug is fixed
3. Expected result(s), after the bug, is fixed

IMPORTANT NOTE:
Missing or Incorrect details to ANY of the above fields will mark the bug report as INCOMPLETE. 
For example, Incorrect Steps, 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 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 verified issues/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 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
• Content Bug:         1 Point

Submitters that do not take 1st, or 2nd place will be paid $5 for each non-duplicate and verified issue up to a maximum of the 2nd place prize.
 

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 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:
 

• Copies of all Test Execution Summaries which you participated in.
• topcoder handle (The one displayed in the top right corner near the Profile picture)
• GitHub handle used to raise the issues. (Login to GitHub and click on the Profile picture > Your Profile. Check the URL https://github.com/[Your Username])

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