Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat/integ tests notifications #1597

Open
wants to merge 22 commits into
base: main
Choose a base branch
from

Conversation

noah-paige
Copy link
Contributor

Feature or Bugfix

  • Feature

Detail

  • Integration Tests Notifications

Relates

Security

Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

  • Does this PR introduce or modify any input fields or queries - this includes
    fetching data from storage outside the application (e.g. a database, an S3 bucket)?
    • Is the input sanitized?
    • What precautions are you taking before deserializing the data you consume?
    • Is injection prevented by parametrizing queries?
    • Have you ensured no eval or similar functions are used?
  • Does this PR introduce any functionality or component that requires authorization?
    • How have you ensured it respects the existing AuthN/AuthZ mechanisms?
    • Are you logging failed auth attempts?
  • Are you using or adding any cryptographic features?
    • Do you use a standard proven implementations?
    • Are the used keys controlled by the customer? Where are they stored?
  • Are you introducing any new policies/roles/users?
    • Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@dlpzx dlpzx self-requested a review October 1, 2024 07:31
assert_that(list_notifications(client1, filter={'read': True})).is_not_none()
assert_that(list_notifications(client1, filter={'unread': True})).is_not_none()
assert_that(list_notifications(client1, filter={'archived': True})).is_not_none()


def test_count_unread_notification(client1, session_share_1):
def test_count_unread_notification(client1):
assert_that(count_unread_notificiations(client1)).is_greater_than_or_equal_to(0)


Copy link
Contributor

Choose a reason for hiding this comment

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

countReadNotifications and countDeletedNotifications are not used in the frontend. Maybe we should delete them from the backend and remove the tests for countReadNotifications. wdyt?

Copy link
Contributor

Choose a reason for hiding this comment

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

deleteNotification is also not used in the frontend

Copy link
Contributor Author

Choose a reason for hiding this comment

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

removed all 3 ops

response = client.query(query=query)
return response.data.countUnreadNotifications


Copy link
Contributor

Choose a reason for hiding this comment

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

As commented already, count_read_notificiations and count_deleted_notificiations are not used in the FE

Copy link
Contributor Author

Choose a reason for hiding this comment

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

removed all 3 ops

assert_that(list_notifications(client1)).is_not_none()
assert_that(list_notifications(client1, filter={'read': True})).is_not_none()
assert_that(list_notifications(client1, filter={'unread': True})).is_not_none()
assert_that(list_notifications(client1, filter={'archived': True})).is_not_none()
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we can assert the keys of the response, not only that it is not None

Copy link
Contributor Author

Choose a reason for hiding this comment

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

asserted contains_key(...)

Copy link
Contributor

@dlpzx dlpzx left a comment

Choose a reason for hiding this comment

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

The part of notifications is fine, I am not approving because of the changes in shares; which I am not sure how they interact with other shares tests

@noah-paige
Copy link
Contributor Author

noah-paige commented Oct 4, 2024

The part of notifications is fine, I am not approving because of the changes in shares; which I am not sure how they interact with other shares tests

Is there another PR for shares that I should wait for on shares before testing once more that all shares tests + notification tests work in tandem? @dlpzx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants