[tests-only][full-ci] add test to disable email notifications by federated user

[prashant-gurung899]

Description

This PR adds test for disabling mail notification by federated user.

Scenario: federated user disables email notification

Related Issue

• Part of: [QA] Tests for disabling notification settings #10802

Motivation and Context

How Has This Been Tested?

• Locally
• CI

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

.

[amrita-shrestha]

current ocm setup doesn't throw any notification related to federated share. So i don't see any sense on adding step related to federated share. Did we get confirmation from developer how they going to implement federated share notification? developer can make different event for federated share and internal share.
If developer make different event then our scenario doesn't work like it should work.
So until developer implement feature or confirm us about concept and event type we should not add such scenario in assumption basis

[prashant-gurung899]

current ocm setup doesn't throw any notification related to federated share. So i don't see any sense on adding step related to federated share. Did we get confirmation from developer how they going to implement federated share notification? developer can make different event for federated share and internal share. If developer make different event then our scenario doesn't work like it should work. So until developer implement feature or confirm us about concept and event type we should not add such scenario in assumption basis

Alright then! If that's the case, should we halt this PR and other OCM notification related PRs for now?
CC @nirajacharya2 @saw-jan @amrita-shrestha

[amrita-shrestha]

current ocm setup doesn't throw any notification related to federated share. So i don't see any sense on adding step related to federated share. Did we get confirmation from developer how they going to implement federated share notification? developer can make different event for federated share and internal share. If developer make different event then our scenario doesn't work like it should work. So until developer implement feature or confirm us about concept and event type we should not add such scenario in assumption basis

Alright then! If that's the case, should we halt this PR and other OCM notification related PRs for now? CC @nirajacharya2 @saw-jan @amrita-shrestha

@prashant-gurung899 i think you can get confirmation from developer about event type.
@nirajacharya2 @saw-jan you guys want to discuss in standup ?

[prashant-gurung899]

@prashant-gurung899 i think you can get confirmation from developer about event type. @nirajacharya2 @saw-jan you guys want to discuss in standup ?

I have confirmed with the developer that the event name for OCM shares will include the term OCM.
I think that won't be much of a problem in future to refactor in out tests.

CC @saw-jan @nirajacharya2 @amrita-shrestha

[amrita-shrestha]

@prashant-gurung899 i think you can get confirmation from developer about event type. @nirajacharya2 @saw-jan you guys want to discuss in standup ?

I have confirmed with the developer that the event name for OCM shares will include the term OCM. I think that won't be much of a problem in future to refactor in out tests.

CC @saw-jan @nirajacharya2 @amrita-shrestha

so disabling email notification will disable all email (internal email and federated email) ?

[prashant-gurung899]

so disabling email notification will disable all email (internal email and federated email) ?

That's what the expected behaviour is. We aren't sure as OCM notifications aren't implemented yet.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[saw-jan]

If the OCM notification events are not implemented yet then IMO we should wait for the implementation before adding the tests. Because we don't know what the behaviour and expectations will be. If everything follows our test expectations, then that's good. We can hold this until the implementation.

[prashant-gurung899]

If the OCM notification events are not implemented yet then IMO we should wait for the implementation before adding the tests. Because we don't know what the behaviour and expectations will be. If everything follows our test expectations, then that's good. We can hold this until the implementation.

Okay! I am holding my OCM notification PRs until further implementation.

[saw-jan]

Please, move it to the backlog blocked

[prashant-gurung899]

Moving this PR to backlog blocked because OCM notification events are not implemented yet. See comment.