Renamed Schemes to make it clear what you're working on. Previously the schemes were named "Bluepill" and "Bluepill-cli" when in fact they corresponded to bluepill and bp respectively. Now the scheme names match the targets.
Better console output that makes it clearer where the output is coming from. For example, output from the bluepill executable wasn't tagged before. Now it is. Log lines that said Simulator N were in fact referring to BP-N.
Removed the --junit-output, --json-output, and --plain-output options. The reports generated were not in a format that was easy to consume and just complicated the code. Now, when --output-directory is specified, it will enable the XML and JSON reporting. (See next item)
Many fixes to reporting. Now Bluepill will produce two reports when outputDirectory is specified:
TEST-FinalReport.xml which is contains every test run by bluepill. This means that for tests that failed, were retried, and eventually passed we report an entry for each attempt.
trace-profile.json is a Crhome tracingformat report that can be loaded in Chrome by typing chrome://tracing in the location bar. It shows a timeline of the test execution and can be helpful in debugging tests or improving the test time. The trace profile includes also CPU and Memory statistics.
This is what it looks like:
Fixes: #303, #301, and #238
Fix a bug where we were only catching SIGINT when in fact SIGTERM is more commonly used in CI/CD environments. Now we catch SIGINT, SIGTERM, and SIGHUP and properly terminate, deleting all simulators, if any of those signals are received. Please don't SIGKILLbluepill as it will leak running simulators.
jerrymarino
commented
5 years ago
Removed
[Additional Failure]output (#322)Renamed Schemes to make it clear what you're working on. Previously the schemes were named "Bluepill" and "Bluepill-cli" when in fact they corresponded to
bluepillandbprespectively. Now the scheme names match the targets.Better console output that makes it clearer where the output is coming from. For example, output from the
bluepillexecutable wasn't tagged before. Now it is. Log lines that saidSimulator Nwere in fact referring toBP-N.Removed the
--junit-output,--json-output, and--plain-outputoptions. The reports generated were not in a format that was easy to consume and just complicated the code. Now, when--output-directoryis specified, it will enable the XML and JSON reporting. (See next item)Many fixes to reporting. Now Bluepill will produce two reports when
outputDirectoryis specified:TEST-FinalReport.xmlwhich is contains every test run by bluepill. This means that for tests that failed, were retried, and eventually passed we report an entry for each attempt.trace-profile.jsonis a Crhome tracing format report that can be loaded in Chrome by typingchrome://tracingin the location bar. It shows a timeline of the test execution and can be helpful in debugging tests or improving the test time. The trace profile includes also CPU and Memory statistics. This is what it looks like:Fixes: #303, #301, and #238
Fix a bug where we were only catching
SIGINTwhen in factSIGTERMis more commonly used in CI/CD environments. Now we catchSIGINT,SIGTERM, andSIGHUPand properly terminate, deleting all simulators, if any of those signals are received. Please don'tSIGKILLbluepillas it will leak running simulators.