Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests: RabbitMQ as a default BROKER_URL #41

Closed
wants to merge 1 commit into from

Conversation

nharraud
Copy link
Member

@nharraud nharraud commented Sep 7, 2016

Signed-off-by: Nicolas Harraudeau nicolas.harraudeau@cern.ch

@nharraud nharraud added this to the v1.0.0 milestone Sep 7, 2016
@@ -50,7 +50,7 @@ def app(request):
instance_path = tempfile.mkdtemp()
app = Flask('testapp', instance_path=instance_path)
app.config.update(
BROKER_URL=os.environ.get('BROKER_URL', 'memory://'),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you just change the default value so one can still test with different brokers?

@jirikuncar jirikuncar changed the title tests: test message queue fix tests: RabbitMQ as a default BROKER_URL Sep 7, 2016
@jirikuncar
Copy link
Member

@nharraud WDYT about new PR title as commit title?

@nharraud
Copy link
Member Author

nharraud commented Sep 7, 2016

I would just specify in the title that it is only for the tests.

@jirikuncar
Copy link
Member

it's clear from the component name ;)

@nharraud
Copy link
Member Author

nharraud commented Sep 7, 2016

@jirikuncar you're right. Fixing it.

* FIX Fixes tests by using rabbitmq instead of in memory queue.
  (closes inveniosoftware#40)

Signed-off-by: Nicolas Harraudeau <nicolas.harraudeau@cern.ch>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tests: conflict between CliRunner and Celery in memory broker
2 participants