What are Versioned Tests and why should you use them?
Proposal
Versioned tests are listed as one of the highlighted features of GitLab CI/CD, but it doesn't look like we use that term or have fully explained what that looks like and what that means. I would like to make a post that talks about versioned tests and what they are, what they do, how to set them up, and why they're a good feature.
This is for the CI Use Case Campaign. Publish date is not time-sensitive, anytime in Q3 is fine.
Checklist
-
If you have a specific publish date in mind (please allow 3 weeks' lead time) -
Include it in the issue title -
Give the issue a due date of a minimum of 2 working days prior -
If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
-
-
If time sensitive -
Add ~"Blog: Priority" label and supplied rationale in description -
Mention @rebecca
to give her a heads up ASAP
-
-
If wide-spread customer impacting or sensitive, mention @nwoods
to give her a heads up ASAP, apply the sensitive label, and check the PR handbook in case you need to open an announcement request instead of a blog post issue -
If the post is about one of GitLab's Technology Partners, including integration partners, mention @TinaS
, apply the Partner Marketing label, and see the blog handbook for more on third-party posts -
If the post is about one of GitLab's customers, mention @KimLock
and@FionaOKeeffe
, apply the Customer Reference Program label, and see the blog handbook for more on third-party posts -
Indicate if supporting an event or campaign -
Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)