Skip to content

General QA Notes

Jump to bottom
Erin Germ edited this page Nov 8, 2016 · 46 revisions

The following outlines testing for the Drive The Vote (DtV).

DtV Testing Party

Schedule a ride: https://dev.drive.vote/ride/berkeley-ca

Volunteer to Driver: https://dev.drive.vote/volunteer/berkeley-ca

Git Labels

There are two (2) labels for tracking QA testing:

  • QA required
  • This label informs the developers and QA engineers that test should be performed after an issue is resolved. The steps to verify an issue should be included in the Expected Results.
  • QA verified
  • Typically a bug that is already closed and fixes in place. This label is used once a issue is verified using the Expected Results.
  • QA blocked
  • When an issue is blocked by an existing open issue. The blocking issue should be noted in a blocked issue's comment.
  • QA investigate
  • This label is for open issues when an engineer is requiring additional information or further investigation

If an issue is closed with the "QA required" label but is still reproducible or does not meet all the expected results, the issue should be reopened and the label left at " QA required"; add a comment explaining what was tested and the current actual results. "QA blocked" is used in addition to "QA required" to track when a closed issue cannot be verified because another issue is open and impacting functionality.

The following query will show issues that are closed that need to be tested:

Issue/Bug Writing

Here is the template for reporting issues:

**Description**


**Version**
unknown
https://dev.drive.vote




**Steps**




**Actual Results**




**Expected Results**

It may be helpful to screen shot any issues that are seen.

#Scope of Sites

  • Drive to Vote (Development)
  • https://dev.drive.vote
  • This is the test site. All testing should be done on this site.
  • Drive to Vote (Production)
  • https://www.drive.vote
  • This is production site; no testing should be performed on this site that would impact user experience. Be careful and conservative when testing on the production site.
  • Drive to Vote - Information
  • https://info.drive.vote
  • This site contains information about dev.drive.vote. There should be no testing performed on this site.

Roles

Roles include:

  • Unauthenticated user - this is a casual browser that is no logged in
  • Driver - Authenticated user that is a driver
  • Dispatcher - Authenticated user that is coordinating a ride zone
  • Admin - Authenticated user that is managing ride zones
  • Super Admin - Authenticated user that is able to control various aspects of DtV and its data
  • Voter - Authenticated user that is looking for a free ride

Setting up multiple phone numbers for testing

Testing the app sometimes requires multiple working cell phone numbers in order to text back and forth. Here are some apps that can provide additional numbers:

  • TextNow - app for iPhone and Android
  • Google Numbers

If you are testing random creation of accounts and don't need to test the communication, you can use 555 exchange numbers (###-555-####) - e.g. 440-555-3958. Some 555 exchange numbers are valid.

Area code 555 is a real area code; do not use numbers like 555-###-#### because they are valid numbers and may send unwanted texts to people.

If you are experiencing issues and not receiving text messages, you may have been blacklisted. From your voter cell message "START" to the ride zone number.

It should also be noted that sending "cancel" will blacklist your number from our messaging service.

X-Code and Simulator

The following link may be beneficial: http://www.macinstruct.com/node/494

Depending on what version of X-Code you are using Simulator may have moved from [package contents] > Applications to [package contents] > Developer > Applications

  • Las Vegas, NV
  • 36.1699 / -115.1398 (36.1699° N, 115.1398° W)
  • Florida 5th cd
  • 28.5383 / -81.3792 ( 28.5383° N, 81.3792° W)
  • Berkeley, CA
  • 37.8716 / -122.2727 ( 37.8716° N, 122.2727° W)

When testing, driver should have a small spread on the map in order to see all the drivers. To achieve this we need to modify the latitude and longitude between 0.001-0.005 degrees.

If testing Berkeley, CA 37.8716 / -122.2727, the latitude/longitude that would get entered into custom location would be 37.8726 / -122.2747.

Geolocation

If having issue in iOS Safari:

  • General > Privacy > Location Services > Safari > set to While Using the App
  • General > Safari > Clear history and web site data

NOTE: test was only performed on Safari, not Chrome

NOTE: in live environments there may be issues with the app trying to use cellular data while the user is on a call.

Clone this wiki locally