gitlab-org--gitlab-foss/spec/models/cycle_analytics
Timothy Andrew dd112ef117 Test the staging cycle analytics phase.
Remove overlap from the "start + end" durations in the happy test
case. For the `staging` phase, the end time is the _first_ deployment
that happens after the MR merge.

If we have 5 MRs where the `start_time`s (merge time) are the
same, and all the `end_time`s (deploy to production) a few days from
now, only the earliest deploy will get picked up, because that
consitutes a deploy for _all_ the MRs.

We fix this by removing overlap. Every `start_time` is now generated to
be _after_ the preceding `end_time`.
2016-09-07 12:12:51 +05:30
..
code_spec.rb Generate branch/file names more randomly to avoid failures. 2016-09-07 11:26:07 +05:30
issue_spec.rb Test the code cycle analytics phase. 2016-09-07 10:39:46 +05:30
plan_spec.rb Generate branch/file names more randomly to avoid failures. 2016-09-07 11:26:07 +05:30
review_spec.rb Generate branch/file names more randomly to avoid failures. 2016-09-07 11:26:07 +05:30
staging_spec.rb Test the staging cycle analytics phase. 2016-09-07 12:12:51 +05:30