This issue is raised to record the readability concerns introduced by the rule-based infrastructure change and to collect ideas externally.
With the introduction of the rule-based infrastructure in xbsa, additional messages and structural markers were added to the test logs. While this improves internal structure and extensibility, it also significantly changes the log output compared to the previous format.
As a result, the current log output is harder to scan and interpret for users who rely on manual log inspection and debugging. In particular, it is less obvious:
- which tests are being executed,
- where failures occur, and
- how individual sub-test results contribute to a parent rule result.
The goal of this issue is to track improvements to the xbsa test log output so that we can restore a similar level of readability to what users had before the rule-based change, without breaking existing parsers or tooling.
Attached is a comparison of:
#1 Log output before the rule-based change
#2 Current log output (after the rule-based change)
#3 A proposed refinement for a future release
Cc @chetan-rathore, @amrathesh, @anncheng-arm
This issue is raised to record the readability concerns introduced by the rule-based infrastructure change and to collect ideas externally.
With the introduction of the rule-based infrastructure in xbsa, additional messages and structural markers were added to the test logs. While this improves internal structure and extensibility, it also significantly changes the log output compared to the previous format.
As a result, the current log output is harder to scan and interpret for users who rely on manual log inspection and debugging. In particular, it is less obvious:
The goal of this issue is to track improvements to the xbsa test log output so that we can restore a similar level of readability to what users had before the rule-based change, without breaking existing parsers or tooling.
Attached is a comparison of:
#1 Log output before the rule-based change
#2 Current log output (after the rule-based change)
#3 A proposed refinement for a future release
Cc @chetan-rathore, @amrathesh, @anncheng-arm