Execute all children test suites after the user suggests a test suite. Examples with test suites: ``` run_test "Executing at first level" "/perf" ``` will execute: ``` Executing at first level with pattern /perf /perf/symmetric/sha2/compare /perf/symmetric/sha2/rand /perf/symmetric/sha3/compare /perf/symmetric/sha3/rand /perf/asymmetric/x25519/compare /perf/asymmetric/x25519/rand /perf/asymmetric/NIST/compare /perf/asymmetric/NIST/rand ``` ``` run_test "Executing at second level" "/perf/symmetric" ``` will execute: ``` Executing at second level with pattern /perf/symmetric /perf/symmetric/sha2/compare /perf/symmetric/sha2/rand /perf/symmetric/sha3/compare /perf/symmetric/sha3/rand ``` Also works with the "full path" of the test: ``` run_test "Executing at leaf level" "/perf/symmetric/sha2/rand" ``` will execute ``` Executing at leaf level with pattern /perf/symmetric/sha2/rand /perf/symmetric/sha2/rand ``` Note: ``` run_test ``` does ``` ./test_setup $suite | grep " OK " | cut -d "[" -f1 ``` to make the log reproducible (removing the seed and the time to execute)
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be still under discussion. The issue was opened by alvarogarcia7 and has received 0 comments.