- 'SpecReporter' is not assignable to type 'Reporter | CustomReporter' #588
Update signature of CustomReporterResult
to fix collision with new jasmine properties
Before:
export interface CustomReporterResult extends jasmine.CustomReporterResult {
duration?: string
}
Now:
export interface CustomReporterResult extends jasmine.CustomReporterResult {
_jsr?: {
formattedDuration?: string
}
}
- Use colors/safe #538
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
}
}
- pretty stacktrace: catch uncaught exception on node internal files #479
- Promote colors as a dependency #472
- New option to display pretty stacktraces #467
displayStacktrace
options now take a value among none
, raw
and pretty
.
- Correct report from jasmineStarted event #185
- 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
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;
- Add an option to remove duration from execution summary.
- Add jasmine & protractor integration tests #82
- Add
displaySpecErrorMessages
anddisplaySummaryErrorMessages
to DisplayProcessor #85 - Add an option to remove error messages #62
- Add an option to customize stacktrace filtering #72
-
Remove support for node 0.10
-
jasmine-spec-reporter
module exportsSpecReporter
andDisplayProcessor
, see SpecReporter and DisplayProcessor usages. -
Extract groups in configuration and rationalize property names, see new structure. #57
-
Colors deactivation is now achieved with this configuration:
{ colors: { enabled: false } }
-
Custom options for custom processors must now be stored in this configuration field:
{ customOptions: { foo: 'bar' } }
- Migrate code base to TypeScript
- Add example for TypeScript integration
- Extract each example in a dedicated node module, see examples
- Add successes summary. #49
- Display seed used if specs are randomized. #55
- Added support for windows platform to show tick mark and cross symbols. #52
- Add singular form of spec metrics. #41
- Add pending summary to display pending reasons. #33
- Have same sign/color convention than jasmine default reporter for pending specs.
- Add tests on colors. #34
- Bump dependencies versions
Ensure that colors are always enabled. #36
- Fixes All specs displayed when using
fdescribe
andfit
. #37
- Disabled specs was incorrectly reported as failed. #28
- Tests: Use jasmine env instead of fake env #25
-
stacktrace:
displayStacktrace
option has now 4 modes available #26:- all: display stacktraces for failed specs and in failures summary.
- specs: display stacktraces for failed specs only.
- summary: display stacktraces in failures summary only.
- none: do not display stacktraces.
-
processor:
- add
displayJasmineStarted
hook - add
displaySpecStarted
hook #23
- add
displayStacktrace: true
is not working anymore. You will have to choose the displayStacktrace mode that suits you best.
- Bump dependencies versions
- Rework documentation
When a suite or spec is focused, it displays the total of specs defined and the number of skipped specs #11
Add support for jasmine 2.x #10
-
Jasmine 1.x is not supported by this version
-
Skipped specs are not displayable in favour of pending specs.
-
stacktrace:
displayStacktrace
option has now 4 modes available:- all: display stacktraces for failed specs and in failures summary.
- specs: display stacktraces for failed specs only.
- summary: display stacktraces in failures summary only.
- none: do not display stacktraces.
-
processor: add
displayJasmineStarted
hook
displayStacktrace: true
is not working anymore. You will have to choose the displayStacktrace mode that suits you best.
- Bump colors versions
- Rework documentation
Add message when reporter 1.x is used with jasmine > 1.x
Fixes error when the stacktrace is undefined #22
Add suite number option #19
Add customProcessors option #18
Jasmine spec reporter is no more added to the jasmine object. So, make sure to use it like it is described in the usage section.
Display failures summary #13
-
Add option to disable colors #4
-
Add option to overwrite color theme #5
-
Add option to include skipped specs #2
Add option to display spec duration #6
Display human readable duration #9
Added a hack procedure to remove dot reporter #8
Add options to exclude successful / failed specs #3
Add option to include stack trace on failure #1
First version with unit tests