From 834ae4dbc40b802502f48bd07cf16dfcd6160b33 Mon Sep 17 00:00:00 2001
From: Olivier Le Thanh Duong <olivier@lethanh.be>
Date: Thu, 20 Jun 2024 09:59:58 +0200
Subject: [PATCH] Add more information on testing for devs

---
 TESTING.md | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/TESTING.md b/TESTING.md
index 67f9143b5..7adbae0c6 100644
--- a/TESTING.md
+++ b/TESTING.md
@@ -44,3 +44,30 @@ hatch env create testing
 ```shell
 hatch run testing:test
 ```
+
+
+## Debugging the tests
+Some tricks and options that might help debugging problematic tests.
+
+Only launch pytest with a test name and more verbose debugging
+```shell
+hatch run testing:pytest -vv --log-level=DEBUG --full-trace -o log_cli=true -k <TEST NAME>
+```
+
+
+Specify `--capture=no` to pytest so it launch. This way you get the full output, including firecracker logs
+
+## Debugging runtimes
+If the error is in the runtime:
+Modify the #!  to pass the -v option to python, which will print all the debugging info
+`#!/usr/bin/python3 -vOO`
+
+To have these modification take effect you need to rebuild the runtime file using `create_disk_image.sh` as _root_
+
+```shell
+sudo bash create_disk_image.sh
+```
+
+Don't forget to have the print system log option set `ALEPH_VM_PRINT_SYSTEM_LOGS=1`
+
+`aleph-debian-12-python` is used in test_create_execution
\ No newline at end of file