This page describes tests to be performed on the collaboration software to determine availability and usability.
----
Machine tests
Title
|
Description
|
Host availability
|
Checks whether the host is up and is reachable
|
Host resources
|
Checks whether disk, memory and cpu usage is below a specified threshold
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
Confluence tests
Title
|
Description
|
Availability test
|
Checks that Confluence is up and is not returning an error page on access to the base url.
|
Login test
|
Checks that a user can login to Confluence, also verifies that Crowd/LDAP can be connected to and users/groups read
|
Read test
|
Checks that spaces and pages can be read
|
Write Test
|
Checks that spaces, pages and attachments can be written.
|
User test
|
Checks that a user/group can be added, modified and deleted from within Confluence.
|
Mail test
|
Checks that mail can be sent from Confluence
|
| |
|
| |
|
| |
|
Alfresco tests
Title
|
Description
|
Availability test
|
Checks that Alfresco is up and is not returning an error page on access to the base url.
|
Login test
|
Checks that a user can login to Alfresco, also verifies that LDAP can be connected to and users/groups read
|
Read test
|
Checks that spaces and content can be read
|
Write Test
|
Checks that spaces and content can be written.
|
Mail test
|
Checks that mail can be sent from Alfresco
|
| |
|
| |
|
| |
|
Jira tests
Title
|
Description
|
Availability test
|
Checks that Jira is up and is not returning an error page on access to the base url.
|
Login test
|
Checks that a user can login to Jira, also verifies that LDAP can be connected to and users/groups read
|
Read test
|
Checks that projects and issues can be read
|
Write Test
|
Checks that issues and attachments can be written.
|
Mail test
|
Checks that mail can be sent from Jira
|
| |
|
| |
|
| |
|
Page Operations
Browse Space