Apps/QA/Community Tasks

Overview

These are known tasks that we need help with on the Apps project with QA. To start on a task, find one that sounds interesting and contact the listed mentor for that task.

Mobile Website Compatibility Analysis

Mentors: Jason Smith and Aaron Train

Skills you will learn:

Under construction, stay tuned for more information.

Summary:

Under construction, stay tuned for more information.

Subjective App Analysis on Soup

Mentors: Jason Smith and Aaron Train

Skills you will learn:

• How to exploratory test a real Android application
• How to report issues to different stakeholders
  • Developers of the product
  • Developers of the app
• How to subjectively analyze an application using real customer data against set criteria
• How to log a bug

Summary:

1. Ask Jason Smith for an app to analyze
2. On an android device, download and install Soup
3. Use the instructions provided by Jason Smith to install the app
4. Exploratory test the app by launching an playing around with it in ways such as:
   1. Login into the app if it has account management
   2. Navigate around the app through clicking links and pressing the back button
   3. If the app has audio or video, play audio and video
   4. Navigate outside of the scope of the app by clicking a link that goes to a different origin (e.g. click a link on facebook.com that goes to google.com)
   5. If the app allows you to upload files, try uploading a file
   6. Any other ideas you have not listed here
5. Evaluate the app's quality experience using the template provided here
6. Log bugs here on issues discovered while using the app on Soup
7. Send the completed app analysis with the template to Jason Smith for review
8. For any revisions necessary, make the changes as needed
9. If the app analysis passes review, then you are finished

Soup Manual Testing

Mentor: Aaron Train

Skills you will learn:

• How to test a real application on Android
• How to a log a bug
• How to read an existing test cases document
• How to learn different functionality pieces on an Android app

Summary:

Run through the manual test cases for Soup listed here. These test cases span multiple sheets in this google document to cover testing soup installation, launching and running soup, installing apps, using the store, sync, purchasing apps, and other miscellaneous areas. After you run one or more test cases, send Aaron Train a message specifying what test case IDs you ran and the results of those test cases on the operating systems you ran the test cases on. Additionally, if an app was used during this case, specify what app was used. If you found any issues while testing, check to see if a bug was logged in the web apps bugzilla component. If there is no issue logged for an issue you found, log a bug here.

Develop New Soup Manual Test Cases

Mentor: Aaron Train

Skills you will learn:

• How to read an existing test cases document
• How to write a test case
• How to test an Android-based application
• How to capture missing test coverage in a system

Summary:

1. Read the existing Soup test cases here
2. Install the latest build of Soup here
3. Play around with the Soup application and note any functionality areas that are not covered by existing test cases
4. For the functionality areas not covered by test cases, construct test cases for them by providing the following:
   1. Summary: A short summary of what the test case is
   2. Steps to Perform: The steps to execute this test case
   3. Expected Results: The expected state of the system after running this test case
   4. Comments: Any additional information that needs to be specified
5. Send these test cases created to Aaron Train for review
6. If revisions are needed, make the revisions as needed and send it back for review
7. For test cases passing review, Aaron Train will add them to the existing Soup test cases

Verify Fixed Bugs

Mentors: Jason Smith and Aaron Train

Skills you will learn:

• How to reproduce problems on past builds
• How to read an existing bug
• How to test the fixed bug in a desktop and android environment
• How to report test results on a bug verification

Summary:

1. Use this bug query to find a bug to test
2. Read the bug to understand the steps to reproduce the conditions to test
3. Test the bug on an older build to verify you can see the bug (older builds are here)
4. Test the bug on the most recent build to verify that it is fixed
5. Send Jason Smith and Aaron Train a message containing the bug number and result