[CONFIG] new BRUTEFORCE behavior added to README.md

Author: Gonzalo Diaz

README.md

@@ -82,7 +82,7 @@ require docker-compose and make installed.
 Using a dotnet 8.0 stack in your SO. You must install dependencies:
 
 ```bash
-dotnet restore --verbosity=normal
+dotnet restore --verbosity normal
 ```
 
 Every problem is a function with unit test.
@@ -95,30 +95,37 @@ Run all tests (skips static analysis, and "clean" test cache before running):
 dotnet test --verbosity normal
 ```
 
+Another way to increase verbosity level in console output:
+
+```bash
+dotnet test --logger "console;verbosity=detailed"
+```
+
 #### Test run with alternative behaviors
 
 > [!IMPORTANT]
-> BRUTEFORCE and LOG_LEVEL environment variables not yet implemented.
+> 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:~~
+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.~~
-- ~~`BRUTEFORCE`: enable or disable running large tests.
-(long time, large amount of data, high memory consumition).~~
+- `BRUTEFORCE`: enable or disable running large tests.
+(long time, large amount of data, high memory consumition).
 
 #### Examples running tests with alternative behaviors
 
-> [!IMPORTANT]
-> BRUTEFORCE and LOG_LEVEL environment variables not yet implemented.
->
-> Currently tests only have one behavior.
+Run brute-force tests with debug outputs:
+
+```bash
+BRUTEFORCE=true dotnet test --logger "console;verbosity=detailed"
+```
 
 ### Install and Run using make
 
@@ -131,6 +138,18 @@ Run tests (libraries are installed as dependency task in make):
 make test
 ```
 
+Run brute-force tests:
+
+```bash
+make test -e BRUTEFORCE=true
+```
+
+Alternative way, use environment variables as prefix:
+
+```bash
+BRUTEFORCE=true make test
+```
+
 ### Install and Running with Docker 🐳
 
 Build an image of the test stage.
@@ -143,13 +162,37 @@ environment using docker-compose.
 docker-compose --profile testing run --rm algorithm-exercises-csharp-test
 ```
 
+To change behavior using environment variables, you can pass to containers
+in the following ways:
+
+From host using docker-compose (compose.yaml) mechanism:
+
+```bash
+BRUTEFORCE=true docker-compose --profile testing run --rm algorithm-exercises-csharp-test
+```
+
+Overriding docker CMD, as parameter of make "-e":
+
+```bash
+docker-compose --profile testing run --rm algorithm-exercises-java-test make test -e BRUTEFORCE=true
+```
+
 ### Install and Running with Docker 🐳 using make
 
 ```bash
 make compose/build
 make compose/test
 ```
 
+To pass environment variables you can use docker-compose
+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
+```
+
 ## Development workflow using Docker / docker-compose
 
 Running container with development target.
@@ -166,6 +209,16 @@ docker-compose build --compress algorithm-exercises-csharp-dev
 docker-compose run --rm algorithm-exercises-csharp-dev dotnet test --verbosity normal
 ```
 
+Or with detailed output to terminal:
+
+```bash
+# Build development target image
+docker-compose build --compress algorithm-exercises-csharp-dev
+
+# Run ephemeral container and override command to run test
+docker-compose run --rm algorithm-exercises-csharp-dev dotnet test --logger "console;verbosity=detailed"
+```
+
 ## Run complete workflow (Docker + make)
 
 Following command simulates a standarized pipeline across environments,