You are here

gitlab

One of the projects I work on uses GitLab . We host our codes on GitLab, review codes and commits, and use GitLabCI to do all the CI auto-testing jobs before we merge branches.

Normally mock data for TDDUnit Test shouldn't be a difficult job, but once we need to do something more complicated, like searching relations in a graph database, or doing some Integration Test, it became a mess, no matter we put them in test codes or put them in separated files and load when needed:

updating hundreds of records in a thousands-rows mockdataset .

container stats and changes will not be kept across stages and jobs, so in every jobs and stages we need to load them again and again.

it takes time and resources to load data into database, and we don't want to wait them long.