Lightspeed Permission / Tagging / Collaboration Bug Hunt

Project Overview

LightSpeed is an Excel based VBA application and in this project we are converting this application to a web based app to make it much easier to use. The web app will be an HTML5 app with offline capabilities.

Contest Objective

The goal of this competition is to test some specific features of the app and see if there are bugs in these areas.

Things to test in the current competetion are:

• The collaboration requirements described in this challenge: http://www.topcoder.com/challenge-details/30052617/?type=develop&noncache=true
• Data Download - When I am new user, I should only have access to download those projects for which I am listed as a key member, regardless of my division or theatre.  For example, I am not listed on any project as a key member, so when I log in, I should be able to create a profile, but will not have the capability download any data, until I am granted divisional or theatre level access.  There appears to be a way to request that, but I have never been able to navigate to that screen.  Once I am granted theatre or divisional access, only then do I see the old matrix that allows me to select key members for data download, or specific division or theatres (Keep in mind, if I was only granted access to one division, I should only be able to select that division. )  If I AM listed as a key member on projects I automatically get all the projects I am listed as a key member, regardless of the geographical location of the project.  I can then be given additional access to projects through either the collaboration feature or divisional/theatres access, but I should always start with the base of the projects I am listed as a key member to start.
• Add a new button named "Tag" beside "Update All" and "Edits Summary". Users can select multiple projects using the rightmost checkbox column (whether filtered or not filtered), and hit Tag button to see the popup where they enter a tag for all checked projects. This means we'll need to remove the keyboard related controls from the popup to edit project name:
  • The new Tag button needs to work for all views
  • The user needs to be able to specify visibility of the tag, it can be private, visible to division or visible to theater. This is also inherited with collaboration
  • Tags get saved on left drawer, organized by theater and division then alphabetical
  • User can add / remove projects from a tag by clicking on the link from tags (left drawer), then it loads up as filter with all rows that apply as checked in the right most checkbox column. User can uncheck a row and when user navigates away it asks if he wants to save
  • Users can also delete a tag from left drawer. We need to add a "x" icon similar to the one we use to remove a keyword in our current "Edit Field" popup. Pressing x means tag is removed from left drawer, removed from projects and removed from database (pick list). But we need to ask the user to confirm this is the expected behavior and if they click yes we do it.
  • Not every user will have the ability to edit the CPM name, but even read only users will have the need to assign tags
• We need to have the ability to delete saved filters, add the "x" icon to both the left drawer and the load filters screen.

General Notes

• Please focus on functionality testing, we don't need reports of really trivial issues like typos, spelling errors, etc...
• No unexpected errors occur
• Test both online and offline mode
• Works in different browsers (see below for a list)

Browser Requirements

The given application must be tested in IE 10+, latest version of Firefox / Chrome / Safari (Mac Only).

Users

Please log in with your own handle as a normal user (you must enter all files to login). To change permissions login as "admin". But please only use "admin" to test admin only features.

Contest Guidelines

The 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.
• The copilot / reviewer will make the decision whether a bug is valid or not

Technologies

• Java
• Angular.js
• HTML5
• Postgres
• Javascript

Provided Resources

Documentation Provided

The following documentation will be available in the contest forum:

• Requirements
• Source code

Contest Prize Eligibility