def test_full_isolation_group_creates_next_isolation_group_adds_bucket_range(
self, ):
"""
Rare case: An isolation group with experiment bucket allocations exists, and the
next requested bucket allocation would overflow its total bucket range, and so a
an isolation group with the same name but subsequent instance ID is created.
This is currently treated naively, ie does not account for possible collisions and
overlaps. When this case becomes more common this will likely need to be given
more thought.
"""
experiment = NimbusExperimentFactory.create(
application=self.application)
isolation_group = NimbusIsolationGroupFactory.create(
name=experiment.slug, application=self.application, total=100)
NimbusBucketRangeFactory(isolation_group=isolation_group, count=100)
bucket = NimbusIsolationGroup.request_isolation_group_buckets(
experiment.slug, experiment, 100)
self.assertEqual(bucket.start, 0)
self.assertEqual(bucket.end, 99)
self.assertEqual(bucket.count, 100)
self.assertEqual(bucket.isolation_group.name, isolation_group.name)
self.assertEqual(bucket.isolation_group.instance,
isolation_group.instance + 1)
self.assertEqual(
bucket.isolation_group.randomization_unit,
self.randomization_unit,
)
def test_existing_isolation_group_with_matching_name_but_not_application_is_filtered(
self, ):
"""
Now that isolation groups are bound to applications, we have to check for the
case where isolation groups with the same name but different applications are
treated separately.
"""
name = "isolation group name"
NimbusIsolationGroupFactory.create(
name=name, application=NimbusExperiment.Application.DESKTOP)
experiment = NimbusExperimentFactory.create(
name=name,
slug=name,
application=NimbusExperiment.Application.FENIX)
bucket = NimbusIsolationGroup.request_isolation_group_buckets(
name, experiment, 100)
self.assertEqual(bucket.isolation_group.name, name)
self.assertEqual(bucket.isolation_group.application,
NimbusExperiment.Application.FENIX)
def test_existing_isolation_group_adds_bucket_range(self):
"""
Rare case: An isolation group with no buckets allocated already exists.
This may become common when users can create their own isolation groups
and then later assign experiments to them.
"""
experiment = NimbusExperimentFactory.create()
isolation_group = NimbusIsolationGroupFactory.create(
name=experiment.slug)
bucket = NimbusIsolationGroup.request_isolation_group_buckets(
experiment.slug, experiment, 100)
self.assertEqual(bucket.start, 0)
self.assertEqual(bucket.end, 99)
self.assertEqual(bucket.count, 100)
self.assertEqual(bucket.isolation_group, isolation_group)
def test_existing_isolation_group_with_buckets_adds_next_bucket_range(
self):
"""
Common case: An isolation group with experiment bucket allocations exists,
and a subsequent bucket allocation is requested. This will be the common case
for any experiments that share an isolation group.
"""
experiment = NimbusExperimentFactory.create()
isolation_group = NimbusIsolationGroupFactory.create(
name=experiment.slug)
NimbusBucketRangeFactory.create(isolation_group=isolation_group,
start=0,
count=100)
bucket = NimbusIsolationGroup.request_isolation_group_buckets(
experiment.slug, experiment, 100)
self.assertEqual(bucket.start, 100)
self.assertEqual(bucket.end, 199)
self.assertEqual(bucket.count, 100)
self.assertEqual(bucket.isolation_group, isolation_group)