dalehenrich / gsteststats Goto Github PK

...so that output routed to Github actions has the nice coloring, while output to log files can have coloring turned off ...

from @rjsargent:

(classNames collect: [:each | Rowan globalNamed: each ]) reject: [:each | each isNil ]
I prefer having some record of what was rejected rather than having it silently be ignored. I don't know what it would take to be able to report the names which couldn't be resolved.

• produce the .json file used by the rowanTestStats.stone script ... local batch jobs will GsTestStats runner to drive batch test runs, produce .json file and compare to stored test results ...
• optionally omit the detailed listing of passing tests (can be too much information) only list detail for failing/erroring tests
• produce a .json file to be stored as github action artifact, that can be downloaded and stored/compared locally
• add full stacks (frame label and frame variables) for analyzing github ci failures
• use the .json file to drive test/debug sessions via GsTestStatsCI.solo script for debugging and confirmation of test results against local run

... extra credit for automating the generateBootstrapGsFiles.solo?

I think the way to do this would be to create an example .solo/.stone script that interprets the .smalltalkCi.ston file and arranges to run an equivalent GsTestStatus run ... worth doing if GsTestStatus can emulate the majority of use cases for GemStone test runs

...

... should have canonical order for output ... expecially when large number of failing tests are involved ...