Describe the bug
When using the accessibility collector in a suite, the entire codesniffer JS source file is written to logs for each accessibility collection. This happens only in the DEBUG logs level - however this should not happen even on this level - this JS file contains few thousands lines of code.
CC @plutasnyy
To Reproduce
Steps to reproduce the behavior:
0. Make sure that the Logger on your AET environement (karaf) is set to DEBUG mode
- Prepare a suite XML with a test using accessibility collector.
- Run the suite
- View the
worker.log file - see the entry starting with
<time> | DEBUG | com.cognifide.aet.jobs | JavaScriptJobExecutor 51 | Executing JavaScript command: /* followed by the whole source of htmlcs.js file
Expected behavior
Option 1 - When writing the JS code snippet to the log file, it's length should be limited to some reasonable value (e.g. first 100 characters).
Option 2 -The Accessibility collector should not log the content of executed JS file at all
Describe the bug
When using the accessibility collector in a suite, the entire codesniffer JS source file is written to logs for each accessibility collection. This happens only in the DEBUG logs level - however this should not happen even on this level - this JS file contains few thousands lines of code.
CC @plutasnyy
AET 3.1.0To Reproduce
Steps to reproduce the behavior:
0. Make sure that the Logger on your AET environement (karaf) is set to DEBUG mode
worker.logfile - see the entry starting with<time> | DEBUG | com.cognifide.aet.jobs | JavaScriptJobExecutor 51 | Executing JavaScript command: /*followed by the whole source of htmlcs.js fileExpected behavior
Option 1 - When writing the JS code snippet to the log file, it's length should be limited to some reasonable value (e.g. first 100 characters).
Option 2 -The Accessibility collector should not log the content of executed JS file at all