Housekeeping: QA & Development Terminology & Standards

Notes:

• QA will use this sheet to describe observations.
• Development takes the lead on renaming terminology to ensure it's accurate.
• The goal is to create a "shared language" while diagnosing/describing requirements.

Standards:

• After a codepush is deployed, QA must K/R the app to ensure the codepush will work as expected
• After a staging build is released on Testflight, QA must perform a clean install
• QA will not name username, bots, or any feature that allows free text entry with the name of a app function such as push, push notification, bot, presence. For example, QA should not create a user called user or presence. Or QA should not create a bot named bot or presence bot. For features that are thoroughly tested, QA will not name these items gibberish.
• For bot testing purposes, QA will always enable a unique image to ensure proper testing and reduce confusion.

Feature Related Adjustments:

• Geofence does not have debouncing logic on Staging

Terminology

-	-
Foreground app refresh	Data updates while the app is in the foreground (without having to tap onto another screen and returning to the original screen)
Geofence Widget	The geofence header that appears on the HS
Location upload	When the client uploads a location data point to the server
Subscribing	Loosely interchanged between hearting a bot and enabling footprint for a bot
K/R	Kill and reload, "quit" the app and then launch it
Clean install	App is deleted and then reinstalled
Dynamic Updates	(May not be the best word but per QA discussion this is how it's used) Data is updated as it happens "live"
Bugsnag	Issues found on the bugsnag platform
Loading states	UI that is intentionally shown to the user as they wait for information
Avatars	User Profile Images
hitSlop	The tappable area a user must tap in order to trigger a CTA
Static/Persistent/Fixed	(this one needs work) The UI sticks to a certain area
Live Updates	?
Geofence Timeouts	? (how to best define this?)
"....of doom"	Jargon to communicate "constantly there", for example "offline of doom" means it's consistently there or "spinner of doom"
Debouncing	? (how to best define this?)
App crash	Occurs when the app automatically quits. (A related bugsnag should have been automatically created as well as a github ticket)
Repro	Reproduction steps needed so that the dev can diagnose the issue
App Icon Badge Counter	The badge counter that exist on the App Icon (the red circle with a number) on a user's app icon screen (could be better explained)
bugreport	A channel on slack that lists all the bugs that occur in a build
[geofence] debugger	A debugging tool, called Location Debug that sits in the navigation menu of the staging app.
Presence Online Indicator	(perhaps the term can be renamed to online/offline indicator) The blue icon that sits on the user avatar that indicates if a user is on or off the app