[CONFIG] new LOGL_LEVEL behavior added to README.md

Author: Gonzalo Diaz

README.md

@@ -91,40 +91,45 @@ Unit test has test cases and input data to solve the problem.
 
 Run all tests (skips static analysis, and "clean" test cache before running):
 
+By default, there are no log outputs from the application or tests to the console.
+"--verbosity \<LEVEL\>" only control verbosity of dotnet proccess
+(building, test running, ...)
+
 ```bash
-dotnet test --verbosity normal
+dotnet clean && dotnet test --verbosity normal
 ```
 
-Another way to increase verbosity level in console output:
+To enable console detailed output use:
 
 ```bash
 dotnet test --logger "console;verbosity=detailed"
 ```
 
 #### Test run with alternative behaviors
 
-> [!IMPORTANT]
-> LOG_LEVEL environment variable not yet implemented.
->
-> Currently tests only have one behavior.
-
 You can change test running behaviour using some environment variables as follows:
 
 | Variable | Values | Default |
 | ------ | ------ | ------ |
 | LOG_LEVEL  | `debug`, `warning`, `error`, `info` | `info` |
 | BRUTEFORCE | `true`, `false`| `false` |
 
-- ~~`LOG_LEVEL`: change verbosity level in outputs.~~
+- `LOG_LEVEL`: change verbosity level in outputs.
 - `BRUTEFORCE`: enable or disable running large tests.
 (long time, large amount of data, high memory consumition).
 
 #### Examples running tests with alternative behaviors
 
+Run tests with debug outputs:
+
+```bash
+LOG_LEVEL=debug dotnet test --logger "console;verbosity=detailed"
+```
+
 Run brute-force tests with debug outputs:
 
 ```bash
-BRUTEFORCE=true dotnet test --logger "console;verbosity=detailed"
+BRUTEFORCE=true LOG_LEVEL=debug dotnet test --logger "console;verbosity=detailed"
 ```
 
 ### Install and Run using make
@@ -138,16 +143,22 @@ Run tests (libraries are installed as dependency task in make):
 make test
 ```
 
-Run brute-force tests:
+Run tests with debug outputs:
+
+```bash
+make test -e LOG_LEVEL=debug
+```
+
+Run brute-force tests with debug outputs:
 
 ```bash
-make test -e BRUTEFORCE=true
+make test -e BRUTEFORCE=true -e LOG_LEVEL=debug
 ```
 
 Alternative way, use environment variables as prefix:
 
 ```bash
-BRUTEFORCE=true make test
+BRUTEFORCE=true LOG_LEVEL=debug make test
 ```
 
 ### Install and Running with Docker 🐳
@@ -174,7 +185,11 @@ BRUTEFORCE=true docker-compose --profile testing run --rm algorithm-exercises-cs
 Overriding docker CMD, as parameter of make "-e":
 
 ```bash
-docker-compose --profile testing run --rm algorithm-exercises-java-test make test -e BRUTEFORCE=true
+docker-compose --profile testing run --rm algorithm-exercises-csharp-test make test -e BRUTEFORCE=true
+```
+
+```bash
+docker-compose --profile testing run --rm algorithm-exercises-csharp-test make test -e LOG_LEVEL=DEBUG -e BRUTEFORCE=true
 ```
 
 ### Install and Running with Docker 🐳 using make
@@ -190,7 +205,7 @@ or overriding CMD and passing to make as "-e" argument.
 Passing environment variables using docker-compose (compose.yaml mechanism):
 
 ```bash
-BRUTEFORCE=true make compose/test
+BRUTEFORCE=true LOG_LEVEL=debug make compose/test
 ```
 
 ## Development workflow using Docker / docker-compose