The goal of the challenge is to bug hunt Myyna web application.

Project Overview

The Planetary Data System (PDS http://pds.nasa.gov/) is an archive of data from NASA’s planetary missions. The mission data (called products) can be raw images, time-series data  or text documents.

While this treasure trove of information is accessible to the public, utilization has been somewhat limited by barriers to entry such as required expertise on the domain, and familiarity with the data format.

The goal of this (PDS Storyboard) project is to develop a web application that will make the data easier to find and use by a wider range of people. PDS data is only as valuable as the ease of access and adoption – and NASA wants to make sure all this valuable mission data reaches a broader audience to further scientific discovery and research.

We are building a basic web application version. We are starting by reusing an open source web application called myyna. The point is to create a Pinterest-like social web application that address the need to make PDS data more accessible, and foster greater use of the available resources through collaboration and ease of distribution of data and research. By making PDS data easily accessible, and providing a Pinterest-like collaboration tool, the goal is to advance research and utilization of the data. This new web application will be called the “Planetary Data Storyboard” (Or PDS).

We are customizing Myyna web application to include the features we need to implement in the first version of this PDS Storyboard web application.

Challenge Task Overview

The goal of this challenge is to identify all issues in the pages and functionality of Myyna web application.

Testing

• The website to test is hosted here http://52.3.187.118:3000/

• You can also deploy the application if you have Mac OSX or Linux OS if you want to test your own setup version.

• You should test the website against following browsers :

  • Latest Chrome on Windows and Mac OSX

  • Latest FireFox on Windows and Mac OSX

  • Latest Safari on Windows and Mac OSX.

  • IE browsers 10, and 11.

• You need to register new accounts to use it for testing.

• You need to verify emails sent to users are rendered properly and the links are rendered correctly.

• Blocked and mixed content in https should be reported, i.e. all content should be loaded in https protocol when accessing website in https protocol.

GitLab Source Code

If you want to setup your own version the source code is placed it in gitlab

https://gitlab.com/nasa-pds-storyboard/storyboard-frontend

• You need to be logged in to view the repository.

• The app requires nodejs 0.8.28, and mongo 2.6

• Readme file contains all information you need to seup the app.

Pages in the web application

We have the following pages in this web application :

• Landing page (Non logged in)

• /pins

• /timeline

• /categories

• /boards

• /mostrepin

• /mostlike

• Pin details page

• Board details page

• Category details page

• Search page

• Profile page

• Search page

 

Functionality To Test

You will need to make thorough testing for the following functionality :

• Browsing all pages listed above without any console error.

• Register via email

• Register via facebook/twitter

• Login via email

• Login via facebook/twitter

  • The app should connect the account if an email already associated with an existing account.

• Forgot password

• Reset password

• Update user settings

• Create pin (desktop or web)

  • web also has different types (pdf, image, audio and video)

  • Note that there is a limit of 500kb for image/file size to be uploaded.

• Create category

  • Note that there is a limit of 500kb for image size to be uploaded.

• Create board

  • Note that there is a limit of 500kb for image size to be uploaded.

• Repin a pin.

• Like a pin.

• Comment on a pin.

• All links/buttons should be functional.

• Update pin details

• Update category details

• Update board details.

• User profile update details.

• Use settings update

• Following users/boards.

• Add/Remove users from board/category.

• In any listing pages (grid or list view), progressive loading should be functional, progressive means it loads new items when it reaches bottom of the page.

• In any listing pages (grid or list view) new resources should be added to top of the list in real time and highlighted.

  • If an item in the list was updated, the item will be reloaded to top of the list and highlighted in real time as well.

• In category/board/pin details page, real time update of the asset should be functional.

  • When user A is updating pin, and User b is viewing same pin, then User B will see the pin widget highlighted and updated in real time when user A makes any update to pin details.

• Searching pins/boards/categories/boards.

• Timeline - this is same as facebook feed, it show user all stories/activities done by other users

  • User will see stories from following resources :

    • From followings - user will see all activities done by the users he/she is following.

    • If user is category owner or admin

      • User can see any updates on the category, or associated boards, or associated pins.

    • If user is board owner or contributor

      • User can see any updates on the board, or associated pins.

    • If user follow a pin or created a pin

      • User can see the updates done on that pin.

  • Activity Feed

    • This feed appears in all pages except /timeline page, you can view it by clicking on electricity icon in header (when you are logged in)

    • It is same as /timeline except that it display activities related to the resource the user is viewing or it’s associated resources. i.e. if I am viewing board details page, I will see in activity feed all actions/activities done in the board or it’s associated pins.

  • List of stories we support in this version :

    • Create/update pin

    • Create/update board

    • Create/update category

    • Rename board

    • Renamed category

    • Moved pin

    • Moved board

    • Added/Removed user to/from board/category

    • Liked a pin

    • Commented on a pin

    • Repinned a pin

    • Follow user/board

    • User changed profile picture.

  • The /timeline and activity feed do an aggregation on stories, the aggregation aggregates actions done by a single user, grouped by resource and verb. Resource in this case is (user, board, category, pin), a verb here is (create, like, comment, update, renamed, moved, commented, followed, repin).

• Permissions and Roles - This table summarize the permission and roles each member in the web application :
    

Browsers in Scope

• Latest Chrome on Windows and Mac OSX

• Latest FireFox on Windows and Mac OSX

• Latest Safari on Windows and Mac OSX.

• IE browsers 10 and 11.

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.

• Members who submit duplicate reported bugs will lose 1 point/duplicate bug from their overall points.

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

• Issues will be classified via points system :

  • 4 points for functionality issue.

  • 2 points for UI and styling issue.

  • 2 points for Content issue (i.e. mixed content)

  • -1 point if you submit a duplicate issue

  • -1 point for irrelevant and out-of-scope issue.

• The member who get most points will win first place prize plus $2 per point, others will get $2 per point.

Important Notice

You must also be the first person to report the issue and submit it while submission phase is open.  JIRA will allow you to file issues before and after the submission phase, but these will NOT be counted.

 

Bug Report Format

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

• Proper title.

• Body of the JIRA should contain the following :

  • Protocol (https or http)

  • 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

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 and you will lose 1 point for each duplicate reported bug.

 

Ticket Logging

You will log your tickets here: https://apps.topcoder.com/bugs/browse/PDSEUREKA and when creating a bug you MUST select the "August Bugs" Bugs will not be counted if a selection is not made.

Scoring

 

The Scoring guidelines followed for the contest are given below:

• Issues will be classified via points system :

  • 4 points for functionality issue

  • 2 points for UI and styling issue.

  • 2 points for Content issue (i.e. mixed content)

  • -1 point if you submit a duplicate issue

  • -1 point for irrelevant and out-of-scope issue.

• For scoring, the submitter with the most accumulated points will win.

• All submitters will receive $2 per point for each point.

 

Important Notice

If two submitters submit the same bug report, the submitter who submitted the report first into JIRA 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.

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

 

Final Submission Guidelines

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.