Details
-
Task
-
Resolution: Fixed
-
Minor
-
7.1.0
-
1
-
Tools 2022-Jan, Tools 2022-Feb, Tools 2022-March, Tools 2022-April
Description
What needs to be done?
Right now a lot of keywords can fail with a Robot framework assertion not being met, which produces insufficient console output for debugging. We need to improve this.
Example:
A 'Run Process' keyword fails with an error (or simply returns an unexpected exit code), the console DEBUG-level output is not informative enough for debugging.
For example, consider the following output in the terminal console after a CLI command failed with an error:
Test data backup :: This tests that only information about the Dat... | FAIL |
|
Parent suite setup failed:
|
1 != 0
|
------------------------------------------------------------------------------
|
Test index backup :: This tests that only information about the In... | FAIL |
|
Parent suite setup failed:
|
1 != 0
|
------------------------------------------------------------------------------
|
Test fts backup :: This tests that only information about the Full... | FAIL |
|
Parent suite setup failed:
|
1 != 0
|
------------------------------------------------------------------------------
|
Test analytics backup :: This tests that only information about th... | FAIL |
|
Parent suite setup failed:
|
1 != 0
|
------------------------------------------------------------------------------
|
Test eventing backup :: This tests that only information about the... | FAIL |
|
Parent suite setup failed:
|
1 != 0
|
------------------------------------------------------------------------------
|
Collecting logs from /tmp/data/backups failed: Error opening archive at /tmp/data/backups due to `Not an archive directory`
|
SUCCESS: Request to undeploy the function was accepted
|
This is not very useful for debugging since:
- This doesn't tell us which CLI command has failed
- This doesn't show us the error traceback if one exists
- Not obvious which assertion failed
Attachments
Issue Links
- duplicates
-
-
- Closed
-