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

Disable Push support when Fennec is migrating #7645

Closed
jonalmeida opened this issue Jan 13, 2020 · 9 comments
Closed

Disable Push support when Fennec is migrating #7645

jonalmeida opened this issue Jan 13, 2020 · 9 comments

Comments

@jonalmeida
Copy link
Contributor

jonalmeida commented Jan 13, 2020

Stop push when migrating.

QA testing STR:

  1. Ensure Send Tab is working on Fennec.
  2. Migrate to Fenix.
  3. Send another tab.

Expected:

At 3, the tab should be delivered.

┆Issue is synchronized with this Jira Task

@st3fan
Copy link
Contributor

st3fan commented Jan 15, 2020

@jonalmeida can we close this or move it to QA? (Is it verifiable by QA?)

@jonalmeida
Copy link
Contributor Author

Add the label as soon as the patch lands. 👌

jonalmeida added a commit to jonalmeida/fenix that referenced this issue Jan 15, 2020
jonalmeida added a commit to jonalmeida/fenix that referenced this issue Jan 15, 2020
A-C: Android Components Sprint Planning automation moved this from ⏳ Sprint Backlog to 🏁 Done Jan 15, 2020
Fennec migration automation moved this from Nightly to Ready for QA Jan 15, 2020
@jonalmeida jonalmeida reopened this Jan 15, 2020
Fennec migration automation moved this from Ready for QA to In progress Jan 15, 2020
@jonalmeida jonalmeida added the eng:qa:needed QA Needed label Jan 15, 2020
@grigoryk grigoryk moved this from In progress to Ready for QA in Fennec migration Jan 15, 2020
@ebalazs-sv
Copy link

@jonalmeida I had tested this on Release, Beta, Nightly migration builds 01/15 with Samsung Galaxy S8 (Android 9), Huawei Honor 8 (Android 7.0), Xiaomi Mi4i (Android 5.0.2), following the steps:

  1. On Fennec Release open a page and go to Menu -> Settings -> Share -> Fennec Nightly;
  2. Replace Fennec Nightly with Fenix Nightly;
  3. On Fennec Release open a page and go to Menu -> Settings -> Share -> Fenix Nightly;
  4. Observe the tab received on Fenix Nightly.

The tab sent from Fennec to Fenix is received.
I had tested this also from sending tabs from Nightly to Release.

Is this the required testing scenario? Thanks!

@jonalmeida
Copy link
Contributor Author

@ebalazs-sv

At step 4, did you have to open the app to see the tab appear?

If the app is in the background or in foreground already, you should see the tab appear. If it appears by switching between the two then that would mean we didn't receive the tab from push, but by a sync when the app is in the foreground.

@ebalazs-sv
Copy link

ebalazs-sv commented Jan 15, 2020

At step 4 the tab appear, I don't have to switch between the apps. Is this correct? Thank you!

@jonalmeida
Copy link
Contributor Author

At step 4 the tab appear, I don't have to switch between the apps. Is this correct? Thank you!

To clarify, the tab should appear without having to bring Fenix to the foreground after the tab is sent.

@ebalazs-sv
Copy link

ebalazs-sv commented Jan 16, 2020

To clarify, the tab should appear without having to bring Fenix to the foreground after the tab is sent.

Yes, the tab appear without having to bring Fenix to the foreground after the tab is sent.
I will move this to Done. Thanks!

@ebalazs-sv ebalazs-sv moved this from Ready for QA to Done in Fennec migration Jan 16, 2020
@ebalazs-sv ebalazs-sv added eng:qa:verified QA Verified and removed eng:qa:needed QA Needed labels Jan 16, 2020
@liuche liuche mentioned this issue Jan 22, 2020
32 tasks
@jonalmeida
Copy link
Contributor Author

Closing since this is verified.

Fennec migration automation moved this from Done to Ready for QA Feb 24, 2020
@ebalazs-sv
Copy link

This was verified as fixed in my previous comment, so I will move this to Done. Thanks!

@ebalazs-sv ebalazs-sv moved this from Ready for QA to Done in Fennec migration Feb 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
E5 Estimation Point: about 5 days eng:qa:verified QA Verified Feature:Migration
Projects
No open projects
Development

No branches or pull requests

4 participants