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.

Sign up for GitHub

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

Jump to bottom

Add high volume Tests #36

Open
helkv opened this issue Oct 29, 2018 · 0 comments
Open

Add high volume Tests #36

helkv opened this issue Oct 29, 2018 · 0 comments

Comments

@helkv
Copy link

helkv commented Oct 29, 2018

Ticket for implementing high volume tests for imeji.

A currently revealed bug (imeji Tickets: #1049 + #1052) showed that there were problems with collections containing more than 500 items. Therefore some selenium tests should be created to check whether imeji handles large amount of data correctly.

These test should show that the main imeji functions (workflows) work correctly, also with a high data volume. These test are NO Load-Tests / Performance-Tests.

The selenium test classes should cover the following sections:

  • Upload/Edit/Delete more than 500 itms (in one collection)
  • Create/Edit/Delete more than 500 collections
  • Create/Edit/Delete more than 500 users
  • Create/Edit/Delete more than 500 usergroups
  • Create/Edit/Delete more than 500 statements
helkv added a commit that referenced this issue Oct 31, 2018
@helkv
#36 Added TODO to UploadMultipleItems
a113fc6 
- The test items are not committed yet (so the UploadMultipleItems test
can only be run locally)
- TODO: Commit/Push appropriate test items
helkv added a commit that referenced this issue Oct 31, 2018
@helkv
#36 Added TODO to CreateMultipleCollections
bba5a5a 
- The used methods openCollectionByTitle and collectionPresent must be
refactored () to find collections which are not on the first
collections-page
helkv added a commit that referenced this issue Oct 31, 2018
@helkv
#36 Refactored CreateMultipleUsers
3fc1ef0 
- Added check for the number of created users to CreateMultipleUsers
- Added userCount() to BrowseUsersPage
- Added wait to NewUserPage.createNewUser()
helkv added a commit that referenced this issue Oct 31, 2018
@helkv
#36 Refactored CreateMultipleUserGroups
41be1b6 
- Added check for the number of created userGroups to
CreateMultipleUserGroups
- Added userGroupsCount() to UserGroupsOverviewPage
helkv added a commit that referenced this issue Oct 31, 2018
@helkv
#36 Refactored CreateMultipleStatements
1b6597d 
- Added check for the number of created statements to
CreateMultipleStatements
- Added statementCount() to BrowseStatementsPage
helkv added a commit that referenced this issue Nov 6, 2018
@helkv
#36 Refactored BrowseStatementsPage
ed6548d 
- Refactored the deleteStatement() method
- Sometimes the Selenium-Click-method does not work for certain
webelements. Therefore the JavaScript click() method is used instead for
the two delete-buttons
helkv added a commit that referenced this issue Nov 6, 2018
@helkv
#36 Refactored CreateMultipleStatements
d64c1ba 
- Small changes in CreateMultipleStatements
helkv added a commit that referenced this issue Nov 6, 2018
@helkv
#36 Small Refactoring of NewStatementPage
61da9a2 
- Added a wait to the submit() method
helkv added a commit that referenced this issue Nov 6, 2018
@helkv
#36 Refactored UserGroupsOverviewPage
129b190 
- Refactored the findUserGroupByName() method: Optimized the search for
a usergroup (optimized runtime).
- Refactored a wait in the NewUserGroupPage
helkv added a commit that referenced this issue Nov 6, 2018
@helkv
#36 Refactored CreateMultipleUserGroups
229b1bc 
- Small changes in CreateMultipleUserGroups
helkv added a commit that referenced this issue Nov 6, 2018
@helkv
#36 Refactored CreateMultipleUsers
39ccd12 
- Small changes in CreateMultipleUsers
- Small refactoring in BrowseUsersPage
helkv added a commit that referenced this issue Nov 7, 2018
@helkv
#36 Refactored: CreateMultipleCollections + CreateMultipleUsers
82ad8e2 
- Used the new search-methods to first search+find the user/collection
and then delete it. Using the imeji-search is more efficient than using
only the delete method.
@helkv helkv mentioned this issue Nov 19, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@helkv