-should have access to admin addons
  ✅ -should have access to admin addons
-should have access to admin strategies
  ✅ -should have access to admin strategies
-should have access to admin contexts
  ✅ -should have access to admin contexts
-should have access to create projects
  ✅ -should have access to create projects
-should have access to update applications
  ✅ -should have access to update applications
-should not have admin permission
  ✅ -should not have admin permission
-should have project admin to default project as editor
  ✅ -should have project admin to default project as editor
-should not have project admin to other projects as editor
  ✅ -should not have project admin to other projects as editor
-cannot add CREATE_FEATURE without defining project
  ✅ -cannot add CREATE_FEATURE without defining project
-cannot remove CREATE_FEATURE without defining project
  ✅ -cannot remove CREATE_FEATURE without defining project
-should remove CREATE_FEATURE on default environment
  ❌ -should remove CREATE_FEATURE on default environment
	Error: expect(received).toBe(expected) // Object.is equality
-admin should be admin
  ✅ -admin should be admin
-should create default roles to project
  ✅ -should create default roles to project
-should require name when create default roles to project
  ✅ -should require name when create default roles to project
-should grant user access to project
  ✅ -should grant user access to project
-should not get access if not specifying project
  ✅ -should not get access if not specifying project
-should remove user from role
  ✅ -should remove user from role
-should return role with users
  ✅ -should return role with users
-should return role with permissions and users
  ✅ -should return role with permissions and users
-should set root role for user
  ✅ -should set root role for user
-should switch root role for user
  ✅ -should switch root role for user
-should switch project roles on when multiple roles are present for same user
  ✅ -should switch project roles on when multiple roles are present for same user
-should not crash if user does not have permission
  ✅ -should not crash if user does not have permission
-should support permission with "ALL" environment requirement
  ✅ -should support permission with "ALL" environment requirement
-Should have access to create a strategy in an environment
  ✅ -Should have access to create a strategy in an environment
-Should be denied access to create a strategy in an environment the user does not have access to
  ✅ -Should be denied access to create a strategy in an environment the user does not have access to
-Should have access to edit a strategy in an environment
  ✅ -Should have access to edit a strategy in an environment
-Should have access to delete a strategy in an environment
  ✅ -Should have access to delete a strategy in an environment
-Should be denied access to delete a strategy in an environment the user does not have access to
  ✅ -Should be denied access to delete a strategy in an environment the user does not have access to
-Should be denied access to delete a role that is in use
  ✅ -Should be denied access to delete a role that is in use
-Should be denied move feature toggle to project where the user does not have access
  ✅ -Should be denied move feature toggle to project where the user does not have access
-Should be allowed move feature toggle to project when the user has access
  ✅ -Should be allowed move feature toggle to project when the user has access
-Should not be allowed to edit a root role
  ✅ -Should not be allowed to edit a root role
-Should not be allowed to delete a root role
  ✅ -Should not be allowed to delete a root role
-Should not be allowed to edit a project role
  ✅ -Should not be allowed to edit a project role
-Should not be allowed to delete a project role
  ✅ -Should not be allowed to delete a project role
-Should be allowed move feature toggle to project when given access through group
  ✅ -Should be allowed move feature toggle to project when given access through group
-Should not lose user role access when given permissions from a group
  ✅ -Should not lose user role access when given permissions from a group
-Should allow user to take multiple group roles and have expected permissions on each project
  ✅ -Should allow user to take multiple group roles and have expected permissions on each project
-Should allow user to take on root role through a group that has a root role defined
  ✅ -Should allow user to take on root role through a group that has a root role defined
-Should not elevate permissions for a user that is not present in a root role group
  ✅ -Should not elevate permissions for a user that is not present in a root role group
-Should not reduce permissions for an admin user that enters an editor group
  ✅ -Should not reduce permissions for an admin user that enters an editor group
-Should not change permissions for a user in a group without a root role
  ✅ -Should not change permissions for a user in a group without a root role
-Should add permissions to user when a group is given a root role after the user has been added to the group
  ✅ -Should add permissions to user when a group is given a root role after the user has been added to the group
-Should give full project access to the default project to user in a group with an editor root role
  ✅ -Should give full project access to the default project to user in a group with an editor root role
-if user has two roles user has union of permissions from the two roles
  ✅ -if user has two roles user has union of permissions from the two roles
-calling set for user overwrites existing roles
  ✅ -calling set for user overwrites existing roles
-if group has two roles user has union of permissions from the two roles
  ✅ -if group has two roles user has union of permissions from the two roles
-calling set for group overwrites existing roles
  ✅ -calling set for group overwrites existing roles
-group with root role can be assigned a project specific role
  ✅ -group with root role can be assigned a project specific role
-calling add access with invalid project role ids should not assign those roles
  ✅ -calling add access with invalid project role ids should not assign those roles
-calling set roles for user with invalid project role ids should not assign those roles
  ✅ -calling set roles for user with invalid project role ids should not assign those roles
-calling set roles for user with empty role array removes all roles
  ✅ -calling set roles for user with empty role array removes all roles
-calling set roles for user with empty role array should not remove root roles
  ✅ -calling set roles for user with empty role array should not remove root roles
-remove user access should remove all project roles
  ✅ -remove user access should remove all project roles
-remove user access should remove all project roles, while leaving root roles untouched
  ✅ -remove user access should remove all project roles, while leaving root roles untouched
-calling set roles for group with invalid project role ids should not assign those roles
  ✅ -calling set roles for group with invalid project role ids should not assign those roles
-calling set roles for group with empty role array removes all roles
  ✅ -calling set roles for group with empty role array removes all roles
-calling set roles for group with empty role array should not remove root roles
  ✅ -calling set roles for group with empty role array should not remove root roles
-remove group access should remove all project roles
  ✅ -remove group access should remove all project roles
-remove group access should remove all project roles, while leaving root roles untouched
  ✅ -remove group access should remove all project roles, while leaving root roles untouched