Skip to content
This repository has been archived by the owner on Feb 21, 2023. It is now read-only.

Document testing best practices #70

Open
mcomella opened this issue Nov 1, 2018 · 1 comment
Open

Document testing best practices #70

mcomella opened this issue Nov 1, 2018 · 1 comment

Comments

@mcomella
Copy link
Contributor

mcomella commented Nov 1, 2018

  • Test naming conventions
  • UI vs integration vs unit: when to write which?
  • androidTest package hierarchy
  • robot pattern
@mcomella mcomella self-assigned this Jan 19, 2019
mcomella added a commit that referenced this issue Feb 5, 2019
The documentation now describes the basics of testing, of testing on
Android with the libraries we use, and some best practices. It can be
improved by explaining:
- how to override the application in each test type
- how we override the ServiceLocator (maybe in FFTV docs)
mcomella added a commit that referenced this issue Feb 5, 2019
The documentation now describes the basics of testing, of testing on
Android with the libraries we use, and some best practices. It can be
improved by explaining:
- how to override the application in each test type
- how we override the ServiceLocator (maybe in FFTV docs)
@mcomella
Copy link
Contributor Author

mcomella commented Feb 5, 2019

* Test naming conventions

* UI vs integration vs unit: when to write which?

* androidTest package hierarchy

* robot pattern

Landed all of these in https://github.com/mozilla-mobile/shared-docs/blob/master/android/testing.md

Still TODO:

  • How we override the application class in each case
  • How we do ServiceLocator injections
  • ...?

@mcomella mcomella removed their assignment Feb 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant