-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Add test case identifiers for tests being executed to console output and more informative console output #1958
Labels
enhancement
New feature or request
Comments
Yes this would help ~!
|
+1 for the "Testing" line. |
"PASSED: [test name] Hello world" |
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Apr 10, 2024
Ref: lfn-cnti#1958 Add information of which test is starting to the console output Add test name to test result console output Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Apr 19, 2024
Ref: lfn-cnti#1958 Add information of which test is starting to the console output Add test name to test result console output Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
pushed a commit
to kosstennbl/cnf-testsuite
that referenced
this issue
Apr 19, 2024
Ref: lfn-cnti#1958 Add information of which test is starting to the console output Add test name to test result console output Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
referenced
this issue
in kosstennbl/cnf-testsuite
Apr 23, 2024
Ref: cnti-testcatalog#1958 Add information of which test is starting to the console output Add test name to test result console output Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
referenced
this issue
in kosstennbl/cnf-testsuite
Apr 25, 2024
Ref: cnti-testcatalog#1958 Add information of which test is starting to the console output Add test name to test result console output Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
kosstennbl
referenced
this issue
in kosstennbl/cnf-testsuite
Apr 27, 2024
Ref: cnti-testcatalog#1958 Add information of which test is starting to the console output Add test name to test result console output Signed-off-by: Konstantin Yarovoy <konstantin.yarovoy@tietoevry.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently, console output does not provide any information about what testcase is being executed/has been executed.
Example:
$ ./cnf-testsuite single_process_type
(test is being executed, user is not informed about any action ongoing)
$ ./cnf-testsuite single_process_type
✔️ 🏆PASSED: Only one process type used ⚖👀
$
(test execution finished, user is informed about the test result, but no explicit test identifier (single_process_type) given. User needs to guess what test case it was (from the result note "Only one process type used")
Describe the solution you'd like
Give more information about what is going on and an exact test description.
Example:
$ ./cnf-testsuite single_process_type
🎬 Testing "single_process_type"
(test is being executed, user is not informed about any action ongoing)
$ ./cnf-testsuite single_process_type
🎬 Testing: single_process_type
✔️ 🏆PASSED: single_process_type ⚖👀
$
or
$ ./cnf-testsuite single_process_type
🎬 Testing: single_process_type
✖️ 🏆FAILED: single_process_type ⚖👀
$
Eventually, the "Testing" line can be replaced on then console with the result line after the test is executed. But that is probably not feasible now as the console output is mixed with logs.
Where needed, keep additional information for failed tests (where it is now)
Note that this is related to "console output". Increasing log level is not a solution for this as logging is (or rather should be) a different mechanism with potentially routing to different files than the console output.
The text was updated successfully, but these errors were encountered: