Replies: 3 comments
-
Ok. Let me give few examples. EXAMPLE 1 The test file has undefined function at the same time those two values open debugger when something going wrong (setf 5am:*on-error* :debug)
(setf 5am:*on-failure* :debug) What will be in the debugger?
CONCLUSIONS 1 There is no any reference to source code The result screen is too verbose and does not have source code reference |
Beta Was this translation helpful? Give feedback.
-
The example 2 The source code is (def-suite* main-test)
(test dumy-test
(is (= 2 1) "2 equal 2")
)
(defun run-tests-for-ci ()
(setf 5am:*on-error* :debug)
(setf 5am:*on-failure* :debug)
(run! 'main-test)
(typespec-test))
(run-tests-for-ci) The result screen
The first line is actual test fail but 'v' shorcut open the source code of CONCLUSIONS 1 There is no any reference to source code |
Beta Was this translation helpful? Give feedback.
-
I believe, I can be wrong. I just do not know how to use FiveAM correctly. So please let me know |
Beta Was this translation helpful? Give feedback.
-
Is there a way to make the test report less verbose (less empty lines, less unnecessary lines) but more human readable (with color markup) and references to the source code (For example failed test line M-. jump to test function definition)?
Beta Was this translation helpful? Give feedback.
All reactions