-
Notifications
You must be signed in to change notification settings - Fork 46
Testing instructions for critical flows
Test steps:
- Download the plugin
- Go to Plugins > Installed Plugins
- Click on the activate link
- Verify that there are no activation errors or conflicts with other plugins.
- Check that the relevant plugin information appears, i.e. Descriptions, Version.
Expected Result:
No activation errors or conflicts with other plugins should be displayed
Test steps:
- Verify that the plugin allows users to input Azure Storage account credentials.
- Ensure that the plugin supports different storage types (blob, table, queue, file).
- Validate the handling of invalid credentials and configuration parameters.
Expected Result:
Changes should be saved successfully. For invalid credentials, an error message should displayed.
Test steps:
- Test successful connection to Azure Storage using valid credentials.
- Test unsuccessful connection attempts with incorrect credentials.
- Verify handling of network errors during connection.
- Ensure that the plugin supports Azure AD authentication.
Expected Result:
Azure Storage connection should established using valid credentials.
Test steps:
- Upload a file to Azure File Storage and verify its existence.
- Download a file from Azure File Storage and compare it with the original.
- Test file sharing and access control for shared files and directories.
- Verify support for file storage snapshots and versioning.
Expected Result:
A file should be saved to Azure Storage, and file sharing and access control for shared files should be implemented
Test steps:
- Ensure that the plugin supports secure connections (HTTPS).
- Verify that access keys and credentials are encrypted and stored securely.
- Test access control lists (ACLs) for various storage resources.
Expected Result:
The plugin should support secure connections (HTTPS). access keys and credentials should be encrypted and stored securely.
Test steps:
- Test the plugin's response to unexpected errors and exceptions.
- Validate error messages for clarity and accuracy.
- Confirm that the plugin gracefully handles transient errors and retries appropriately.
Expected Result:
The error message should be shown for unexpected errors and exceptions.
Test steps:
- Measure the time taken for various operations under normal load.
- Test the plugin's performance with a large number of concurrent requests.
- Validate that the plugin scales well with increased data volume.
Expected Result:
For various operations, the site should work under normal load. a large number of concurrent requests site should work seamlessly.
Test steps:
- Test the plugin with different WordPress themes.
- Check for conflicts with other plugins.
- Verify that the plugin works seamlessly across different environments.
Expected Result:
The plugin should work seamlessly across different environments.
Test steps:
- Ensure that the plugin adheres to WordPress security best practices.
- Verify that the plugin does not introduce vulnerabilities.
Expected Result:
The plugin should not introduce vulnerabilities.
Test steps:
- Ensure that the plugin generates relevant logs for different operations.
- Verify integration with Azure Monitor and other monitoring tools.
Expected Result:
The plugin should generate relevant logs for different operations.
User Type | Flow Area | Flow Name | Testing Instruction | E2E Status |
---|---|---|---|---|
Backend | Installation and Activation | No activation errors or conflicts with other plugins should be displayed | Refer | |
Backend | Configuration and Setup | Changes should be saved successfully. For invalid credentials, an error message should displayed. | Refer | |
Backend | Connection and Authentication | Azure Storage connection should established using valid credentials. | Refer | |
Backend | File Storage | A file should be saved to Azure Storage, and file sharing and access control for shared files should be implemented | Refer | |
Backend | Security and Access Control | The plugin should support secure connections (HTTPS). access keys and credentials should be encrypted and stored securely. | Refer | |
Backend | Error Handling | The error message should be shown for unexpected errors and exceptions. | Refer | |
Backend | Performance and Scalability | For various operations, the site should work under normal load. a large number of concurrent requests site should work seamlessly. | Refer | |
Backend | Compatibility | The plugin should work seamlessly across different environments. | Refer | |
Backend | Security | The plugin should not introduce vulnerabilities. | Refer | |
Backend | Logging and Monitoring | The plugin should generate relevant logs for different operations. | Refer | |
Frontend | Verify Uploaded media file in Post/Page | Verify Uploaded media file in Post/Page appears properly on FE | Refer |