[B2G] SMS notification not clearing when Marionette is running tests

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
6 years ago
4 years ago

People

(Reporter: zcampbell, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

6 years ago
Created attachment 713346 [details]
Test case for replicating toaster getting stuck

The SMS notification that appears in the System toaster is not clearing properly if Marionette stops and starts a test before the 5 second timeout of the toaster notification.

I've attached a test case and logcat. It is useful to observe the device while this test is running.

The test case will Fail which is expected, but there is an option to make it pass by un-commenting line #73. (again, observe the correct behaviour in the passing case).

This doesn't appear to affect any tests just yet but it is concerning that Marionette can interrupt a System app process.

The presence of the toaster element could also interfere with future tests, it obscuring the page.
(Reporter)

Comment 1

6 years ago
Created attachment 713347 [details]
Logcat for failing test case
I can also reproduce this locally... 
======================================================================
FAIL: test_b_check_sms_notify_still_pres (test_ok.TestSms)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/bebe/gaia/gaia-ui-tests/gaiatest/tests/test_ok.py", line 92, in test_b_check_sms_notify_still_pres
    self.assertFalse(self.marionette.find_element('id','notification-toaster').is_displayed())
TEST-UNEXPECTED-FAIL | test_ok.py TestSms.test_b_check_sms_notify_still_pres | AssertionError: True is not false
----------------------------------------------------------------------
Ran 2 tests in 39.730s
(Reporter)

Comment 3

4 years ago
Haven't seen this since.. well 18 months.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.