Readme changes

Author: dnozay

README.md

@@ -60,6 +60,21 @@ Or you can manually download the latest released version from
 [PyPI](https://pypi.python.org/pypi/unittest-xml-reporting/).
 
 
+## Command-line
+
+````bash
+python -m xmlrunner [options]
+python -m xmlrunner discover [options]
+
+# help
+python -m xmlrunner -h
+````
+
+e.g. 
+````bash
+python -m xmlrunner discover -t ~/mycode/tests -o /tmp/build/junit-reports
+````
+
 ## Usage
 
 The script below, adapted from the
@@ -157,32 +172,12 @@ TEST_RUNNER = 'xmlrunner.extra.djangotestrunner.XMLTestRunner'
 
 Also, the following settings are provided so you can fine tune the reports:
 
-**TEST_OUTPUT_VERBOSE** (Default: `1`, choose between `0`,`1`, and `2`)
-
-Besides the XML reports generated by the test runner, a bunch of useful
-information is printed to the `sys.stderr` stream, just like the
-`TextTestRunner` does. Use this setting to choose between a verbose and a
-non-verbose output.
-
-**TEST_OUTPUT_DESCRIPTIONS** (Default: `False`)
-
-If your test methods contains docstrings, you can display such docstrings
-instead of display the test name (ex: `module.TestCase.test_method`). In
-order to use this feature, you have to enable verbose output by setting
-`TEST_OUTPUT_VERBOSE = 2`.
-
-**TEST_OUTPUT_DIR** (Default: `"."`)
-
-Tells the test runner where to put the XML reports. If the directory
-couldn't be found, the test runner will try to create it before
-generate the XML files.
-
-**TEST_OUTPUT_FILE_NAME** (Default: `None`)
-
-Tells the test runner to output a single XML report with this filename
-under `os.path.join(TEST_OUTPUT_DIR, TEST_OUTPUT_FILE_NAME)`. Please note
-that for long running tests, this will keep the results in memory for
-a longer time than multiple reports, and may use up more resources.
+|setting|default|values|description|
+|-|-|-|-|
+|`TEST_OUTPUT_VERBOSE`|`1`|`0|1|2`|Besides the XML reports generated by the test runner, a bunch of useful information is printed to the `sys.stderr` stream, just like the `TextTestRunner` does. Use this setting to choose between a verbose and a non-verbose output.|
+|`TEST_OUTPUT_DESCRIPTIONS`|`False`|`True|False`|If your test methods contains docstrings, you can display such docstrings instead of display the test name (ex: `module.TestCase.test_method`).<br>In order to use this feature, you have to enable verbose output by setting `TEST_OUTPUT_VERBOSE = 2`.<br>Only effects stdout and not XML output.|
+|`TEST_OUTPUT_DIR`|`"."`|`<str>`|Tells the test runner where to put the XML reports. If the directory couldn't be found, the test runner will try to create it before generate the XML files.|
+|`TEST_OUTPUT_FILE_NAME`|`None`|`<str>`|Tells the test runner to output a single XML report with this filename under `os.path.join(TEST_OUTPUT_DIR, TEST_OUTPUT_FILE_NAME)`.<br>Please note that for long running tests, this will keep the results in memory for a longer time than multiple reports, and may use up more resources.|
 
 
 ## Contributing