-should add and delete feature dependencies
  ❌ -should add and delete feature dependencies
	Error: expected 200 "OK", got 403 "Forbidden"
-should not allow to add a parent dependency to a feature that already has children
  ❌ -should not allow to add a parent dependency to a feature that already has children
	Error: expected 200 "OK", got 403 "Forbidden"
-should not allow to add non-existent parent dependency
  ✅ -should not allow to add non-existent parent dependency
-should not allow to add archived parent dependency
  ✅ -should not allow to add archived parent dependency
-should check if any dependencies exist
  ❌ -should check if any dependencies exist
	Error: expected 200 "OK", got 403 "Forbidden"
-should not allow to add dependency to self
  ✅ -should not allow to add dependency to self
-should not allow to add dependency to feature from another project
  ✅ -should not allow to add dependency to feature from another project

import-export for project-specific segments-exports features with project-specific-segments
  ✅ import-export for project-specific segments-exports features with project-specific-segments
-exports features
  ❌ -exports features
	Error: expected 200 "OK", got 403 "Forbidden"
-exports features by tag
  ✅ -exports features by tag
-should export custom context fields from strategies and variants
  ✅ -should export custom context fields from strategies and variants
-should export tags
  ✅ -should export tags
-returns no features, when no feature was requested
  ✅ -returns no features, when no feature was requested
-import features to existing project and environment
  ❌ -import features to existing project and environment
	Error: expected 200 "OK", got 403 "Forbidden"
-import multiple features with same tag
  ✅ -import multiple features with same tag
-import too many feature exceeding limit
  ✅ -import too many feature exceeding limit
-can update toggles on subsequent import
  ✅ -can update toggles on subsequent import
-reject import with unknown context fields
  ✅ -reject import with unknown context fields
-reject import with unsupported strategies
  ✅ -reject import with unsupported strategies
-reject import with duplicate features
  ✅ -reject import with duplicate features
-validate import data
  ✅ -validate import data
-should create new context
  ✅ -should create new context
-should not import archived features tags
  ✅ -should not import archived features tags
-should give errors with flag names if the flags don't match the project pattern
  ✅ -should give errors with flag names if the flags don't match the project pattern

-Trying to add a strategy configuration to environment not connected to toggle should fail
  ✅ -Trying to add a strategy configuration to environment not connected to toggle should fail
-Can get project overview
  ✅ -Can get project overview
-should list dependencies and children
  ❌ -should list dependencies and children
	Error: expected 200 "OK", got 403 "Forbidden"
-should not allow to change project with dependencies
  ❌ -should not allow to change project with dependencies
	Error: expected 200 "OK", got 403 "Forbidden"
-Should not allow to archive/delete feature with children
  ❌ -Should not allow to archive/delete feature with children
	Error: expected 200 "OK", got 403 "Forbidden"
-Should allow to archive/delete feature with children if no orphans are left
  ❌ -Should allow to archive/delete feature with children if no orphans are left
	Error: expected 200 "OK", got 403 "Forbidden"
-Should not allow to archive/delete feature when orphans are left
  ❌ -Should not allow to archive/delete feature when orphans are left
	Error: expected 200 "OK", got 403 "Forbidden"
-should clone feature with parent dependencies
  ❌ -should clone feature with parent dependencies
	Error: expected 200 "OK", got 403 "Forbidden"
-Can get features for project
  ✅ -Can get features for project
-Project overview includes environment connected to feature
  ✅ -Project overview includes environment connected to feature
-Disconnecting environment from project, removes environment from features in project overview
  ✅ -Disconnecting environment from project, removes environment from features in project overview
-Can enable/disable environment for feature with strategies
  ✅ -Can enable/disable environment for feature with strategies
-Can bulk enable/disable environment for feature with strategies
  ✅ -Can bulk enable/disable environment for feature with strategies
-Trying to get a project that doesn't exist yields 404
  ✅ -Trying to get a project that doesn't exist yields 404
-Trying to get features for non-existing project also yields 404
  ✅ -Trying to get features for non-existing project also yields 404
-Can use new project feature toggle endpoint to create feature toggle without strategies
  ✅ -Can use new project feature toggle endpoint to create feature toggle without strategies
-Can create feature toggle without strategies
  ✅ -Can create feature toggle without strategies
-Still validates feature toggle input when creating
  ✅ -Still validates feature toggle input when creating
-Trying to create toggle that already exists yield 409 error
  ✅ -Trying to create toggle that already exists yield 409 error
-Trying to create toggle under project that does not exist should fail
  ✅ -Trying to create toggle under project that does not exist should fail
-Can get environment info for feature toggle
  ✅ -Can get environment info for feature toggle
-Getting environment info for environment that does not exist yields 404
  ✅ -Getting environment info for environment that does not exist yields 404
-Trying to toggle environment that does not exist yields 404
  ✅ -Trying to toggle environment that does not exist yields 404
-Getting feature that does not exist should yield 404
  ✅ -Getting feature that does not exist should yield 404
Interacting with features using project IDs that belong to other projects-Getting a feature yields 404 if the provided project id doesn't match the feature's project
  ✅ Interacting with features using project IDs that belong to other projects-Getting a feature yields 404 if the provided project id doesn't match the feature's project
Interacting with features using project IDs that belong to other projects-Getting a feature yields 404 if the provided project doesn't exist
  ✅ Interacting with features using project IDs that belong to other projects-Getting a feature yields 404 if the provided project doesn't exist
Interacting with features using project IDs that belong to other projects-Archiving a feature yields 404 if the provided project id doesn't match the feature's project
  ✅ Interacting with features using project IDs that belong to other projects-Archiving a feature yields 404 if the provided project id doesn't match the feature's project
Interacting with features using project IDs that belong to other projects-Archiving a feature yields 404 if the provided project doesn't exist
  ✅ Interacting with features using project IDs that belong to other projects-Archiving a feature yields 404 if the provided project doesn't exist
Interacting with features using project IDs that belong to other projects-Trying to archive a feature that doesn't exist should yield a 404, regardless of whether the project exists or not.
  ✅ Interacting with features using project IDs that belong to other projects-Trying to archive a feature that doesn't exist should yield a 404, regardless of whether the project exists or not.
-Should update feature toggle
  ✅ -Should update feature toggle
-Should not change name of feature toggle
  ✅ -Should not change name of feature toggle
-Should not change project of feature toggle even if it is part of body
  ✅ -Should not change project of feature toggle even if it is part of body
-Should patch feature toggle
  ✅ -Should patch feature toggle
-Should patch feature toggle and not remove variants
  ✅ -Should patch feature toggle and not remove variants
-Patching feature toggles to stale should trigger FEATURE_STALE_ON event
  ✅ -Patching feature toggles to stale should trigger FEATURE_STALE_ON event
-Trying to patch variants on a feature toggle should trigger an OperationDeniedError
  ✅ -Trying to patch variants on a feature toggle should trigger an OperationDeniedError
-Patching feature toggles to active (turning stale to false) should trigger FEATURE_STALE_OFF event
  ✅ -Patching feature toggles to active (turning stale to false) should trigger FEATURE_STALE_OFF event
-Should archive feature toggle
  ✅ -Should archive feature toggle
-Can add strategy to feature toggle to a "some-env-2"
  ✅ -Can add strategy to feature toggle to a "some-env-2"
-Can update strategy on feature toggle
  ✅ -Can update strategy on feature toggle
-should coerce all strategy parameter values to strings
  ✅ -should coerce all strategy parameter values to strings
-should NOT limit the length of parameter values
  ✅ -should NOT limit the length of parameter values
-Can NOT delete strategy with wrong projectId
  ✅ -Can NOT delete strategy with wrong projectId
-add strategy cannot use wrong projectId
  ✅ -add strategy cannot use wrong projectId
-update strategy on feature toggle cannot use wrong projectId
  ✅ -update strategy on feature toggle cannot use wrong projectId
-Environments are returned in sortOrder
  ✅ -Environments are returned in sortOrder
-Can get strategies for feature and environment
  ✅ -Can get strategies for feature and environment
-Getting strategies for environment that does not exist yields 404
  ✅ -Getting strategies for environment that does not exist yields 404
-Can update a strategy based on id
  ✅ -Can update a strategy based on id
-Trying to update a non existing feature strategy should yield 404
  ✅ -Trying to update a non existing feature strategy should yield 404
-Can patch a strategy based on id
  ✅ -Can patch a strategy based on id
-Trying to get a non existing feature strategy should yield 404
  ✅ -Trying to get a non existing feature strategy should yield 404
-Can enable environment for feature without strategies
  ✅ -Can enable environment for feature without strategies
-Deleting a strategy should include name of feature strategy was deleted from
  ✅ -Deleting a strategy should include name of feature strategy was deleted from
-Enabling environment creates a FEATURE_ENVIRONMENT_ENABLED event
  ✅ -Enabling environment creates a FEATURE_ENVIRONMENT_ENABLED event
-Disabling environment creates a FEATURE_ENVIRONMENT_DISABLED event
  ✅ -Disabling environment creates a FEATURE_ENVIRONMENT_DISABLED event
-Can delete strategy from feature toggle
  ✅ -Can delete strategy from feature toggle
-List of strategies should respect sortOrder
  ✅ -List of strategies should respect sortOrder
-Feature strategies list should respect strategy sortorders for each environment
  ✅ -Feature strategies list should respect strategy sortorders for each environment
-Deleting last strategy for feature environment should disable that environment
  ✅ -Deleting last strategy for feature environment should disable that environment
-Deleting strategy for feature environment should not disable that environment as long as there are other strategies
  ✅ -Deleting strategy for feature environment should not disable that environment as long as there are other strategies
-should clone feature toggle without strategies
  ✅ -should clone feature toggle without strategies
-should clone feature toggle WITH strategies
  ✅ -should clone feature toggle WITH strategies
-should clone feature toggle WITH variants
  ✅ -should clone feature toggle WITH variants
-should clone feature toggle without replacing groupId
  ✅ -should clone feature toggle without replacing groupId
-Should not allow changing project to target project without the same enabled environments
  ✅ -Should not allow changing project to target project without the same enabled environments
-Should allow changing project to target project with the same enabled environments
  ✅ -Should allow changing project to target project with the same enabled environments
-a feature's variants should be sorted by name in increasing order
  ✅ -a feature's variants should be sorted by name in increasing order
-should validate context when calling update with PUT
  ✅ -should validate context when calling update with PUT
-should validate context when calling update with PATCH
  ✅ -should validate context when calling update with PATCH
-should not update project with PUT
  ✅ -should not update project with PUT
-should not update project with PATCH
  ✅ -should not update project with PATCH
-Can create a feature with impression data
  ✅ -Can create a feature with impression data
-Can create a feature without impression data
  ✅ -Can create a feature without impression data
-Can update impression data with PUT
  ✅ -Can update impression data with PUT
-Can create toggle with impression data on different project
  ✅ -Can create toggle with impression data on different project
-should handle strategy variants
  ✅ -should handle strategy variants
-should reject invalid constraint values for multi-valued constraints
  ✅ -should reject invalid constraint values for multi-valued constraints
-should add default constraint values for single-valued constraints
  ✅ -should add default constraint values for single-valued constraints
-should allow long parameter values
  ✅ -should allow long parameter values
-should change strategy sort order when payload is valid
  ✅ -should change strategy sort order when payload is valid
-should reject set sort order request when payload is invalid
  ✅ -should reject set sort order request when payload is invalid
-should return strategies in correct order when new strategies are added
  ✅ -should return strategies in correct order when new strategies are added
-should create a strategy with segments
  ✅ -should create a strategy with segments
-should add multiple segments to a strategy
  ✅ -should add multiple segments to a strategy
-Can filter based on tags
  ✅ -Can filter based on tags
-Can query for features with namePrefix
  ✅ -Can query for features with namePrefix
-Can query for features with namePrefix and tags
  ✅ -Can query for features with namePrefix and tags
-Can query for two tags at the same time. Tags are ORed together
  ✅ -Can query for two tags at the same time. Tags are ORed together
-Should batch stale features
  ✅ -Should batch stale features
-should return disabled strategies
  ✅ -should return disabled strategies
-should disable strategies in place
  ✅ -should disable strategies in place
-Disabling last strategy for feature environment should disable that environment
  ✅ -Disabling last strategy for feature environment should disable that environment
-Enabling a feature environment should add the default strategy when only disabled strategies
  ✅ -Enabling a feature environment should add the default strategy when only disabled strategies
-Updating feature strategy sort-order should return strategies in correct order
  ✅ -Updating feature strategy sort-order should return strategies in correct order
-Updating feature strategy sort-order should trigger a an event
  ✅ -Updating feature strategy sort-order should trigger a an event
-should not be allowed to create with invalid strategy type name
  ✅ -should not be allowed to create with invalid strategy type name
-should not be allowed to update with invalid strategy type name
  ✅ -should not be allowed to update with invalid strategy type name
-should return correct data structure for /api/admin/features
  ✅ -should return correct data structure for /api/admin/features

-advanced playground evaluation with no toggles
  ✅ -advanced playground evaluation with no toggles
-advanced playground evaluation with parent dependency
  ❌ -advanced playground evaluation with parent dependency
	Error: expected 200 "OK", got 403 "Forbidden"
-advanced playground evaluation happy path
  ✅ -advanced playground evaluation happy path
-show matching variant from variants selection only for enabled toggles
  ✅ -show matching variant from variants selection only for enabled toggles
-should return disabled strategies with unevaluated result
  ✅ -should return disabled strategies with unevaluated result

-returns three archived toggles
  ✅ -returns three archived toggles
-returns three archived toggles with archivedAt
  ✅ -returns three archived toggles with archivedAt
-revives a feature by name
  ✅ -revives a feature by name
-archived feature is not accessible via /features/:featureName
  ✅ -archived feature is not accessible via /features/:featureName
-must set name when reviving toggle
  ✅ -must set name when reviving toggle
-should be allowed to reuse deleted toggle name
  ✅ -should be allowed to reuse deleted toggle name
-Deleting an unarchived toggle should not take effect
  ✅ -Deleting an unarchived toggle should not take effect
-can bulk delete features and recreate after
  ✅ -can bulk delete features and recreate after
-can bulk revive features
  ✅ -can bulk revive features
-Should be able to bulk archive features
  ✅ -Should be able to bulk archive features
-Should validate if a list of features with dependencies can be archived
  ❌ -Should validate if a list of features with dependencies can be archived
	Error: expected 200 "OK", got 403 "Forbidden"

-returns four feature toggles
  ❌ -returns four feature toggles
	InvalidOperationError: Parent and child features should be in the same project
-returns dependencies
  ❌ -returns dependencies
	InvalidOperationError: Parent and child features should be in the same project
-returns four feature toggles without createdAt
  ❌ -returns four feature toggles without createdAt
	InvalidOperationError: Parent and child features should be in the same project
-gets a feature by name
  ❌ -gets a feature by name
	InvalidOperationError: Parent and child features should be in the same project
-returns a feature toggles impression data
  ❌ -returns a feature toggles impression data
	InvalidOperationError: Parent and child features should be in the same project
-returns a false for impression data when not specified
  ❌ -returns a false for impression data when not specified
	InvalidOperationError: Parent and child features should be in the same project
-cant get feature that does not exist
  ❌ -cant get feature that does not exist
	InvalidOperationError: Parent and child features should be in the same project
-Can filter features by namePrefix
  ❌ -Can filter features by namePrefix
	InvalidOperationError: Parent and child features should be in the same project
-Can get strategies for specific environment
  ❌ -Can get strategies for specific environment
	InvalidOperationError: Parent and child features should be in the same project
-Can use multiple filters
  ❌ -Can use multiple filters
	InvalidOperationError: Parent and child features should be in the same project
-returns a feature toggles impression data for a different project
  ❌ -returns a feature toggles impression data for a different project
	InvalidOperationError: Parent and child features should be in the same project