In this article, we will provide a comprehensive overview of Tests on Deploy, a feature available in Flusk Vault that can help improve the security of your application. We will also provide guidance on how to configure Tests on Deploy and discuss its limitations and performance impact.
What are Tests on Deploy?
Tests on Deploy allows you to automatically run tests whenever a new version of your application is deployed to the live branch.
This feature helps to prevent issues that may have been forgotten during the development process from reaching the production version of your application, thereby contributing to its overall security.
How to Configure Tests on Deploy
Before enabling Tests on Deploy, ensure that you have an active Flusk Vault license and that the live version/branch is enabled in Flusk Vault.
Once you have met these prerequisites, follow these steps to enable Tests on Deploy:
Navigate to "Security" -> "Tools & More" tab of your Flusk Vault dashboard.
Choose "Test Schedule".
Click on the "Enable" button next to "Automatic test on deploy".
Limitations
While Tests on Deploy is a valuable tool for improving the security of your application, there are some limitations that you should be aware of.
These include:
Recurrence
To prevent server surcharging and ensure stable system performance, our security tool runs tests on deployment at a minimum recurrence of 90 minutes.
Other Restrictions
Tests on deployment will not run if any other automatic tests were conducted within the last 90 minutes. This includes tests on deployment, scheduled tests, and tests conducted through the API.
Additionally, tests on deployment will not run if a manual test was conducted within the last 15 minutes.
Due to the lower priority in the queue, tests on deployment and other automatic tests may take longer to start and complete than manual tests.
Tests on deployment and other automatic tests will not run if your Flusk Vault account has been inactive for more than 90 days.
Performance Impact
Enabling Tests on Deploy has no performance impact on your application or your application's editor.
This is because we do not constantly ping your application for new deploys. Instead, we use a webhook-like system to detect when your application has been deployed.