jasmine

I am using Chutzpah to run our Jasmine tests. I have added the Chutzpah dlls to the solution and updated the build to run *.js tests. The project structure is as follows: MyApp.Web Scripts App Home DateControl.js MyApp.Web.Tests Scripts Jasmine lib Chutzpah (dlls) Spec App Home DateControlSpecs.js The Jasmine test file uses a reference tag to reference the file to be tested /// <reference path="../../../../../../App.web/scripts/app/home/datecontrol.js" /> The Jasmine tests are run however I get the following error: ReferenceError: Can't find variable: dateControl in file dateControl is the

I'm aware that if you were to do something like protractor config.js > file.log all the console output would be written to file.log. Is there a way to do this/access that output from within the tests though so that I can use a dynamic path that's created with my reporting tool? And also in a way that I don't lose the console output. Edits: To elaborate a little further, I'm not only interested in console.log output. I'm interested in everything that comes from what seems to be protractors testLogger . For example, at the end of a suite's execution I am presented with: [13:19:37] I/launcher - 0

how do I test this module on jasmine ? The problem is that it's very difficult to test the $controller because the function is hidden inside a closure, it’s very difficult to test them. In other words, given the module definition below, writing a unit test for MainCtrl seems impossible. (function () { 'use strict'; angular.module('app', []); function MainCtrl() { var mc = this; mc.obj = { val : 50 }; } angular.module('app').controller('MainCtrl', MainCtrl); } () ); and the "typical" jasmine test describe('app', function(){ beforeEach(module('app')); it('should create an objet with val 50',

I am testing a controller using a combination of angular and jasmine, and am not completely sure about using deffered promises. This is my spec code. describe('Controller Tests', function(){ var scope, searchAPI; beforeEach(function(){ var mockSearchAPI = {}; module('myApp', function($provide){ $provide.value('searchAPI', mockSearchAPI); }); }); inject(function($q){ var testData = {"message":"hi"}; mockSearchAPI.executeSearch = function(){ var defer = $q.defer(); defer.resolve(testData); return defer.promise; }; }); beforeEach('Main Search Controller Tests', function(){ function($controller,

Currently I'm trying to get Jasmine to run along with Webpack, to execute tests written in typescript to test Angular2 Apps in the Terminal. I researched yesterday which packages are available for testing, and while angular2 has their own approach *1 , I looked for other tools than the recommended jasmine-core or jasmines native package jasmine . I found jasmine-node which is outdated for 2 years now. Currently investigating the Webpack+Angular2 with Jasmine testing package *2 After reading Become a Ninja with Angular2 *3 by Ninja Squad I have no satisfying information on how to combine the 3

This is the code I'm testing eventsApp.factory('userData', ['userResource', function(userResource){ return{ getUser: function(userName, callback){ return userResource.get({userName:userName}, function(user){ if(callback) callback(user); }); }; }]); And this is the Jasmine test for it describe('userData', function(){ var mockUserResource; beforeEach(module('eventsApp')); beforeEach(function(){ mockUserResource = {get: function(){} }; module(function($provide){ $provide.value('userResource', mockUserResource); }); }); it('should make a call to userResource.get with provided userName', inject

I'm working on a project and we've begun to write Jasmine unit tests. This application, like any good JS app does a lot of asynchronous fetching of data. I see that angular provides $httpBackend to mock up an HTTP request. I've also read and heard that it's a bad idea to test AJAX requests in your controller, and thus the raison d'etre for $httpBackend. Why is it not a good idea to test AJAX calls? How do big JS applications get around this fact? When does the actual testing of hitting the actual servers happen? Asserting that you shouldn't be testing the server from Jasmine is an overly

I am trying to set up unit testing for a SPA using karma/jasmine First of all, the following test runs just fine in karma: /// <reference path="../../definitions/jasmine/jasmine.d.ts" /> /// <reference path="../../src/app/domain/core/Collections.ts"/> define(["app/domain/core/Collections"], (collections) => { describe('LinkedList', () => { it('should be able to store strings for lookup', () => { var list = new collections.Collections.LinkedList<string>(); list.add("item1"); expect(list.first()).toBe("item1"); }); }); }); However, collections is of type any so that I can not use it for type