1816715 - UI tests aren't run anymore when a fenix change occurs

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Comment 1

[BMO Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1816715 - Do not optimize away UI tests task when a change happen… (#793)

Comment 2

[BMO Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1816715 - Do not optimize away UI tests task when a change happen… (backport #793) (#794)

Comment 3

[BMO Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1816715 - Do not optimize away UI tests task when a change happen… (backport #793) (#795)

Comment 4

[Donal Meehan [:dmeehan]]

:jlorenzo could you take a look at your fix in the release_v111 branch?
https://github.com/mozilla-mobile/firefox-android/pull/791 was backported to release_v111 branch after you backported Bug 1816715.
https://github.com/mozilla-mobile/firefox-android/pull/800 did not schedule the UI tests

Comment 5

[Johan Lorenzo [:jlorenzo]]

I see what happened. At the moment, any PR open by Mergify won't trigger UI tests. That's because Mergify is not considered a trusted user. I'll have a closer look at this.

That said, there's another thing that worries me: we should have built and unit-tested fenix in this PR too. This doesn't work as intended.

I'll file bugs for these 2 issues.

Comment 6

[Johan Lorenzo [:jlorenzo]]

PRs landed on all actives branches. UI tests are now run on PRs open by trusted contributors whenever a change requires UI tests.