The goal of the challenge is to bug hunt Managed Risk web app.

Project Background/Description

The client for this project has an existing risk navigation solution that provides companies in the industrial commodities sector with a structured approach for addressing two fundamental issues associated with hedge programs and their interdependence: understanding the risk to financial goals that volatile commodities cause and adopting a lucid hedge structure to protect the goals. The solution also incorporates regulatory and compliance requirements, as well as the complexities and nuances of financial reporting for the energy industry.  

A core component of the delivery of its service offering is a web-based risk management system which provides our practitioners and clients with access to a hosted deal capture, valuation, risk quantification, and risk reporting solution.  This existing web application primarily leverages static dashboards and customized, but pre-defined reports.  These elements produce a robust data set on a daily basis from valuations to probabilistic distributions of costs, earnings, gross margins, to position and fixed prices across the portfolio and book structure and different time horizons.  However, users currently don’t have access to this full set of data - if it’s not contained in a specific report, then customized development is needed to create the report or graph.

Through challenges, we have created a user controlled reporting module where the client can provide access to the underlying data and users can create their own reports, charts, and graphs to meet their reporting needs.  User’s can create simple graphs and reports based on the data that gets generated daily.

Challenge Task Overview

In this bug hunt you will focus on the UI and functionality issues that affect rendering pages properly for the users.

How/What to Test

- Post in the forums to get access to Amazon EC2 Windows VM with the application setup on it with client test data, you will use it to do the testing. You don’t need to deploy the app unless you want to dig deep into the code to provide exact code causing the bug.

- We have four main pages :

• - Generate/Edit Report page

• - Dashboard page

• - Reports Listing page

• - Report Details page

- You will test all navigation/flow and functionality exposed in these four pages. We want you to stress test and try to break the UI. Meaning you need to try every single option or button or UI element on these pages.

- Please test the representative business cases below as well.

• - One thing to note: Because of the style of the site and the dropdown widget used, they scroll.  If you open a dropdown and don’t see an option in that list, please scroll within that dropdown to see more options.

Business Cases to Test

Business cases are step-by-step generation of reports.  We have provided 3 as a sample since output analysis requires a fair amount of business knowledge.  Follow the cases below, but please be sure to identify which business case bugs are related to.

Business Case 1 - Native Position and Hedge Position

1. Name the Report - <yourhandle>TestReport1

2. Data Source - TradeData

3. Select All Fields

   1. Sum on Quantity

4. No calculated fields

5. No filters

6. Under Graph Options

   1. Graph Type - Bar Chart

   2. Data

      1. x-axis = Trade Type

      2. y-axis = Quantity

   3. Colors

      1. select colors you’d like

   4. Notations

      1. Name the graph, X, and Y

7. Result is showing below: two quantity bars for the two types of trade types.

Business Case 2 - Market price v. fixed price

1. Name the Report - <yourhandle>TestReport1

2. Select data source – TradeData

3. Selected data fields = TradeID, Price (avg), PriceIndexName, Quantity, Contract Month

4. Do not select a Calculated field

5. Add the following filter:

   1. TradeData.ContractMonth>’6/1/2015 12:00:00 AM’

6. Graph Type: Line

7. Data

   1. X-Axis: Contract Month

   2. Y Axis: Price

Business Case 3 - Mark-to-market of transactions by counterparty

1. Name the Report - <yourhandle>TestReport1

2. Select data source – TradeData & Prices

3. Select data fields = Quantity (SUM), Trade type, DeliveryDate,

4. Did not add a Calculated field

5. Do not add a Filter field

Bug values

Bug Hunt Value is the value paid when an admin confirms a bug you found to be that level.  

Rules to Find Bugs

We need you to hunt for the issues and report these issues to GitLab https://gitlab.com/aers-managed-risk/backend/issues (see below to get access).

The issue you report should have the following :

1. Clear title for the issue - If you are testing a Business Case above, please identify which business case it relates to.

2. Provide a detailed description with screenshots with steps to produce as the issue description.

3. If you have technical explanation, then you can provide more details with links to the code in the gitlab repo that is causing the problem.

4. Assign it a priority level you think fits:

1. P1 - Blocker - This bug prevents anyone from using the app in any browser. No work around exists.

2. P2 - Critical - This bug prevents some users from using the app on some browsers. No work around exists.

3. P3 - Major - This bug prevents some users from using the app, but they can work around the issue (ie: use a nav to get back in generate report flow, submit the form with the enter key when the submit button is off screen, etc)

4. P4 - Minor - This is an annoyance, but won’t prevent the target market from using the app

5. P5 - Enhancement - Something noticed by testers that should be fixed, but isn’t considered a bug.

Please note:

1. Assigning the task to the admin/copilot.

2. Only test areas of the application listed in the "How to Test" section above.

3. We are mainly looking for issues related to Usability : UX/Flow, UI, and functionality that affect the website usability. Spelling mistakes and minor styling issues should be out of the scope.

4. We will not pay for duplicate bugs.  We will accept the first submitted bug, based on time in GitLab.  Please do not submit slight differences to try and get accepted. This will get you banned.

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

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

7. We plan to run another business focused bug hunt in the future (i.e. more business test cases).  If you have detailed subject matter expertise (financial commodities and/or reporting), we will accept business focused bugs outside of the 3 test cases provided.

Browsers In Scope

• - IE 11 (this is the main client browser)

• - Latest Chrome, Safari and FireFox.

Gitlab Access and Setup

• - You can get access to the Gitlab repo group in this tool https://tc-ragnar.herokuapp.com/ragnar/groups/564783092789620e00fa75d1/290828  .  If you are having trouble with the auto registration tool, please ask in the forums.

• - Once added to the team, start log issues here https://gitlab.com/aers-managed-risk/backend/issues 

• - The source code of the app exists here https://gitlab.com/aers-managed-risk/backend/tree/develop if you want to deploy locally or your own version follow Docs/Deployment Guide - Report Generation Improvement Code Challenge.doc to deploy and configure the application.

Final Submission Guidelines

Final Submission Deliverables

You need report your issues in Gitlab. Please submit a text file contains your gitlab handle to Online Review, this is needed so we can process payment if you win.