6.0.0

Feature

• Use colors/safe #538

Breaking change

String prototype does not contain color properties anymore, colors must now be applied with the new theme component available as a field in custom display processors.

Before:

class MyProcessor extends DisplayProcessor {
  public displaySuccessfulSpec(spec: CustomReporterResult, log: string): string {
    return 'OK '.successful + log
  }
}

Now:

class MyProcessor extends DisplayProcessor {
  public displaySuccessfulSpec(spec: CustomReporterResult, log: string): string {
    return this.theme.successful('OK ') + log
  }
}

5.0.2

Bugfix

• pretty stacktrace: catch uncaught exception on node internal files #479

5.0.1

Bugfix

• Promote colors as a dependency #472

5.0.0

Feature

• New option to display pretty stacktraces #467

Breaking change

displayStacktrace options now take a value among none, raw and pretty.

4.2.1

Bugfix

• Restore compatibility with jasmine < 2.5.0 #222, #223

4.2.0

Feature

• Support reporting errors in afterAll #210, #214

4.1.1

Bugfix

• Correct report from jasmineStarted event #185

4.1.0

Feature

• If any defined spec is not executed, report INCOMPLETE rather than SUCCESS #142, #145

Other

• Rewrite unit tests by bumping jasmine-core to 2.6.x #155
• Use yarn for development #98, #138
• Add greenkeeper-yarn.sh to automatically updates yarn.lock on greenkeeper PR

4.0.0

• Use string primitive instead of String wrapper object #134, #137

Breaking change

It only impacts TypeScript integrations, DisplayProcessor methods signature now use string instead of String.

Before:

displaySuite(suite: CustomReporterResult, log: String): String;

Now:

displaySuite(suite: CustomReporterResult, log: string): string;