Great question. CheckView does not automatically trigger tests immediately after every WordPress update runs. The main reason is that updates can happen frequently and unpredictably across WordPress core, plugins, themes, and hosting environments. Automatically running tests after every update could quickly consume an entire month’s test allowance and create unnecessary noise, especially for sites with multiple updates per day.
Instead, you can schedule tests to run on a daily, weekly, or monthly basis at specific times that make sense for your workflow. Many agencies schedule tests to run early in the morning or overnight so issues are caught before clients or users notice them.
For more advanced workflows, we’re also working toward supporting this through our API and webhooks. This will allow teams to trigger tests programmatically using tools like Zapier or their own custom update processes. Feel free to reach out if you have any other questions!