NASA Search Portal - Find and Log Defects

Welcome to the NASA Search Portal - Find and Log Defects contest. 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

NASA needs your help building an enterprise search portal. NASA & Topcoder have completed the design and frontend code for a search interface that is intuitive for beginner to advanced users which allows users to search against NASA intranet as well as public internet data sets.

 

As part of this project, we are integrating the search engine (Solr Cloud) which will serve as a backend to the Enterprise Search User Interface and seek to expand the capabilities of the existing application.

 

Contest Details

As part of this contest, we will provide you with a Nodejs based web application that needs to be tested in the following browsers:

1. IE11 (Windows)

2. Edge Latest (Windows)

3. Firefox ESR Latest (Windows)

4. Firefox Latest (Windows)

5. Google Chrome Latest (Windows)

6. Safari (Mac)

 

The Search Portal currently has the following features:

1. Simple string search.

2. Exclude certain words and result domains from the search

3. Filter the results to a specific domain (Internet, Public Info and NASA Intranet). If filtered to NASA Intranet, the results can further be filtered to a NASA Center and Agency.

4. Filter to a type of result - example - Images, Audio, Video. These are also restricted to the types shown in the Results. For example, if there is no Image in the results for a search query, the “Images” option will not show up as a filter here.

5. Filter the results to a specific date range - example - results from the past 24 hours, within a week.

6. Sorting the results based on the date.

7. Pagination to restrict the number of results returned.

8. A chart that shows the distribution of results across the three domains mentioned in point three above.

9. Allow the user to save the search criteria.

10. The first three results are from a Recommendation Engine - They will always have the title “No Title” and their description will always be “No Description”.

11. These results will only be shown for point 1 - simple string search. The moment any filter is applied, these results will disappear.

12. Multiple configurations. Check out the config folder for possible configurations that you can modify.

 

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 unique bug logged. The total amount paid will not exceed the second place prize money.

 

Points to Note

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

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

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

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

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

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

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

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

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