Skip to content

Bug 2036167 - Enterprise: Access Connector testing#825

Merged
lissyx merged 1 commit intomozilla:enterprise-mainfrom
lissyx:enterprise-bug2036167_access_connectors_tests
May 4, 2026
Merged

Bug 2036167 - Enterprise: Access Connector testing#825
lissyx merged 1 commit intomozilla:enterprise-mainfrom
lissyx:enterprise-bug2036167_access_connectors_tests

Conversation

@lissyx
Copy link
Copy Markdown
Contributor

@lissyx lissyx commented Apr 30, 2026

Provide basic testing of access connector from policies pushed by the console, either being set enabled by default (from console) or disabled by default (from console). Coverage ensures prefs and set at expected values, and locked when applied and correctly unlocked and reset after.

Also try to load data with the policy applied and verify there is a proxy error because no proxy is really setup to handle the connections.

Bugzilla: Bug-2036167

Testing

  • Added tests
  • Manual testing performed

@lissyx lissyx requested a review from jporter-dev April 30, 2026 19:46
@lissyx lissyx added bug Something isn't working branch:main PR that should be merged on enterprise-main branch labels Apr 30, 2026
Comment thread testing/enterprise/test_felt_browser_access_connector.py Outdated

def run_load_page_with_access_connector(self):
try:
self.open_tab_child("https://support.mozilla.org/")
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there value in checking a non matching URL loads properly?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there is value in checking this since we currently configure it to operate in "inclusion mode" - checking both paths will make sure it's operating properly. If we only check one, we can miss cases of misconfiguration, inclusion mode breaking, or issues with the channel filtering/pattern matching.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A good example is http://support.mozilla.org since the pattern in the policy is specific to https. Can also add https://example.com for one that's entirely different.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lissyx the PR is looking good - just need to add the "non-matching url when AccessConnector is enabled" case to make sure the inclusion mode is working as expected.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jporter-dev I've added tests to /ping of the console

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

http://support.mozilla.org is unfortunately redirecting to https so ...

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah didn't catch that addition, that should cover it then!

@lissyx lissyx force-pushed the enterprise-bug2036167_access_connectors_tests branch from 85da431 to 6221221 Compare April 30, 2026 20:49
@lissyx lissyx self-assigned this May 1, 2026
Comment thread testing/enterprise/test_felt_browser_access_connector.py Outdated

def run_load_page_with_access_connector(self):
try:
self.open_tab_child("https://support.mozilla.org/")
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there is value in checking this since we currently configure it to operate in "inclusion mode" - checking both paths will make sure it's operating properly. If we only check one, we can miss cases of misconfiguration, inclusion mode breaking, or issues with the channel filtering/pattern matching.

Comment thread testing/enterprise/test_felt_browser_access_connector.py Outdated
Comment thread testing/enterprise/felt_tests.py Outdated
Comment thread testing/enterprise/test_felt_browser_access_connector.py Outdated
Comment thread testing/enterprise/test_felt_browser_access_connector.py Outdated
@lissyx lissyx force-pushed the enterprise-bug2036167_access_connectors_tests branch 3 times, most recently from 492b46e to 3d055bd Compare May 4, 2026 13:11
Provide basic testing of access connector from policies pushed by the
console, either being set enabled by default (from console) or disabled
by default (from console). Coverage ensures prefs and set at expected
values, and locked when applied and correctly unlocked and reset after.

Also try to load data with the policy applied and verify there is a
proxy error because no proxy is really setup to handle the connections.
@lissyx lissyx force-pushed the enterprise-bug2036167_access_connectors_tests branch from 3d055bd to 5f38e85 Compare May 4, 2026 13:55
@lissyx lissyx requested a review from jporter-dev May 4, 2026 13:56
@lissyx lissyx merged commit a63478f into mozilla:enterprise-main May 4, 2026
68 of 69 checks passed
@lissyx lissyx added the uplift-to-beta PR that needs an uplift to beta label May 4, 2026
@lissyx lissyx deleted the enterprise-bug2036167_access_connectors_tests branch May 4, 2026 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch:main PR that should be merged on enterprise-main branch bug Something isn't working uplift-to-beta PR that needs an uplift to beta

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants