Challenge Overview

Project Overview

The Sales IM tool is an application that will create a web based instant messaging system.  The system will be used to install and run on a company's web site. The tool will allow potential clients of the company to ask questions and chat with the company.

The goal of this project is to build a responsive, HTML5-based Location Based Analytics application. This app will parse through data from several inputs (Wi-Fi, social media, mobile, etc.) and integrate it with transactional information to generate analytics on customer traffic and movement throughout a retail location. With this data the user can optimize customer interactions and operations, and can unlock the following:

  • Onsite Insights: A better understanding of customer profile and his/her behavior within a retail location
  • Dynamic Targeting: Market specific products based on the profile of the customer and his/her behavior patterns

Essentially, a user (store manager, marketing professional, etc.) will be able to use this app to monitor visitors/customers within a retail location. They can see where users are within that location as well as view their transaction data (what they are buying, how much, etc.). This in turn gives the user great insights into their customers and allows them to directly target specific customers or groups of customers with specific advertisements and promotions directly related and of interest to them. The Location Based Analytics app is the dashboard and tool to monitor that data and initiate those advertisements.

Contest Objective

The goal of this competition is to test the application UI. You should focus on testing the functions as well as usability. If there’s some intuitive usability issue you find, please do submit that (ie: “I tried to go back to the home screen but there was no way to do that from this screen”).

The basic guidelines for this contest are given below:

  • As issues are identified they need to be logged in GitLab.
  • Issues must include clear descriptions, test cases and steps to reproduce, and expected vs. actual results in order to be counted.
  • First competitor to find an issue gets credit, duplicates will not be counted.
  • Reviewers will accept, reject, or mark the issues as duplicate.
  • Please DO take a look at the reported bugs, duplicated bugs cost your work time and the reviewer's time.
  • Important Notice:  You must also be the first person to report the issue and submit it while submission phase is open.  Any bugs submitted outside of the submission duration will not be counted.
  • Please focus on functional testing. We do not want bug reports on typos, spelling errors, content spacing, and any other content-related trivial issues; all such issues will be rejected and will not count.
  • Please also submit standard usability issues (ie: usually apps allow you to interact a certain way, this one doesn’t)

What To Test

Please see the screenshots below, the areas in red rectangles need to properly tested.

Target Platforms

This application was designed to work on a tablet and have a touch-friendly user interface. Primary test devices are tablets, but browsers should be tested as well.

Desktop
Internet Explorer 10+, 
Current Versions of Firefox, Chrome, Safari

Tablets - Apple
OS: iOS 8+
Devices: iPad 2, iPad 3, iPad Air, iPad Mini
 
Android
OS: 5.0+ (Lollipop)
Devices: Samsung Galaxy Tab 4, Tab A

Technologies

  • Java
  • Spring
  • HTML
  • HP Vertica
  • HTML5
  • Angular.js


Final Submission Guidelines

Bug Report Process

Bug Report Format

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

  1. If Testing on a Device, Device Specs:
    1. Device Type and Version (ie: iPad 3)
    2. OS Version (ie:iOS 8.4)
    3. If you are in an Emulator or a Physical Device
  2. If Testing on a Browser:
    1. OS Version (ie: Windows 10)
    2. Browser Version (ie: Chrome Version 47.0.2526.73 (64-bit))
  3. Bug Details
    1. Steps to reproduce, including any needed information
    2. Screen shots (if applicable) or Screencast if the bug requires multiple steps to reproduce. In short, the best way to show the bug!
    3. Expected results after the bug is fixed
    4. Current results, before the bug is fixed

 Important Notice:

  • If you do not properly document your bug reports, they will likely be rejected due to lack of information or documentation. Also, make sure your bug reports are reasonably general.
  • If you submit the same bug that is seen in multiple screens, for instance, you will likely only get credit for the original bug report. The others will all be closed as duplicates.

How to Log Tickets

Scoring

Scoring will be based on the number of bugs, weighted by severity.  Be sure to correctly attach a severity label to your bug.  The co-pilot has the right to change a severity at their discretion.

Scoring is inverse to severity: P1 = 5points, P2 = 4points, P3 = 3points, P4 = 2 points, P5 = 1point

The member with the highest score will win 1st place.  The member who gets the 2nd most points will win $100.

For submitters who submit but don't take first, if they submit bugs that aren't covered in the by either prize mentioned above, they will receive $5 for other accepted bugs up to a $200 grand total.  All bugs outside of the first and second place awards are subject to the co-pilot’s discretion.

If two submitters submit the same bug report, the submitter who submitted the report first into GitLab will get credit for the bug. The second submitter will not.

Tips

Some of the tips helpful for the contest are:

  • 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 members 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 creation of any necessary data.

Submission Deliverables

For each ticket you fix, upload text file with link to gitlab merge request to Online Review, we will need this to pay you.

Final Submission

  • For each member, the final submission should be uploaded via the challenge detail page on topcoder.com.

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30050161