{"id":1657,"date":"2019-01-16T22:00:00","date_gmt":"2019-01-16T21:00:00","guid":{"rendered":"https:\/\/demo.sidekick.be\/itenium\/javascript-testing-jasmine-plugins\/"},"modified":"2025-11-28T13:31:46","modified_gmt":"2025-11-28T12:31:46","slug":"javascript-testing-jasmine-plugins","status":"publish","type":"post","link":"https:\/\/demo.sidekick.be\/itenium\/blog\/javascript\/javascript-testing-jasmine-plugins\/","title":{"rendered":"JavaScript Testing: Jasmine plugins"},"content":{"rendered":"

Or apparently just <\/a>thlorenz\/proxyquire<\/a>: Proxies nodejs require in order to allow overriding dependencies during testing.<\/p>\n

and some custom reporters:
<\/a>bcaudan\/jasmine-spec-reporter<\/a>: Real time console spec reporter for jasmine testing framework <\/a>Marak\/colors.js<\/a>: Color configuration for jasmine-spec-reporter <\/a>larrymyers\/jasmine-reporters<\/a>: Reporter classes for the jasmine test framework.<\/p>\n

Other Jasmine plugins you might find useful:<\/p>\n

<\/a>node-nock\/nock<\/a>: HTTP server mocking and expectations library for Node.js <\/a>visionmedia\/supertest<\/a>: Super-agent driven library for testing node.js HTTP servers using a fluent API. <\/a>jhnns\/rewire<\/a>: Use rewire('.\/file.js')<\/code> instead of require()<\/code> and get a fresh copy each time<\/p>\n

Reporters<\/h1>\n

Jasmine Spec Reporter<\/h2>\n

Probably your goto console logger: jasmine-spec-reporter<\/a>:<\/p>\n

npm install jasmine-spec-reporter --save-dev\n<\/code><\/pre>\n
Usage:<\/p>\n
const SpecReporter = require('jasmine-spec-reporter').SpecReporter;\n\njasmine.getEnv().clearReporters();\njasmine.getEnv().addReporter(new SpecReporter({\n  spec: {\n    displayPending: true,\n    \/\/ See configuration.d.ts for more config\n    \/\/ Colors: https:\/\/github.com\/Marak\/colors.js\n    colors: {\n        failed: 'magenta',\n        prettyStacktraceError: 'magenta',\n    }\n  }\n}));\n<\/code><\/pre>\n
Jasmine-Reporters<\/h2>\n
A collection of reporters: JUnitXmlReporter, NUnitXmlReporter, AppVeyor, TapReporter, TeamCityReporter and TerminalReporter.<\/p>\n
Proxyquire<\/h1>\n
Stub imports of the code being tested.<\/p>\n
npm install --save-dev proxyquire\n<\/code><\/pre>\n
api.js<\/strong>:<\/p>\n
module.exports = {\n  someLongRunningOperation: function() {\n    for (var i = 0; i <= 1000; i++) {}\n  }\n};\n<\/code><\/pre>\n
cut.js<\/strong>:<\/p>\n
const webApi = require('.\/api.js');\nmodule.exports = function() {\n  webApi.someLongRunningOperation();\n};\n<\/code><\/pre>\n
spec.js<\/strong>:<\/p>\n
const proxyquire = require('proxyquire');\nvar apiStub = {};\nconst cut = proxyquire('.\/cut.js', {'.\/api.js': apiStub});\n\ndescribe('fake the api call', function() {\n  beforeEach(function() {\n    this.hasRunStub = false;\n    apiStub.someLongRunningOperation = () => this.hasRunStub = true;\n  });\n\n  it('should not actually call the api', function() {\n    cut();\n    expect(this.hasRunStub).toBe(true);\n  });\n});\n<\/code><\/pre>\n
VSCode Integration<\/h1>\n
The Jest VSCode test runner got me thinking, this probably also exists for Jasmine.<\/p>\n
<\/a>hbenl\/vscode-jasmine-test-adapter<\/a>: Jasmine Test Adapter for the VS Code Test Explorer<\/p>\n
And instructions for setting up a launch.json<\/code> on Stackoverflow<\/a><\/p>\n
Also in this series<\/h1>\n