Closed Bug 800017 Opened 12 years ago Closed 12 years ago

[B2G] B2g gaia test framework needs a 'kill all' method

Categories

(Remote Protocol :: Marionette, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: zcampbell, Assigned: jgriffin)

Details

Attachments

(1 file)

In some circumstances a test might start an app by clicking it's icon rather than using the 'launch' function in the GaiaApps class.

In that circumstance the test may not know the name of the app and as such a 'kill all' method would be useful.
This will be especially pertinent when running on a CI environment with real devices that are repeatedly used.

The phone will need to be restored to the same basic state.

A workaround would be 'stop b2g, start b2g' and return to that state.
Attachment #678575 - Flags: review?(jlal)
Attachment #678575 - Flags: review?(jlal) → review+
Needed to automating smoke tests.  Requesting blocking-basecamp to expedite landing in Gaia.
blocking-basecamp: --- → ?
https://github.com/mozilla-b2g/gaia/commit/614e237a7ba7687876a589ba44f241b4268a059f
Assignee: nobody → jgriffin
blocking-basecamp: ? → ---
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Zac, the structure of gaiatest in the gaia repo has changed a little; it now depends on both tests/python and tests/atoms.
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: