teuton 3.3.0 → 3.4.0

data/docs/learn/10-debug.md

@@ -1,4 +1,4 @@
-[<< back](README.md)
+[<<back](../../README.md)
 
 # debug
 
@@ -50,32 +50,33 @@ end
 
 ```
 $ teuton examples/10-debug 
+
 ------------------------------------
-Started at 2026-10-21 21:50:52 +0100
+Started at 2026-10-26 16:30:56 +0000
 
 ******************** [DEBUG] count=6 ********************
  0: PING 192.168.1.1 (192.168.1.1) 56(84) bytes de datos.
- 1: 64 bytes desde 192.168.1.1: icmp_seq=1 ttl=64 tiempo=2.22 ms
+ 1: 64 bytes desde 192.168.1.1: icmp_seq=1 ttl=64 tiempo=5.11 ms
  2: 
  3: --- 192.168.1.1 estadísticas ping ---
  4: 1 paquetes transmitidos, 1 recibidos, 0% packet loss, time 0ms
- 5: rtt min/avg/max/mdev = 2.220/2.220/2.220/0.000 ms
+ 5: rtt min/avg/max/mdev = 5.106/5.106/5.106/0.000 ms
 *********************************************************
 .
 ******************** [DEBUG] count=1 ********************
  0: 1
 *********************************************************
-FFFFFF
-Finished in 35.898 seconds
+.FFFFF
+Finished in 1.431 seconds
 ------------------------------------
  
- CASE RESULTS
+ ☰ CASE RESULTS
 ┌──────┬───────────┬───────┬───────┐
 │ CASE │ MEMBERS   │ GRADE │ STATE │
-│ 01   │ student_1 │ 14.0  │ ?     │
+│ 01   │ student_1 │ 29.0  │ ?     │
 └──────┴───────────┴───────┴───────┘
 
- CONN ERRORS
+ 🗲 CONN ERRORS
 ┌──────┬───────────┬─────────┬───────┐
 │ CASE │ MEMBERS   │ HOST    │ ERROR │
 │ 01   │ student_1 │ windows │ error │

data/docs/learn/11-export.md

@@ -1,4 +1,4 @@
-[<< back](README.md)
+[<<back](../../README.md)
 
 # export
 

data/docs/learn/12-preserve.md

@@ -1,4 +1,4 @@
-[<< back](README.md)
+[<<back](../../README.md)
 
 # preserve
 
@@ -31,11 +31,11 @@ Example, executing `teuton run example/12-preserve` twice:
 ```
 var
 └── 12-preserve
-    ├── 20200519-113035
+    ├── 20200519-163035
     │   ├── case-01.txt
     │   ├── moodle.csv
     │   └── resume.txt
-    ├── 20200519-123039
+    ├── 20200519-173039
     │   ├── case-01.txt
     │   ├── moodle.csv
     │   └── resume.txt
@@ -44,4 +44,4 @@ var
     └── resume.txt
 ```
 
-The first time test was launched at 11:30, and second at 12:30 the same day.
+The first time test was launched at 16:30, and second at 17:30 the same day.

data/docs/learn/13-feedback.md

@@ -1,4 +1,4 @@
-[<< back](README.md)
+[<<back](../../README.md)
 
 # feedback
 
@@ -36,13 +36,13 @@ With `feedback: false` the fields are hidden: command, alterations, expected and
 Executing `teuton run examples/13-feedback`, we get this output:
 
 ```
-GROUPS
+☰ GROUPS
  ▶ Hide feedback messages from output
    ✔ 01 (1.0/1.0)   ┌──
         Description │ Service SSH disabled
         Command     │ *********************
         Output      │ *********
-        Duration    │ 0.008 (local)
+        Duration    │ 0.145 (local)
         Alterations │ **********************
         Expected    │ **************
         Result      │ ********

data/docs/learn/14-moodle_id.md

@@ -1,4 +1,4 @@
-[<< back](README.md)
+[<<back](../../README.md)
 
 # Moodle
 
@@ -12,7 +12,7 @@ Add a new field called `tt_moodle_id` to each case in "config.yaml". Fill it wit
 
 Example:
 
-```
+```yaml
 global:
 cases:
 - tt_members: Darth Vader
@@ -31,7 +31,7 @@ We use `tt_moodle_max_score` to customize Moodle max score. So when Teuton expor
 
 ## Example
 
-```
+```yaml
 global:
   tt_moodle_max_score: 10
 cases:

data/docs/learn/15-readme.md

@@ -1,4 +1,4 @@
-[<< back](README.md)
+[<<back](../../README.md)
 
 # readme
 
@@ -11,12 +11,12 @@ Take a look at our test definition section (Group):
 ```ruby
 group "Customize readme output" do
 
-  readme "This is our README example."
-  readme "And here we'll see how to use readme keyword"
+  doc "This is our README example."
+  doc "And here we'll see how to use readme keyword"
 
   target "Create user david."
-  readme "Help: you can use 'useradd' command to create users."
-  readme "Remember: Only root is permitted to create new users."
+  doc "Help: you can use 'useradd' command to create users."
+  doc "Remember: Only root is permitted to create new users."
 
   run "id david"
   expect "david"
@@ -26,19 +26,19 @@ end
 
 > In this example, localhost's OS must be GNU/Linux (any other compatible OS) because the command used is `id david`.
 
-There exists some `readme` instructions after `group` and `target` lines.
+There exists some `doc` instructions after `group` and `target` lines.
 
 ## Execution
 
-To generate automatically a README file from previous test, execute this:
+To generate automatically a Markdown file from previous test, execute this:
 
 ```
-$ teuton readme example/15-readme > example/15-readme/README.md
+$ teuton doc example/15-doc > example/15-doc/README.md
 ```
 
 ## Result
 
-Content of `example/15-readme/README.md` file.
+Content of `example/15-doc/README.md` file.
 
 ---
 
@@ -49,7 +49,7 @@ Teuton : 3.2.1
 
 # Test: 15-readme
 
-## Customize readme output
+## Customize doc output
 This is our readme example.
 And here we'll see how to use readme keyword
 

data/docs/learn/16-include.md

@@ -1,4 +1,4 @@
-[<< back](README.md)
+[<<back](../../README.md)
 
 # include
 
@@ -58,8 +58,8 @@ Config files into `moreconfigfiles` folder:
 
 If we execute the test we will see that 3 cases are processed. Which are defined in the files `file01.yaml`, `02/file02.yaml` and `file03.yml`.
 
-```
- CASE RESULTS
+``` 
+ ☰ CASE RESULTS
 ┌──────┬────────────┬───────┬───────┐
 │ CASE │ MEMBERS    │ GRADE │ STATE │
 │ 01   │ student_02 │ 0.0   │ ?     │

data/docs/learn/17-alias.md

@@ -1,4 +1,4 @@
-[<< back](README.md)
+[<<back](../../README.md)
 
 # alias
 
@@ -50,4 +50,4 @@ cases:
   username: obiwan
 ```
 
-Now our test will work correctly. Calling `get(:super)` will return the same value as doing `get(:superuser).
+Now our test will work correctly. Calling `get(:super)` will return the same value as doing `get(:superuser)`.

data/docs/learn/18-log.md

@@ -1,4 +1,4 @@
-[<< back](README.md)
+[<<back](../../README.md)
 
 # log
 
@@ -53,7 +53,8 @@ end
 Content of `var/18-log/case-01.txt` file.
 
 ```txt
-❯ cat var/18-log/case-01.txt 
+$ cat var/18-log/case-01.txt 
+
  CONFIGURATION
 ┌────────────────┬───────────────────────────────────┐
 │ tt_config_path │ examples/18-log/config.yaml       │

data/docs/learn/19-read_vars.md

@@ -1,4 +1,4 @@
-[<< back](README.md)
+[<<back](../../README.md)
 
 # Read vars
 

data/docs/learn/20-macros.md

@@ -1,4 +1,4 @@
-[<< back](README.md)
+[<<back](../../README.md)
 
 # Macros
 

data/docs/learn/21-exit_codes.md

@@ -1,4 +1,4 @@
-[<< back](README.md)
+[<<back](../../README.md)
 
 # Example: exit_codes
 

data/docs/learn/22-result.md

@@ -1,4 +1,4 @@
-[<< back](README.md)
+[<<back](../../README.md)
 
 # result
 

data/docs/learn/23-test-code.md

@@ -1,4 +1,4 @@
-[<<back](README.md)
+[<<back](../../README.md)
 
 # Test code
 

data/docs/learn/24-test-sql.md

@@ -1,4 +1,4 @@
-[<<back](README.md)
+[<<back](../../README.md)
 
 # Test SQL and database content
 

data/docs/learn/25-expect-result.md

@@ -1,4 +1,4 @@
-[<<back](README.md)
+[<<back](../../README.md)
 
 # expect vs result
 

data/docs/learn/26-expect_sequence.md

@@ -1,4 +1,4 @@
-[<<back](README.md)
+[<<back](../../README.md)
 
 # DSL: expect_sequence
 

data/docs/learn/27-run_script.md

@@ -1,4 +1,4 @@
-[<<back](README.md)
+[<<back](../../README.md)
 
 # DSL: run_script
 

data/docs/learn/28-upload.md

@@ -1,9 +1,11 @@
-[<<back](README.md)
+[<<back](../../README.md)
 
 # DSL: upload
 
 `upload` is a dsl instruction, whose purpose is to upload files to the remote host.
 
+> **Recommendation**: Use this function as little as possible, to minimize any modifications, changes, or alterations to the remote device.
+
 ```ruby
   upload "FILENAME", to: :host1
 ```

data/docs/learn/31-event-stop.md

@@ -0,0 +1,134 @@
+[<<back](../../README.md)
+
+# Event: stop
+
+Sometimes it may be necessary to trigger an action when a specific condition occurs; for this, we can use events.
+
+Events are defined with the following structure:
+
+```ruby
+event on: OBJECT, when: CONDITION do
+  ACTION
+end
+```
+
+Where
+* OBJECT can be `:last_target`
+* CONDITION can be `:failed`
+* And ACTION can be `stop`, `scores_to_zero`, or both.
+
+## Example
+
+In this example, we have 4 targets, all of which will function correctly except for target 3.
+
+```ruby
+group "Events: stop" do
+  target "Target 1: ok"
+  run "id root"
+  expect_ok
+
+  target "Target 2: ok"
+  run "id root"
+  expect_ok
+
+  target "Target 3: fail"
+  run "id vader"
+  expect_ok
+
+  event on: :last_target, when: :failed do
+    stop
+  end
+
+  target "Target 4: ok"
+  run "id root"
+  expect_ok
+end
+```
+
+An event is defined to trigger the `stop` action when the last target (target 3) fails.
+
+The "stop" action halts the test, setting the number of targets yet to be evaluated to zero, while the rest retain their current assessment.
+
+## Report output
+
+```
+$ teuton examples/31-event-stop 
+ 
+ 🗹 CASE RESULTS
+┌──────┬──────────┬───────┬───────┐
+│ CASE │ MEMBERS  │ GRADE │ STATE │
+│ 01   │ TOCHANGE │ 50.0  │       │
+└──────┴──────────┴───────┴───────┘
+```
+
+Process:
+* target 1 is Ok.
+* target 2 is Ok.
+* target 3 fails so the `stop` action is triggered.
+* target 4 is not evaluated because test was stopped.
+
+```
+$ cat var/31-event-stop/case-01.txt
+
+ ⚒ CONFIGURATION
+┌────────────────┬────────────────────────────────────┐
+│ tt_config_path │ examples/31-event-stop/config.yaml │
+│ tt_members     │ TOCHANGE                           │
+│ tt_script_path │ examples/31-event-stop/start.rb    │
+│ tt_sequence    │ false                              │
+│ tt_skip        │ false                              │
+└────────────────┴────────────────────────────────────┘
+
+ 🛈 LOGS
+   [16:27:43]  INFO| Event[0] triggered because target[3] failed
+   [16:27:43]  INFO| Test STOPPED!
+
+ ☰ GROUPS
+ ▶ Events: stop
+   ✔ 01 (1.0/1.0)   ┌──
+        Description │ Target 1: ok
+        Command     │ id root
+        Output      │ uid=0(root) gid=0(root) grupos=0(root)
+        Duration    │ 0.002 (local)
+        Alterations │ Read exit code
+        Expected    │ 0
+        Result      │ 0
+   ✔ 02 (1.0/1.0)   ├──
+        Description │ Target 2: ok
+        Command     │ id root
+        Output      │ uid=0(root) gid=0(root) grupos=0(root)
+        Duration    │ 0.001 (local)
+        Alterations │ Read exit code
+        Expected    │ 0
+        Result      │ 0
+   ✖ 03 (0.0/1.0)   ├──
+        Description │ Target 3: fail
+        Command     │ id vader
+        Output      │ id: «vader»: no existe ese usuario
+        Duration    │ 0.002 (local)
+        Alterations │ Read exit code
+        Expected    │ 0
+        Result      │ 1
+   ✖ 04 (0.0/1.0)   ├──
+        Description │ TEST STOPPED!
+        Command     │ 
+        Output      │ 
+        Duration    │ ? (?)
+        Alterations │ 
+        Expected    │ 
+        Result      │ 
+                    └──
+ 🗹 RESULTS
+┌──────────────┬───────────────────────────┐
+│ unique_fault │ 0                         │
+│ case_id      │ 01                        │
+│ start_time   │ 2026-10-30 16:27:43 +0000 │
+│ finish_time  │ 2026-10-30 16:27:43 +0000 │
+│ duration     │ 0.006686742               │
+│ max_weight   │ 4.0                       │
+│ good_weight  │ 2.0                       │
+│ fail_weight  │ 2.0                       │
+│ fail_counter │ 2                         │
+│ grade        │ 50                        │
+└──────────────┴───────────────────────────┘
+```

data/docs/learn/32-event-zero.md

@@ -0,0 +1,127 @@
+[<<back](../../README.md)
+
+# Event: scores to zero
+
+We are going to create an event that triggers when the last target fails, and which sets all the scores for the targets already evaluated to zero.
+
+```ruby
+event on: :last_target, when: failed do
+  scores_to_zero
+end
+```
+
+## Example
+
+In this example, we have 4 targets, all of which will function correctly except for target 3.
+
+```ruby
+group "Events: scores_to_zero" do
+  target "Target 1: ok"
+  run "id root"
+  expect_ok
+
+  target "Target 2: ok"
+  run "id root"
+  expect_ok
+
+  target "Target 3: fail"
+  run "id vader"
+  expect_ok
+
+  event on: :last_target, when: :failed do
+    scores_to_zero
+  end
+
+  target "Target 4: ok"
+  run "id root"
+  expect_ok
+end
+```
+
+The event, before target 3, is defined to trigger the `scores_to_zero` action when target fails.
+
+The action resets the values ​​of all already-evaluated targets to zero.
+
+## Report output
+
+```
+$ teuton examples/32-event-zero
+
+ ☰ CASE RESULTS
+┌──────┬──────────┬───────┬───────┐
+│ CASE │ MEMBERS  │ GRADE │ STATE │
+│ 01   │ TOCHANGE │ 25.0  │ ?     │
+└──────┴──────────┴───────┴───────┘
+```
+
+Process:
+* target 1 is Ok.
+* target 2 is Ok.
+* target 3 fails so the `scores_to_zero` action is triggered. Targets 1 and 2 are reset to zero.
+* target 4 is Ok.
+
+```
+$ cat var/32-event-zero/case-01.txt 
+
+ ⚒ CONFIGURATION
+┌────────────────┬────────────────────────────────────┐
+│ tt_config_path │ examples/32-event-zero/config.yaml │
+│ tt_members     │ TOCHANGE                           │
+│ tt_script_path │ examples/32-event-zero/start.rb    │
+│ tt_sequence    │ false                              │
+│ tt_skip        │ false                              │
+└────────────────┴────────────────────────────────────┘
+
+ 🛈 LOGS
+   [16:27:47]  INFO| Event[0] triggered because target[3] failed
+   [16:27:47]  INFO| Scores READJUSTED!
+
+ ☰ GROUPS
+ ▶ Events: scores_to_zero
+   ✔ 01 (0.0/1.0)   ┌──
+        Description │ Target 1: ok (SCORE TO ZERO)
+        Command     │ id root
+        Output      │ uid=0(root) gid=0(root) grupos=0(root)
+        Duration    │ 0.002 (local)
+        Alterations │ Read exit code
+        Expected    │ 0
+        Result      │ 0
+   ✔ 02 (0.0/1.0)   ├──
+        Description │ Target 2: ok (SCORE TO ZERO)
+        Command     │ id root
+        Output      │ uid=0(root) gid=0(root) grupos=0(root)
+        Duration    │ 0.001 (local)
+        Alterations │ Read exit code
+        Expected    │ 0
+        Result      │ 0
+   ✖ 03 (0.0/1.0)   ├──
+        Description │ Target 3: fail (SCORE TO ZERO)
+        Command     │ id vader
+        Output      │ id: «vader»: no existe ese usuario
+        Duration    │ 0.002 (local)
+        Alterations │ Read exit code
+        Expected    │ 0
+        Result      │ 1
+   ✔ 04 (1.0/1.0)   ├──
+        Description │ Target 4: ok
+        Command     │ id root
+        Output      │ uid=0(root) gid=0(root) grupos=0(root)
+        Duration    │ 0.001 (local)
+        Alterations │ Read exit code
+        Expected    │ 0
+        Result      │ 0
+                    └──
+ 🗹 RESULTS
+┌──────────────┬───────────────────────────┐
+│ unique_fault │ 0                         │
+│ case_id      │ 01                        │
+│ start_time   │ 2026-10-30 16:27:47 +0000 │
+│ finish_time  │ 2026-10-30 16:27:47 +0000 │
+│ duration     │ 0.006894103               │
+│ max_weight   │ 4.0                       │
+│ good_weight  │ 3.0                       │
+│ fail_weight  │ 1.0                       │
+│ fail_counter │ 1                         │
+│ grade        │ 25                        │
+└──────────────┴───────────────────────────┘
+```

data/docs/more.md

@@ -9,7 +9,10 @@
 
 # Videos
 
-> By now there are no English videos. We are sorry!
+> By now there are no English videos. Sorry!
+
+Teuton v3.0:
+* [RubySur Agosto 2026 - Test de Infraestructura Teuton](https://www.youtube.com/live/JW4T3cTyG5A?si=bt356lypKlrr_YLK)
 
 Teuton v2.1:
 * [Apuntes FP Informática - I Congreso Virtual - Mayo 2020](https://youtu.be/RxIV26BAoGo)