The goal of this challenge is to identify all issues in the UI, UX and functionality of Bank Ambassador ionic application in both Android and iOS platforms.

Project Overview

Our Client is building a mobile application that will allow employees--from the CEO to a high ranking individual contributor--to act as bank ambassadors when engaging with customers out in the community. The interactions range from official bank business (such as a charity event participant) to chance encounters (like crossing paths at a baseball game).

Challenge Requirements

You will have to build the ionic application and deploy it to your device, please refer to Gitlab Access and Setup below to get started.

Bug values

Bug Hunt Value is the value paid when an reviewer 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/bank-ambassador/mobile-app/issues

The issue you report should have the following :

1. Clear title for the issue

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:

• - P1 - Blocker - This bug prevents anyone from using the app in all target Devices. No work around exists.

• - P2 - Critical - This bug prevents some users from using the app on some of the devices. No work around exists.

• - P3 - Major - This bug prevents some users from using the app, but they can work around the issue.

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

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

Please note:

1. Assign the task to the admin/copilot.

2. Only test areas of the application listed in the "What to Test" section below.

3. We are mainly looking for issues related to Usability : UX/Flow, UI, and functionality that affect the app 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.

High Level User Stories

1. Ed is an executive who just met Carl,  a customer, at a baseball game. Ed only knows Carl’s first and last name and uses the app better understand Carl’s relationship with the bank.  In this instance, Ed would like to know total account value, if Carl uses online banking, and if Carl has any outstanding help desk tickets.

2. Ed gets introduced to a potential customer, Lisa, at a cocktails receptions. She explains that she has considered becoming a consumer of the bank for some time and that her co-worker, Bryan has been a costumer of the bank for over five years . Ed would like to check the status of Bryan and open a referral ticket related to Bryan’s introduction to Lisa. Ed only knows Bryan’s first name and the company that he works at.

3. On a phone call Ed’s assistant John tells him that he should double check the address of two customers who will be at an event he is attending later the same evening. To avoid typing, Ed uses the voice-to-text functionality to look up the two individuals based on their first and last name.

4. Ed handed out a few business cards at the customer appreciation lunch he was on yesterday. Two of the individuals texted him thanking him for a great lunch. Ed would now like to look them up based just the phone number so he can address the individuals by their correct first and last name when he replies to their message.

5. Ed is at an investment gathering in one of the suburbs in the city he works in. Janet, a potential consumer asks Ed if his bank is serving any of her neighbors since she is concerned that the closest branch might be a bit far away. To answer Janet’s question he wants to look up the approximate number of customer and businesses they serve in the community based on the city / zip code and distance from where they are located.

What to Test

Please test the following against real devices :

1. The Get Started slider and Skipping it.

2. Login

3. Search contacts by typing

4. Search contacts by speech to text

5. Filtering and sorting the contacts list

6. Reset search

7. Pull to refresh and Progressive loading the contacts list

8. Contact Profile

9. Contact Profile Bank accounts, Services, and Sales referral/opportunities including the filtering, sorting, pull to refresh and progressive loading in these screens.

10. Create service request

11. Create Referral

12. Recently Viewed and History

13. Logout

14. High Level User Stories

Supported OS and Devices

1. Android :

  1.1 OS : 5+

  1.2 Device: +4.7 inch

2. iOS :

  2.1 iPhone 5s+

  2.2 OS : 8.1+

Gitlab Access and Setup

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

Once added to the team, fork the repository and work off ‘develop’ branch  

• Mobile app : https://gitlab.com/bank-ambassador/mobile-app (use develop branch)

• Rest api : https://gitlab.com/bank-ambassador/rest-api  (use develop branch)

Follow README of both repositories to setup the application.

You can use the herokuapp instance to test the app, the mobile app in gitlab repo currently configured to hit http://bankambassador.herokuapp.com api instance

The API test data generator (if you set it up locally or used the heroku app) will generate 40 users, login id is : user1-user40.

 

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.