Suggestions for Smoke Testing an Installation
After an on-premise installation or upgrade, we suggest to run a smoke test to make sure that the application works fine within its IT environment.
The exact steps and use cases to be tested depend on your specific IT environment and custom configuration, so the following steps are only suggestions and will not be 100% applicable or complete:
| Use Case | Actions to Test | Hints upon Failure |
|---|---|---|
| Workspace Creation | Create a workspace | Check write privileges on Database Check …/stages/logs/stages.log for errors |
| Process Modeling | Create activities, work products, and roles | Check write privileges on Database Check …/stages/logs/stages.log for errors |
| Process Versioning | Create a process version | Check if the correct metamodel is installed Check that WSS connections are allowed through the reverse proxy Check …/stages/logs/stages.log for errors |
| Process Visualizations | Go to a workflow and click through all visualization tabs and options | Check if the correct metamodel is installed Check …/stages/logs/diagram.log for errors |
| EMail Notifications | Run a process release automation and check if the users to be notified correctly receive email notifications | Check if the email server connection is correctly set up in config.xml Check …/stages/logs/notify.log for errors |
| Feedback | Create a feedback item or comment for a workflow or activity | Check if the connection to the external item tracking tool (JIRA, etc.) is working correctly Check …/stages/logs/stages.log for errors |
| Reports | Run a report and change its parameters | Check if the connection to the reporting component works correctly Check if the CA certificate chain is imported into the truststore Check …/stages/logs/stages.log for errors |
| PDF Export | Generate a few PDF exports | Check if the connection to the PDF generator works correctly Check if the CA certificate chain is imported into the truststore Check …/stages/logs/stages.log for errors |
| CMS Integration | Go to a file that is managed in an external CMS (e.g. Sharepoint, SVN) | Check if the connection to the CMS is correctly set up and working Check …/stages/logs/stages.log for errors |
| Search | Search for a few terms in the global search | Check if the Elasticsearch component is running (Linux) or if the “Stages Search” service is running (Windows) Check …/stages/elasticsearch/logs/elasticsearch.log for errors |
| Single Sign On | Try to log in as a normal user via SSO | Check if SSO has been correctly set up in config.xml Check …/stages/logs/stages.log for errors |