Guidelines how to test applications that use this library

[jage]

For example, currently you need to set AMQP_USERNAME, AMQP_PASSWORD, RABBITMQ_N_HOST for tests since the RUBY_ENV isn't "development".

This could be changed easily in:

twingly-amqp/lib/twingly/amqp/connection.rb

Lines 15 to 29 in 4e96a64

	def create_connection
	if ruby_env == "development"
	connection = Bunny.new
	else
	connection_options = {
	hosts: amqp_hosts,
	user: ENV.fetch("AMQP_USERNAME"),
	pass: ENV.fetch("AMQP_PASSWORD"),
	recover_from_connection_close: true,
	}
	connection = Bunny.new(connection_options)
	end
	connection.start
	connection
	end

Another idea is that we should look at both RUBY_ENV and RACK_ENV to figure out if we're in production or not.

An alternative solution might be that we expose some other API for tests (fake connection?).

[jage]

RABBITMQ_N_HOST can be avoided by giving hosts when initializing the connection.

[roback]

AMQP_USERNAME and AMQP_PASSWORD can now also be set when initializing the connection instead of using environment variables (since #26).

[dentarg]

Just a note that #36 removed usage of RUBY_ENV.

[walro]

I think that #26 and #36 made this easy enough to test. There are some other issues related to testing that will make this glorious, e.g. #29, #39, #40, #45 and possibly more to come.