Vitruvius Web Portal - Identify and Log Cross Browser Platform Issues Challenge

Welcome to the Vitruvius Web Portal - Identify and Log Cross Browser Platform Issues Challenge. This is a Bug Hunt Challenge where we would like you to work with a web based application and report any bugs with it.

 

Project Overview

Our client helps individuals, teams and organizations to accelerate innovation. They have a web application that serves as a platform for individuals to grow in their personal development, for teams to build their collective capabilities and for organizations to drive large scale cultural change.

This project centers around the client’s web based application where we intend to enhance its design and architecture.

 

Challenge Overview

As part of this challenge, we will provide you with up with a web based application that needs to be used in the following browsers:

 

1. ���Chrome 46

2. Chrome 45

3. Edge 13

4. Edge 12

5. Firefox 42

6. Firefox 41

7. IE 11

8. Safari 9

9. Safari 8

 

No mobile based browsers need to be tested. Only Desktop browsers are required. You need to log the issues is the Github Issue Tracker directly. We will share the issue tracker link with you in the challenge forums.

 

We will provide you with a template of how to report any issue in the challenge forum itself. Kindly check out the challenge forums for more details.

 

Payment Structure and Scoring

1. The participant with the highest number of valid bugs logged will be declared the winner and will earn the first place payment

2. Participant with the second highest number of valid bugs logged in will earn the second place payment

3. For other participants, we will pay up to $5 for each bug logged. The total amount paid will not exceed the second place prize money.

 

Points to Note

• Before you log your issue, ensure that there is no similar issue already logged in. You can do a quick keyword search and only when you are sure that there is no other ticket logged for the same issue, create one.

• Simple issues related to spelling and grammar may not count.

• Issues must be clearly described. Provide a test case (perhaps an unlisted video reproducing the issue or a document with steps on how to reproduce the issue) along with the expected vs actual results in order for your issue to be counted.

• Video / screenshots in your issue description will help tremendously.

• If an issue is not properly documented, we may reject it and it will not count.

• If you submit an issue that is seen in multiple screens as multiple issues, they will only count as one. Others will be marked as duplicate.

• The first participant to find an issue gets the credit - duplicate issues will not be counted.

• Only create issues until the submission phase. After that, any issue logged will not count.

• We will mark the issue as accepted, rejected or duplicate.

 

Read more about the Bug Hunt challenge and the Issue Report template here:

Bug Hunt - How to: http://apps.topcoder.com/wiki/pages/viewpage.action?pageId=35691122

Issue Report Template: http://apps.topcoder.com/wiki/display/tc/Bug+Hunt+Competitions+-+Issue+Report+Template

In your template kindly make sure that you specify the browser in which the issue was observed. You need to check in all the above mentioned browsers.

 

Final Submission Guidelines

If you have submitted an issue through the provided issue tracker, kindly submit a simple README file containing your github handle in it. Your submissions will be evaluated through the Issue tracker.