Skip to content

Commit f881aeb

Browse files
Create RUNNING_TESTS.md
1 parent 620825c commit f881aeb

File tree

1 file changed

+12
-4
lines changed

1 file changed

+12
-4
lines changed

RUNNING_TESTS.md

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -30,17 +30,25 @@ This will complete the code AMQP 0-9-1 protocol code generation and build all pr
3030
Tests can be run from Visual Studio using [NUnit Test Adapter](https://visualstudiogallery.msdn.microsoft.com/6ab922d0-21c0-4f06-ab5f-4ecd1fe7175d).
3131
Note that it may take some time for the adapter to discover tests in the assemblies.
3232

33-
Running the tests from the command line is also straightforward you don't need to build first to do this: use
33+
The test suite assumes there's a RabbitMQ node [built from source](http://www.rabbitmq.com/build-server.html) running locally
34+
with all defaults. Team RabbitMQ uses [rabbitmq-public-umbrella](https://github.com/rabbitmq/rabbitmq-public-umbrella) to
35+
do that:
3436

35-
On Windows run:
37+
git clone https://github.com/rabbitmq/rabbitmq-public-umbrella umbrella
38+
cd umbrella
39+
make co
40+
cd deps/rabbit
41+
make
42+
make run-broker
43+
44+
Then, to run the tests on Windows use:
3645

3746
run-test.bat
3847

39-
On osx/linux run:
48+
On MacOS, Linux, BSD use:
4049

4150
run-test.sh
4251

43-
4452
Running individual tests and fixtures on Windows is trivial using the Visual Studio test runner.
4553
To run a specific tests fixture on osx/linux you can use nunit3 where expressions to select the tests
4654
to be run:

0 commit comments

Comments
 (0)