Closed zamrokk closed 9 months ago
No response
When we run ligo run test, even if an assertion fails, we have the full logs of the execution
But when we use Taq, it do not should the logs from the dtdout, it just takes the part of the error raised by the assertion failing
Here the first execution with ligo , and second execution using taq. We don't see the ligo logs and the second one
Taq should also display the full ligo logs because it is very helpful to debug the test file itself
see the hidden logs
🔗 Epic|Feature Link
No response
🚥 Definition of Done
🧰 Work Description
When we run ligo run test, even if an assertion fails, we have the full logs of the execution
But when we use Taq, it do not should the logs from the dtdout, it just takes the part of the error raised by the assertion failing
Here the first execution with ligo , and second execution using taq. We don't see the ligo logs and the second one
✅ To Do
Taq should also display the full ligo logs because it is very helpful to debug the test file itself
⚖️ Acceptance Criteria
see the hidden logs
🔭 Scope
No response
Code of Conduct