summaryrefslogtreecommitdiff
path: root/spec/support/services
Commit message (Collapse)AuthorAgeFilesLines
* Upgrade Rails to 5.1.6.1Jasper Maes2019-04-231-2/+2
| | | | Model.new.attributes now also returns encrypted attributes.
* Passing the separator argument as a positional parameter is deprecatedJasper Maes2018-12-141-1/+1
|
* Revert "Merge branch 'refactor-cluster-create-service-spec' into 'master'"Thong Kuah2018-10-221-0/+59
| | | This reverts merge request !22407
* Move shared examples into the only file where usedrefactor-cluster-create-service-specThong Kuah2018-10-171-59/+0
| | | | | This will make it easier to perform in place adjustments, etc for future MRs involving group clusters.
* Remove `rbac_clusters` feature flagThong Kuah2018-10-041-4/+0
| | | | | | | | | | | | | | | Now that Auto DevOps can run in a RBAC enabled cluster from https://gitlab.com/gitlab-org/gitlab-ce/issues/51942, we can now remove the FF. As the flag only governed if UI elements would appear or not when creating/adding existing clusters; the effect of removing the FF would be that the checkbox to choose to enable RBAC clusters will now always appear. Remove FF stubs from specs Improve spec context names
* Address BE review - re-arrange some specsThong Kuah2018-09-141-1/+2
|
* Add FE option for users to choose to create a fully RBAC-enabled cluster or not.Thong Kuah2018-09-141-11/+2
| | | | This is similar to the option in the Add Existing cluster form
* Create a GKE cluster with legacy_abac disabled when the `:rbac_clusters` ↵Thong Kuah2018-09-141-1/+15
| | | | | | feature flag is enabled Explicitly persist the legacy_abac value of the cluster_provider_gcp so that we can disable abac if the `:rbac_clusters` feature flag is enabled
* Resolve "Rename the `Master` role to `Maintainer`" BackendMark Chao2018-07-111-2/+2
|
* Extract shared components from Clusters::CreateService specMatija Čupić2018-05-131-0/+57
|
* Cleanly handle plural name for ghost user migrationOlivier Gonzalez2018-05-071-1/+1
|
* Replace '.team << [user, role]' with 'add_role(user)' in specs36782-replace-team-user-role-with-add_role-user-in-specsblackst0ne2017-12-221-2/+2
|
* Change all `:empty_project` to `:project`rs-empty_project-defaultRobert Speicher2017-08-021-1/+1
|
* Ensure all project factories use `:repository` trait or `:empty_project`rs-empty_project-cleanupRobert Speicher2017-08-011-1/+8
|
* Use Ghost user when edited_by, merged_by deleted34930-fix-edited-byJarka Kadlecova2017-07-191-11/+10
|
* Rename "Slash commands" to "Quick actions"Eric Eastwood2017-06-151-1/+1
| | | | | | | | | | | | | Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/27070 Deprecate "chat commands" in favor of "slash commands" We looked for things like: - `slash commmand` - `slash_command` - `slash-command` - `SlashCommand`
* Correct RSpec/SingleLineHook cop offensesRobert Speicher2017-06-142-2/+6
|
* Backport of multiple_assignees_feature [ci skip]Valery Sizov2017-05-043-117/+1
|
* Move records to the ghost user in a transaction.Timothy Andrew2017-04-241-0/+52
| | | | | | | | | | | | | | | | - While deleting a user, some of the user's associated records are moved to the ghost user so they aren't deleted. The user is blocked before these records are moved, to prevent the user from creating new records while the migration is happening, and so preventing a data race. - Previously, if the migration failed, the user would _remain_ blocked, which is not the expected behavior. On the other hand, we can't just stick the block + migration into a transaction, because we want the block to be committed before the migration starts (for the data race reason mentioned above). - One solution (implemented in this commit) is to block the user in a parent transaction, migrate the associated records in a nested sub-transaction, and then unblock the user in the parent transaction if the sub-transaction fails.
* Implement review comments from @DouweM for !10467.28695-move-all-associated-records-to-ghost-userTimothy Andrew2017-04-061-24/+4
| | | | | | | | | | 1. Have `MigrateToGhostUser` be a service rather than a mixed-in module, to keep things explicit. Specs testing the behavior of this class are moved into a separate service spec file. 2. Add a `user.reported_abuse_reports` association to make the `migrate_abuse_reports` method more consistent with the other `migrate_` methods.
* Move a user's award emoji to the ghost userTimothy Andrew2017-04-061-1/+5
| | | | | | | | | | | | | | | | ... when the user is destroyed. 1. Normally, for a given awardable and award emoji name, a user is only allowed to create a single award emoji. 2. This validation needs to be removed for ghost users, since: - User A and User B have created award emoji - with the same name and against the same awardable - User A is deleted. Their award emoji is moved to the ghost user - User B is deleted. Their award emoji needs to be moved to the ghost user. However, this breaks the uniqueness validation, since the ghost user is only allowed to have one award emoji of a given name for a given awardable
* Move a user's notes to the ghost userTimothy Andrew2017-04-061-12/+14
| | | | ... when the user is destroyed.
* Move a user's merge requests to the ghost user.Timothy Andrew2017-04-061-0/+53
| | | | | | | 1. When the user is deleted. 2. Refactor out code relating to "migrating records to the ghost user" into a `MigrateToGhostUser` concern, which is tested using a shared example.
* Don't use FFaker in factories, use sequences insteadRémy Coutable2017-04-031-1/+1
| | | | | | | FFaker can generate data that randomly break our test suite. This simplifies our factories and use sequences which are more predictive. Signed-off-by: Rémy Coutable <remy@rymai.me>
* Use `:empty_project` where possible in service specsRobert Speicher2017-03-271-1/+1
|
* Enable Style/SpaceInsideBracketsDouwe Maan2017-02-231-1/+1
|
* fix issue creation from milestone doesn't assign the milestonewendy04022017-02-121-1/+1
|
* Add traits for ProjectFeatures to Project factorySemyon Pupkov2017-02-051-2/+2
| | | | https://gitlab.com/gitlab-org/gitlab-ce/issues/24007
* Check if user can read issue before being assignedissue_22664Felipe Artur2016-12-273-1/+107
|
* Ensure issuable state changes only fire webhooks onceMark Fletcher2016-12-161-0/+17
| | | | | * Webhooks for close and reopen events now fired in respective services only * Prevents generic 'update' webhooks firing too
* Fix permission for setting an issue's due dateRémy Coutable2016-09-281-0/+83
Signed-off-by: Rémy Coutable <remy@rymai.me>
View Lorry Controller Status