Technician Scheduling Tool Bug Hunt

Project Overview

The client wants to develop an application that would help them with scheduling people (i.e. qualified technicians) and equipment, to specific job sites (i.e. locations) for a given duration of time. In other words, the client needs an application that would allow it to manage, schedule, and track resources (such as technicians and/or equipment), their engagement, qualification, and availability. They want to have this information at their fingertips though a well-designed application which the client prefers to be web-based.

The client has people and equipment that cover jobs all over the country. Since no location has sufficient resources to meet peak demands (and the ability to predict the peak demand is rather difficult,) the number of requests for services from customers will vary greatly during the year.  
When a location is in need of extra resources, the local (i.e. for that location) supervisor will usually need to acquire and schedule the needed resources from amongst multiple locations.  Sharing of these resources amongst locations is very common but quite challenging.

This application will provide the complete technician scheduling solution.

Contest Objective

The goal of this competition is to clearly identify the limitations of the provided assemblies and ensure the requirements as they were described have been met. You can find the documents describing the applications in contest forum.

Things to test in the current competetion are:

• All the issues implemented in http://www.topcoder.com/challenge-details/30034998/#.U3XhofmSzl8
• Every method and parameter works
• No unexpected errors occur
• Works in different browsers (all mainstream browsers should be tested)
• Our client raised some bugs in TopCoder TST Bugs.pptx, please read it first and don't report these bugs. 

Contest Guidelines

The guidelines for this contest are given below:

• As issues are identified they need to be logged in JIRA.
• 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.

Technologies

• HTML
• C#

Provided Resources

Documentation Provided

The following documentation will be available in the contest forum:

• ARS
• Source code

VM 

We have deployed both applications on our VM and you can access them from the following links:

• Address: topcoder.cloudapp.net:58895
• Username:  topcoder
• Password:  Topcoder2014
   
• Database name:  techtool
• Database Password: thisisNotapA#wo%216
   
• The user name for SQL server auth is "topcoder". The password is "thisisNotapA#wo%216".
• The app has implemented the authentication part. The authorization part is not implemented yet (It is not in scope).
  
  So you need to login first. Try http://topcoder.cloudapp.net/Login
  
  Planner role: planner/<ANY PASSWORD>
  Supervisor role: supervisor/<ANY PASSWORD>

Additional Resources

Some of the additional resources helpful for the project are

• Bug Hunt Competitions Issue Report Template.
• How to compete in Bug Hunt competitions.

Final Submission Guidelines

Bug Report Process

Bug Report Format

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

• Steps to reproduce, including any needed information
• Screen shots (if applicable)
• Expected results after the bug is fixed
• Current results, before the bug is fixed
• Browser version

You will log your tickets here: https://apps.topcoder.com/bugs/browse/TST and when creating a bug you MUST select TST 1st Release Bug Hunt JIRA component. Bugs will not be counted if a selection is not made.

Scoring

The Scoring guidelines followed for the contest are given below:

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.
• Put 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.
• Take a look at the bugs our client reported, please don't report duplicated bugs with our client.

Submission Deliverables

You need report your issues in JIRA. Please submit a text file contains the bugs you reported to OR.

Final Submission

• For each member, the final submission should be uploaded to the Online Review Tool.
• You must not include any identifying information, such as your handle, in your submission. Your submission should be anonymous and you will be scored down in screening for not complying.