Hylo Redesign Testing Instructions (Mobile)

Instructions and important links for testing Hylo's redesign on the mobile platform

Getting Started with Testing

iOS Testing Setup (TestFlight)

1. Provide your email address to the testing Hylo team ([e-mail])

2. Watch for an email invitation to join the Hylo test group

3. Follow the email instructions to download TestFlight

4. Accept the invitation within TestFlight

5. Install the Hylo test build / latest app release

Android Testing Setup (APKflight - TestFlight for Google)

1. Provide a Gmail account or Google-backed email address [you can create a new Google account specifically for testing]

2. You will receive emails when new releases are available for download

3. Follow the provided instructions to install the test build

Important Notes

• Installing the test version will override any existing Hylo app on your device

• The test build connects to our staging environment, not production

• You will receive notifications when new test builds are available

Accessing Test Plan

• Accessing Hylo’s Test Plan - link here

  • Note: the feature sets are divided into various sections

  • The second tab indicates pages that still have the old styling (see Important Notes below)

• Under "Welcome" you will see a link to this Testing Plan and Canny, as well as a list of testers.

• Review the testing guidelines at the top of your section(s)

• Note: Each test will include instructions on how to test each feature and an expected result.

Important Notes for Testers

Visual Appearance

• The mobile UI currently uses a hybrid of old and new styling

• You may notice inconsistent visual styling across different screens

• These cosmetic inconsistencies are expected and should not be reported as bugs

• Reference the Mobile Test Plan's "Styling Screens/Pages" section to identify which pages are pending new brand colors

Step 3: Conduct tests

• For the sections you test, enter your name adjacent to each test, the date you tested the feature, and the result.

• Mark each test as Pass/Fail/"?" in the provided spreadsheet

  • If it is a Fail, you will submit a bug in Canny if there is any deviation from expected behavior, visual inconsistencies, performance issues, or functionality failures [see instructions on submitting bugs below]

  • If you have questions, please enter a "?", create a comment and tag Krisha Subramanian and Tibet Spraguewith your question
• Include whether you are using iOS or Android

• Link the canny issue in the spreadsheet [see instructions BELOW]

Step 4: Submit any bugs you find

• We use Canny to submit bugs

• To submit a bug, navigate to Canny.

• Search for existing bugs for your issue in Canny using the search bar. If your issue hasn't already been reported, you will see an area at the top of the page to submit your bug report.
• In the Title of your canny report, include MOBILE

• In the Description, you will include:

  • Bug Description:

    • Clear summary of the issue

    • Steps to reproduce

    • Expected vs. actual behavior

    • Supporting Materials including screenshots/screen recordings

  • Device Details:

    • iOS or Android

  • Please see the Example Bug Report Below

    • Title: Post content becomes invisible ("whited out") when clicked in Stream view in Mobile

    • Summary of the issue: When viewing posts in the Stream of the Hylo Product Testers group, clicking on any post causes its content to become invisible, appearing as a blank white space.

    • Steps to Reproduce:

      • Navigate to Building Hylo group Stream

      • Locate any post (confirmed with both an event post and a proposal post)

      • Click on the post to view details

      • Observe that the post content becomes invisible

    • Expected Behavior Post content should remain visible and readable when clicked, maintaining the same appearance as in the Stream view. the post to appear the same after clicking on it. Actual Behavior: Post content disappears, showing only a white space where text should be displayed.

    • Supporting Materials: (please see screenshot)
    • Device Details: iOS

Step 5: Bug Report Follow-up

• Monitor your reported bugs for questions

• Respond to requests for additional information

• Update bug status if you discover new information

• Once a bug you created has been closed, you will receive a notification email from Canny, after which you can retest the feature

• Once a week do a full run through of all your assigned tests, in case something broke when fixing other bugs