BigW Consortium Gitlab
Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
gitlab-ce
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Forest Godfrey
gitlab-ce
Commits
1de0261d
Unverified
Commit
1de0261d
authored
Dec 16, 2017
by
Matija Čupić
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Isolate CheckGcpProjectBillingWorker specreturns
parent
68b95cd0
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
4 deletions
+5
-4
check_gcp_project_billing_worker_spec.rb
spec/workers/check_gcp_project_billing_worker_spec.rb
+5
-4
No files found.
spec/workers/check_gcp_project_billing_worker_spec.rb
View file @
1de0261d
...
@@ -12,12 +12,13 @@ describe CheckGcpProjectBillingWorker do
...
@@ -12,12 +12,13 @@ describe CheckGcpProjectBillingWorker do
end
end
it
'stores billing status in redis'
do
it
'stores billing status in redis'
do
redis_double
=
double
expect
(
CheckGcpProjectBillingService
).
to
receive_message_chain
(
:new
,
:execute
).
and_return
(
true
)
expect
(
CheckGcpProjectBillingService
).
to
receive_message_chain
(
:new
,
:execute
).
and_return
(
true
)
subject
expect
(
Gitlab
::
Redis
::
SharedState
).
to
receive
(
:with
).
and_yield
(
redis_double
)
expect
(
redis_double
).
to
receive
(
:set
).
with
(
CheckGcpProjectBillingWorker
.
redis_shared_state_key_for
(
token
),
anything
)
Gitlab
::
Redis
::
SharedState
.
with
do
|
redis
|
subject
expect
(
redis
.
get
(
"gitlab:gcp:
#{
token
}
:billing_enabled"
)).
to
eq
(
'true'
)
end
end
end
end
end
end
end
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment