Skip to content

Encourage creation of seed data

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

When reviewing merge request, it can often be quite tricky to setup GDK to be able to test/recreate/validate.

Setting a project config in a certain way, creating issues, identities, pipelines, artefacts etc

Wouldn't it be great if we always had something in the GDK seed data so we could just say: "Go to crm test project and..." or "go to merge request with code coverage and terraform output and...

Perhaps we should already being doing this and i've overlooked the documentation/advice. But assuming we don't already have it, should we get this into our documentation and spread the word?

It would clearly be a mammoth effort for any one person/team to take on the effort, but each time we work on a merge request, we should take the opportunity to consider whether a tweak to existing, or some additional seed data would help?

I can only take credit for a single instance in the past when I had the forethought to do this: db/fixtures/development/32_crm.rb

Thoughts?

Edited by 🤖 GitLab Bot 🤖