Register
Submit a solution
The challenge is finished.

Challenge Overview

Project Overview

The client for this project is looking to expand its automotive brand. Their current automotive digital strategy lacks an industry-specific marketing brand/platform, resulting in low viewership of digital content and low quality/quantity of contacts in the database.

The goal of the DRIVEN project is to introduce a sustainable automotive-specific application that aggregates content across the firm, digitally delivers that content to stakeholders worldwide, and can evolve with advancements in mobile technology and digital communications.

 

Contest Objective

The goal of this competition is to test both the backend application, built on Magnolia CMS, as well as testing the mobile app on target devices.

You should focus on testing the functions as well as usability. If there’s some intuitive usability issue you find, please do submit that (ie: “I tried to go back to the home screen but there was no way to do that from this screen”)

Common Testing Guidelines

The basic guidelines for this contest are given below:

  • As issues are identified they need to be logged in GitLab.

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

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

  • Important Notice:  You must also be the first person to report the issue and submit it while submission phase is open.  Any bugs submitted outside of the submission duration will not be counted.

 

Mobile Testing Guidelines

  • Issues for the mobile app should be logged here: https://gitlab.com/dinnaco-driven/mobile-app/issues
    Instructions on getting added to the GitLab group are below.

  • Add either label:

    • BUG HUNT - iOS

    • BUG HUNT - Android

  • ���Add a Severity Level:

  • Please focus on functional testing. We do not want bug reports on typos, spelling errors, content spacing, and any other content-related trivial issues; all such issues will be rejected and will not count.

  • Please also submit standard usability issues (ie: usually ipad apps allow you to interact a certain way, this one doesn’t)

  • The iOS and android beta app for testing are  distributed via Hockey app. The app distribution links via hockeyapp are provided in the challenge forum - documentation section.

Backend / Magnolia Testing Guidelines

  • Link and Login will be provided in the challenge forum - documentation section.

  • Issues for the mobile app should be logged here: https://gitlab.com/dinnaco-driven/backend-api/issues
    Instructions on getting added to the GitLab group are below.

  • Only test the Contents App, and Categories in Magnolia.  Test uploading all article types, categorizing them, and publishing them.

  • When testing Magnolia Content, please only add and remove your own test category / content.  Please DO NOT remove category / content that you did not add.  Other members may be testing content they upload to Magnolia on the device. To ensure that, please create a folder with your handle and put the content you create in your own folder.

 

Mobile Device Target Platforms

Apple

OS: iOS 8+

Primary Devices: iPad 2, iPad 3, iPad Air, iPad Mini

Allowed Devices: iPhone 5, 5s, 6, 6+, 6s, 6s+

 

Android

OS: 5.0+ (Lollipop)

Primary Devices: Samsung Galaxy Tab 4, Tab A, Kindle Fire

Allowed Devices: Samsung S5, S6


Please focus on the primary devices (tablet devices) first, then allowed devices.



Final Submission Guidelines

Submission Guidelines

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

  1. Device Specs:

    1. Device Type and Version (ie: iPad 3)

    2. OS Version (ie:iOS 8.4)

    3. If you are in an Emulator or a Physical Device

    4. If you installed the provided app, or checked out the source and built it yourself.

  2. Bug Details

    1. Steps to reproduce, including any needed information

    2. Screen shots (if applicable) or Screencast if the bug requires multiple steps to reproduce. In short, the best way to show the bug !

    3. Expected results after the bug is fixed

    4. Current results, before the bug is fixed

 

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

  1. Browser Specs:

    1. OS Version (Windows 10, etc)

    2. Browser Version (Chrome Version 46.0.2490.80 (64-bit))

  2. Bug Details

    1. Steps to reproduce, including any needed information

    2. Screen shots (if applicable) or Screencast if the bug requires multiple steps to reproduce. In short, the best way to show the bug !

    3. Expected results after the bug is fixed

    4. Current results, before the bug is fixed

 

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.

How to Log Tickets

  1. Create an account on GitLab: http://www.gitlab.com

  2. Go to this URL to join the project group: https://tc-ragnar.herokuapp.com/ragnar/groups/5613f730d601610e000f21bd/284538

  3. Search for and register your GitLab handle to join the project

  4. Install the provided compiled app on your device (Links in the forum)

  5. Log issues in the correct place

    1. Log mobile app issues here: https://gitlab.com/dinnaco-driven/mobile-app/issues

    2. Log backend / magnolia issues here: https://gitlab.com/dinnaco-driven/backend-api/issues

    3. If you’re not sure if the bug is frontend or backend, log them under backend

  6. View and Submit Issues

 

Scoring

Scoring will be based on the number of bugs, weighted by severity.  Be sure to correctly attach a severity label to your bug.  The co-pilot has the right to change a severity at their discretion.

Scoring is inverse to severity: P1 = 5points, P2 = 4points, P3 = 3points, P4 = 2 points, P1 = 1point

The member with the highest score will win 1st place.  The member who gets the 2nd most points will win $100.

For submitters who submit but don't take first, if they submit bugs that aren't covered in the by either prize mentioned above, they will receive $5 for other accepted bugs up to a $200 grand total.  All bugs outside of the first and second place awards are subject to the co-pilot’s discretion.

Important Notice:

If two submitters submit the same bug report, the submitter who submitted the report first into GitLab will get credit for the bug. The second submitter will not.

Tips

Some of the tips helpful for the contest:

  • For the mobile app issues, set up a Device Specs “boilerplate” for yourself with the required information about the device you’re testing on so you don’t have to type it in every time.

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

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

Review style

Final Review

Community Review Board

Approval

User Sign-Off

ID: 30051087