gitlab-org/quality/performance 2.0.0

on GitLab

We’re thrilled to announce the release of GPT v2.0.0!

To achieve consistent and comparable results GPT is now designed primarily to be used with an updated and expanded test data set. This allows you to validate if the target environment is performing as expected by testing with the exact same data and then comparing the results with our GitLab Reference Architectures.

To facilitate this change we’ve developed a new helper tool, the GPT Data Generator, that will update your environment to have all of the required test data as well as update it if required!

As this is a major release and contains several breaking changes in regards to configuration and test data. Please refer to the upgrade notes to learn more.

Highlights:

• GPT’s test data has been updated and expanded to include more data such as Projects and Groups. To make this easier a new helper tool, GPT Data Generator, has been created to set up and update all data !155
  • GPT Data Generator is also available as a Docker Image !162
• New test additions and changes. !167, !173, !178
• New directory structure for the GPT !166
• Tests will now be retried once if they failed to help ensure they are real failures !187
• Various bug fixes and improvements !179 !181 !183 !185 !182
• Documentation has been updated for this release as well as expanded with further guidance in several areas !188
• Individual test result summaries are now saved to the results folder !189

Breaking Changes:

• To facilitate the new test data config files have changed:
  • Environment config files have changed in structure !165, !172
  • New Large Project Data Configuration file !165
  • Removed repo_storage config !164
  • All config files have been moved into the aptly named config folder !166
    • Note that this may affect usage via Docker. Please refer to the docs for latest guidance.
• Access Tokens are now required for all tests !159
• The default results folder has changed location to the root folder (k6/results to results).

Upgrade Notes:

• For users upgrading from v1.x they should follow the Preparing the Environment documentation steps again to set up the new test data.