Minor change to integration-tests README formatting

This commit is contained in:
Charles Allen 2015-07-14 17:01:06 -07:00
parent 798c3320d0
commit 80a18243dd
1 changed files with 6 additions and 6 deletions

View File

@ -34,14 +34,14 @@ Running Integration tests
## Running tests using mvn ## Running tests using mvn
To run all the tests using mvn run the following command - To run all the tests using mvn run the following command -
''''' ```
mvn verify -P integration-tests mvn verify -P integration-tests
''''' ```
To run only a single test using mvn run following command - To run only a single test using mvn run following command -
''''' ```
mvn verify -P integration-tests -Dit.test=<test_name> mvn verify -P integration-tests -Dit.test=<test_name>
''''' ```
Writing a New Test Writing a New Test
@ -66,9 +66,9 @@ A test can access different helper and utility classes provided by test-framewor
To mark a test be able to use Guice Dependency Injection - To mark a test be able to use Guice Dependency Injection -
Annotate the test class with the below annotation Annotate the test class with the below annotation
''''''' ```
@Guice(moduleFactory = DruidTestModuleFactory.class) @Guice(moduleFactory = DruidTestModuleFactory.class)
''''''' ```
This will tell the test framework that the test class needs to be constructed using guice. This will tell the test framework that the test class needs to be constructed using guice.
### Helper Classes provided ### Helper Classes provided