jasmine-node

I'm new to JavaScript, Node.js and jasmine. I'm trying to run a test from the book "The Node Craftsman Book", FilesizeWatcher. I've created the package.json file and run "npm install", thus installing jasmine-node locally to the project. When I run jasmine-node on the spec file I see only output from console.log but nothing from jasmine. I can see from console.log statements that calls to jasmine (e.g. expect(err).toBe("Path does not start with a slash");) are made, but there is no output. Any idea of where i should start to find an error? I know what code you are referring to. The problem is

I am having issues writing unit test for the following setup as a jira.js file (in a node.js module): var rest = require('restler'); // https://www.npmjs.com/package/restler module.exports = function (conf) { var exported = {}; exported.getIssue = function (issueId, done) { ... rest.get(uri).on('complete', function(data, response) { ... }; return exported; }; Now, i want to write unit test for my getIssue function. 'restler' is a REST client through which i make REST calls to the JIRA API to get a JIRA issue via my code. So to be able to test createIssue(..), I want to be able to mock the

I'm trying to configure a CI infrastructure at Codeship. My local meteor --test command works like charm, but I'm getting a weird error at Codeship. Local: I20141208-12:29:42.602(2)? Started I20141208-12:29:42.602(2)? . I20141208-12:29:42.603(2)? I20141208-12:29:42.603(2)? 1 spec, 0 failures I20141208-12:29:42.603(2)? Finished in 0.014 seconds PASSED jasmine-server-unit : Job => Job should be created with title, description, location and isRemote Codeship: => Started proxy. => Started MongoDB. => Errors prevented startup: While Building the application: node_modules/velocity-cli/velocity-cli

Installed jasmine-node using this: sudo npm install jasmine-node -g It is successful and shows: /usr/bin/jasmine-node -> /usr/lib/node_modules/jasmine-node/bin/jasmine-node jasmine-node@1.14.3 /usr/lib/node_modules/jasmine-node ├── underscore@1.6.0 ├── mkdirp@0.3.5 ├── walkdir@0.0.7 ├── jasmine-reporters@2.0.0 ├── coffee-script@1.7.1 ├── requirejs@2.1.14 ├── jasmine-growl-reporter@0.0.3 (growl@1.7.0) └── gaze@0.3.4 (minimatch@0.2.14, fileset@0.1.5) But when I try to run this: $ jasmine-node spec/ or jasmine-node it shows the error like this: /usr/lib/node_modules/jasmine-node/lib/jasmine-node

While trying to figure out how to make certain jasmine expect statements dependent on a previous expect statement I discovered that previous to Jasmine 2.3.0, there was not a way. (see Stop jasmine test after first expect fails ) However, Jasmine 2.3.0 added an option stopSpecOnExpectationFailure that when set to true will stop a test on the first failure. Excited by this prospect, I modified my conf.js to include the option: /* * conf.js */ exports.config = { framework: 'jasmine', specs: ['search-spec.js'], useAllAngular2AppRoots: true, jasmineNodeOpts: { stopSpecOnExpectationFailure: true }

My log4js.js file code 'use strict'; var log4js = require('log4js'); var log4jsGen = { getLogger: function getLogger() { log4js.loadAppender('file'); log4js.addAppender(log4js.appenders.file('./ApplicationLogs.log'), 'logs'); var logger = log4js.getLogger('logs'); return logger; } }; module.exports = log4jsGen; My conf.js file(specific to appender section only) "appenders": [{ "type": "log4js-protractor-appender", "append": 'false', "maxLogSize": 20480, "backups": 3, "category": "relative-logger" }], Problem: 1) IS there a way that the logs will get overwritten in each run. 2) Why log4js