-
Notifications
You must be signed in to change notification settings - Fork 24
Testing Instructions for Critical Flows
maria-anguas edited this page Dec 20, 2023
·
1 revision
Test Steps:
- Download zip from https://github.com/10up/ads-txt
- Install the ads.txt plugin through the WordPress admin panel.
- Choose the zip. file downloaded.
- Activate the plugin.
- Verify that the plugin activation completes without errors.
Expected Result:
The ads.txt plugin is successfully installed and activated.
Test Steps:
- Navigate to the plugin settings page.
- Configure the plugin settings, including publisher ID, accounts, and other relevant information.
- Save the settings and trigger the generation of the ads.txt file.
Expected Result:
- The ads.txt file is generated successfully based on the configured settings.
- The file contains the correct information as per the publisher's specifications.
Test Steps:
- Access the website's root domain (e.g., https://example.com/ads.txt).
- Verify that the ads.txt file is accessible and can be viewed in a web browser.
Expected Result:
- The ads.txt file is located at the root domain.
- The file is accessible, and its contents are displayed in the browser.
Test Steps:
- Manually edit the ads.txt file generated by the plugin.
- Save the changes.
- Revisit the plugin settings page.
Expected Result:
- The plugin detects that the ads.txt file has been manually edited and provides a notification or warning.
- The plugin does not overwrite the manually edited file.
Test Steps:
- Make changes to the configuration in the plugin settings.
- Save the changes and verify if the ads.txt file is automatically updated.
Expected Result:
- Changes in the plugin settings trigger the automatic update of the ads.txt file.
- The updated file reflects the new configuration.
Test Steps:
- Deactivate the ads.txt plugin.
- Access the website's root domain and check for the presence of the ads.txt file.
Expected Result:
- Deactivating the plugin should remove or disable the ads.txt file.
- The file should no longer be accessible at the root domain.
Test Steps:
- Intentionally introduce errors in the plugin configuration.
- Save the settings and check for error messages.
Expected Result:
- The plugin should provide clear error messages for configuration issues.
- The error messages should guide the user in resolving the issues.
Test Steps:
- Test the plugin with different versions of WordPress.
- Verify its compatibility with popular themes and other plugins.
Expected Result:
- The ads.txt plugin should be compatible with various versions of WordPress.
- It should work seamlessly with different themes and plugins without causing conflicts.
Test Steps:
- Monitor the website's performance with the ads.txt plugin activated.
- Measure page load times and server response times.
Expected Result:
- The ads.txt plugin should have minimal impact on the website's performance.
- Page load times and server response times should remain within acceptable limits.