reporter output cruft

This issue has been tracked since 2021-07-21.

I just upgraded from v2 to v3, and the browser log output is now in JSON.stringify() format, which for my purposes is far from ideal -- namely due to character escaping necessary of the log message.

I know I can create my own reporter, but I want 99% of what the default TAP reporter does and would really prefer not to duplicate all that code and then have to manually keep it up-to-date.

I have created a draft PR #1463 which adds a log_processor config to address this. I didn't want to do anything more extensive without consulting the project maintainer(s) on the best way to go about this, but this is working as expected. Thoughts?

Just add the config function to testem.js, for example:

  log_processor(log) {
    return log.text;
  },
More Details About Repo
Owner Name testem
Repo Name testem
Full Name testem/testem
Language JavaScript
Created Date 2011-07-12
Updated Date 2022-11-22
Star Count 2953
Watcher Count 71
Fork Count 409
Issue Count 127

YOU MAY BE INTERESTED

Issue Title Created Date Updated Date