search

status-im / desktop-qa-automation

Legacy desktop tests
6 stars 12 forks source link

test: admin can kick a member and delete message #625

Closed Valentina1133 closed 5 months ago

Valentina1133 commented 5 months ago

Community admin can delete member's message and kick a member test automated CI run (all tests): https://ci.status.im/job/status-desktop/job/e2e/job/manual/1748/allure/

Screenshot 2024-04-08 at 15 07 18
Valentina1133 commented 5 months ago

@anastasiyaig I placed this test in test_communities.py file, but now I think maybe it's better to create a separate file? Also - we can add steps from this scenario to test_join_community_and_pin_unpin_message - it will reduce time of tests but the scenario will be much longer. What do you think?

anastasiyaig commented 5 months ago

file is fine i think! Lets keep it as is for now pls resolve 1 conflict . Btw regarding it, i dont know how test is passing having wrong string for permission deletion (i fixed the string itself but before i changed that - tests were not failing :D

https://github.com/status-im/desktop-qa-automation/blob/74dfc258c7ddeba44845c96ec8a9056c5d4630d4/constants/community_settings.py#L35

we might want to check on the verification for the toasts in permission tests (separate task)

Valentina1133 commented 5 months ago

file is fine i think! Lets keep it as is for now pls resolve 1 conflict . Btw regarding it, i dont know how test is passing having wrong string for permission deletion (i fixed the string itself but before i changed that - tests were not failing :D

https://github.com/status-im/desktop-qa-automation/blob/74dfc258c7ddeba44845c96ec8a9056c5d4630d4/constants/community_settings.py#L35

we might want to check on the verification for the toasts in permission tests (separate task)

Yes! You are right!

I think I know why. Because in permissions test we check that toast message from constants is in list of toast messages appeared in test, because there are several toast messages at the same time. So I believe we need to check it element by element using indexes to check every toast message separately.