QA/Mobile/ReferenceBrowserTestPlan: Difference between revisions

QA/Mobile/ReferenceBrowserTestPlan (view source)

27 bytes removed , 31 January 2019

m

content tweak

Confirmed users

487

edits

@@ Line 146: / Line 146: @@
 = Dependencies/Risks =
-* Since the blocking status of trackers is not exposed via adb log or UI, its validation will rely on unit tests
+* Since blocking status of trackers is not exposed via ADB log or UI, validation will rely on unit tests
-* The performance of Reference Browser is not measured precisely, will rely on the tester feedback
+* Performance of Reference Browser is not measured precisely and will rely on the tester feedback
-* The tester pool for a preliminary first release will be extremely small
+* Tester pool for preliminary first release will be extremely small
-* The automation/manual test suites will be built incrementally as new features are added to Github, and the late features may not be exposed to validation as much as earlier ones
+* Automated / manual test suites will be built incrementally as new features are added to Github
-* The acceptance test after feature completion date will be performed with special emphasis on:
+* Late features may not be exposed to validation as much as earlier ones
-*# key features
+* Acceptance test (after feature completion date) will be performed with special emphasis on:
-*# most recently added features
+** key features
+** most recently added features
 = Signoff/Exit Criteria =
 * No critical or major UI bugs
 * No easily reproducible crashes