<commit_before>This document contains testing scenarios for selenium system tests in EnMasse.

=== Scenarios for AddressTest
* testCreateDeleteQueue
- For brokered/standard address space try to create/delete queues with all available plans
- Brokered:
- Standard:

* testCreateDeleteTopic
- For brokered/standard address space try to create/delete topics with all available plans
- Brokered:
- Standard:

* testCreateDeleteAnycast
- For standard address space try to create/delete anycast with all available plans

* testCreateDeleteMulticast
- For standard address space try to create/delete multicast with all available plans

* testFilterAddressesByName
- Create 2 queues: queue-via-web-N where N=1,3
- Create 2 topics: topic-via-web-M where M=0,2
- add filter for “web” and verify that 4 items are visible
- add filter for “via” and verify that 4 items are visible
- Remove filter “web”
- verify that 4 items is visible
- add filter for “queue” and verify that 2 items is visible
- Remove all filters and verify that 4 items is visible
- Remove addresses

* testFilterAddressesByType
- Create 2 queues: queue-via-web-N where N=1,3
- Create 2 topics: topic-via-web-M where M=0,2
- Filter all queues and verify that 2 items are visible
- Filter all topics and verify that 2 items are visible
- Remove addresses

* testSortAddressesByName
- Create 2 queues: queue-via-web-N where N=1,3
- Create 2 topics: topic-via-web-M where M=0,2
- Sort those addresses by name(ASC/DESC) and verify order
- Remove addresses

* testSortAddressesByClients
- Create 2 queues: queue-via-web-N where N=1,3
- Create 2 topics: topic-via-web-M where M=0,2
- Attach M+1 consumer to each topic and N+1 consumer to each queue
- Sort addresses by count of receivers asc and verify order
- Sort addresses by count of receivers desc and verify order
- Kill receivers
- Create M+1 senders and start sending messages to each topic (1 messages per 1 second)
- Sort addresses by count of senders asc and verify order
- Sort addresses by count of senders desc and verify order
- Kill senders
- Remove addresses

=== Scenarios for ConnectionTest
test steps are TODO

* testSortConnectionsByClientID
* testSortConnectionsByHostname
* testSortConnectionsBySenders
* testSortConnectionsByReceivers
* testFilterConnectionsByContainer
* testFilterConnectionsByHostname
* testFilterConnectionsByUser
* testFilterConnectionsByEncrypted
- Create queue: queue-via-web-connections-encrypted
- Atach 5 consumers to this queue
- Add filter for encrypted and verify count
- Remove all filters
- Add filter for unencrypted and verify count
- Remove all filters
- Remove queue

* Scenarios for Authentication/AuthorizationTest.java
* Test for: Username right, password right (using popup login window)
* Test for: Username right, password wrong (using popup login window)
* Test for: Username wrong, password right (using popup login window)
* Test for: Username wrong, password wrong (using popup login window)
* Test for: Username right, password missing (using popup login window)
* Test for: Username missing, password right (using popup login window)
* Test for: Username missing, password missing (using popup login window)
* testLogoutUser *_this functionality isn't probably implemented at this moment_*

=== Scenarios for AddressSpaceTest
!TODO<commit_msg>UPD scenarios<commit_after>This document contains testing scenarios for selenium system tests in EnMasse.

=== Scenarios for AddressTest
* testCreateDeleteQueue
- For brokered/standard address space try to create/delete queues with all available plans
- Brokered:
- Standard:

* testCreateDeleteTopic
- For brokered/standard address space try to create/delete topics with all available plans
- Brokered:
- Standard:

* testCreateDeleteAnycast
- For standard address space try to create/delete anycast with all available plans

* testCreateDeleteMulticast
- For standard address space try to create/delete multicast with all available plans

* testFilterAddressesByName
- Create 2 queues: queue-via-web-N where N=1,3
- Create 2 topics: topic-via-web-M where M=0,2
- add filter for “web” and verify that 4 items are visible
- add filter for “via” and verify that 4 items are visible
- Remove filter “web”
- verify that 4 items is visible
- add filter for “queue” and verify that 2 items is visible
- Remove all filters and verify that 4 items is visible
- Remove addresses

* testFilterAddressesByType
- Create 2 queues: queue-via-web-N where N=1,3
- Create 2 topics: topic-via-web-M where M=0,2
- Filter all queues and verify that 2 items are visible
- Filter all topics and verify that 2 items are visible
- Remove addresses

* testSortAddressesByName
- Create 2 queues: queue-via-web-N where N=1,3
- Create 2 topics: topic-via-web-M where M=0,2
- Sort those addresses by name(ASC/DESC) and verify order
- Remove addresses

* testSortAddressesByClients
- Create 2 queues: queue-via-web-N where N=1,3
- Create 2 topics: topic-via-web-M where M=0,2
- Attach M+1 consumer to each topic and N+1 consumer to each queue
- Sort addresses by count of receivers asc and verify order
- Sort addresses by count of receivers desc and verify order
- Kill receivers
- Create M+1 senders and start sending messages to each topic (1 messages per 1 second)
- Sort addresses by count of senders asc and verify order
- Sort addresses by count of senders desc and verify order
- Kill senders
- Remove addresses

=== Scenarios for ConnectionTest
test steps are TODO

* testSortConnectionsByClientID
* testSortConnectionsByHostname
* testSortConnectionsBySenders
* testSortConnectionsByReceivers
* testFilterConnectionsByContainer
* testFilterConnectionsByHostname

* testFilterConnectionsByUser
- Create new user via API with username/password:pavel/enmasse
- Create queue: queue-via-web-connections-users
- Attach 5 consumer with user pavel
- Attach 10 consumers with default user: test/test
- Verify count of connections (15 expected)
- Add filter for username: "test"
- Verify count of connections and user names (10 expected)
- Add filter for username: "pavel"
- Verify count of connections and user names (should be empty)
- Remove filter with username "test"
- Verify count of connections and user names (5 expected)
- Clear all filters
- Verify count of connections (15 expected)
- Remove user "pavel"
- Remove queue

* testFilterConnectionsByEncrypted
- Create queue: queue-via-web-connections-encrypted
- Atach 5 consumers to this queue
- Add filter for encrypted and verify count
- Remove all filters
- Add filter for unencrypted and verify count
- Remove all filters
- Remove queue

* Scenarios for Authentication/AuthorizationTest.java
* Test for: Username right, password right (using popup login window)
* Test for: Username right, password wrong (using popup login window)
* Test for: Username wrong, password right (using popup login window)
* Test for: Username wrong, password wrong (using popup login window)
* Test for: Username right, password missing (using popup login window)
* Test for: Username missing, password right (using popup login window)
* Test for: Username missing, password missing (using popup login window)
* testLogoutUser *_this functionality isn't probably implemented at this moment_*

=== Scenarios for AddressSpaceTest
!TODO
{'fraction_non_alphanumeric': 0.05987611837577426, 'fraction_numerical': 0.011562284927735719, 'mean_word_length': 4.663289166017147, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1116123', 'n_tokens_mistral': 2008, 'n_tokens_neox': 1935, 'n_words': 912}