Bug 2044296 - Disable Sync/FxA related tests for firefox enterprise#988
Bug 2044296 - Disable Sync/FxA related tests for firefox enterprise#988victhorlopez wants to merge 1 commit into
Conversation
1rneh
left a comment
There was a problem hiding this comment.
I added browser_contextmenu_sendtab.js link cause it was failing and has a bunch of FxA logic
Sending tabs is supported in enterprise build so I took a closer look at what was failing as we don't generally want to have regressed sending tabs to other devices.
- It seems only
test_sendTabToDevice_showsConfirmationHint_fxaandtest_sendTabToDevice_showsConfirmationHint_onOverflowMenufail because they trigger and assert that the fxa toolbar button becomes visible. - I noticed
test_tab_contextmenu_send_to_mobilepassed although we don't want to support Firefox Enterprise on mobile, hence we shouldn't offer that option.
In conclusion, instead of skipping the whole test suite, we can wrap those three tests if !AppConstants.MOZ_ENTERPRISE (unfortunately we can't skip-if on a task level) and we should also fix not supporting sending tabs to mobile and have test coverage for that.
okay will do, there is this by the way for skipping on task level |
Nice find! Thanks for sharing! |
1- I did the change I would expect this never retrieves mobile devices from backend link otherwise we would need to filter them in that function for enterprise |
|
Use this in the url ?w=1 to get rid of the indentation noise.. |
| availableCommands: { | ||
| "https://identity.mozilla.com/cmd/open-uri": "baz", | ||
| }, |
There was a problem hiding this comment.
yes, I run ./mach lint --fix
There was a problem hiding this comment.
I'm wondering if it warrants an upstream fix as well to make sure we reduce risks of conflicts
There was a problem hiding this comment.
do you have ideas for a workaround? Should I add a helper function add_task_with_skip()
so we can have the original indentation? (and the test skips enterprise by default)
There was a problem hiding this comment.
I'm not worried about conflicts on the add_task changes at the prototype place, rather the rest of the linting changes. I assume without you get a linting failures?
There was a problem hiding this comment.
I assume without you get a linting failures? let me try
There was a problem hiding this comment.
There was a problem hiding this comment.
then we have to live with it :(
There was a problem hiding this comment.
still worth I think fixing upstream to avoid risk of merge regressing just the lint?
| availableCommands: { | ||
| "https://identity.mozilla.com/cmd/open-uri": "boo", | ||
| }, |
34d8ebb to
b5bcbcd
Compare
|
Apologies for the noise... I had to disable yet another one
|
Description
Bugzilla: Bug-2044296
Dependencies / Related Issues
Screenshots
Testing