SpeedCurve Synthetic can be integrated into your continuous integration or continuous deployment environment as a way to test for and react to performance issues.

There are two main SpeedCurve components that you will use to provide this integration:

Using these components, you can implement a performance workflow that looks something like this:

  1. Set performance budgets within SpeedCurve.
  2. Change the code or content of your page(s).
  3. Trigger SpeedCurve tests using the Deploy API. (You can also trigger tests via CircleCI, if that's a tool you're already using.)
  4. Receive performance budget alerts if your changes introduced performance issues.
  5. Use these alerts to monitor the performance of your pages and tune your performance budgets.
  6. Cycle back to (2.)

Where does SpeedCurve fit in my CI/CD pipeline?

In a typical CI/CD pipeline, SpeedCurve fits in either the integration testing stage, or the post-deploy stage, or both.

  1. Compile code, run unit tests.
  2. Deploy the build to the testing environment.
  3. Run integration tests, trigger SpeedCurve tests on the testing environment.
  4. Promote the build to the staging/production environment.
  5. Trigger SpeedCurve tests on the staging/production environment.
Did this answer your question?