We Keep Coding

Testing Javascript function using Jasmine

I have a problem when I'm trying to test some javascript, I'm not sure that the code is actually testable, but then I would be pleased to know how to make it testable.
$("#Button").on('touchstart', () => testFunc());
function testFunc() {
button(true, userInfo, gameCode);
}
I want to test when the button is touched that the testFunc is called. I'm using Jasmine as my test framework.
But for whatever reason when I try to call the testFunc from Jasmine just to test that something is working I get the error
"ReferenceError: Can't find variable: testClass in file:///E:/Dokumenter/SemesterProjekt%20fun%20stuff/PRJ4Web/TankWebApplication/TankWebApplication/Test/Test.js (line 8)s"
I have made the reference to the file. So I'm not sure what is going on.
The test code that gives me the error
describe("Joystick test for functionallity",
function() {
beforeEach(function() {
});
it("All default values",
function() {
testFunc();
});
});
How do I test this code? Is it possible to do?

Your goal is to see if the function will be called upon button click, therefore, you must check the actual function call with
toHaveBeenCalled jasmine method.
Invoking the functions by itself doesn't make any sense (like in your example)
You should do something like this:
it('All default values', => {
spyOn(class.testFunc);
document.getElementById('Button').click();
expect(class.testFunc).toHaveBeenCalled();
}));
})

Protractor Executing afterEach before the expect has occured

For the life of me I cannot figure out why this is happening. Basically the 'it' test is running and executing correctly UNTIL the expect, at which point it jumps off the new page immediately and executes the afterEach statement. I've tried using browser.wait, .then, adding the afterEach into the 'it' browser.sleep etc and get the same result.
So does someone with more knowledge in protractor know how I can force it to execute the expect before running the afterEach?
afterEach(function() {
browser.get(browser.params.urls.base).then(function() {
$('a[href="/Account/LogOff"]').click();
});
});
it('Should use the access code url and login to the content', function() {
loginPage.registerWithAccessCode();
loginPage.accessCodeExisting(accessCode, browser.params.user.email, browser.params.user.password);
loginPage.accessCodeSubmit();
expect(browser.getCurrentUrl()).toContain('pal/placementtest/welcome');
});

Are you wrapping this in a describe?
Try this structure:
describe('My login scenario', function() {
beforeEach(function() {
loginPage.registerWithAccessCode();
// the rest of your "act" steps...
});
it('should...', function() {
expect(browser.getCurrentUrl()).toContain('pal/placementtest/welcome');
});
afterEach(function() {
// Logout
});
});

emberjs - Testing - click on a link with a link-to helper

I try to implement some tests on my app.
When i do a click(".on-action-element")it works very well, but when i try to do same on an element built with the {{#link-to}}helper i have this error
Uncaught Error: Assertion Failed: You have turned on testing mode, which disabled the
run-loop's autorun.
You will need to wrap any code with asynchronous side-effects in an
Ember.run
I 've tried to do :
it('can click on link', function (done) {
Ember.run(function() {
click('a:contains("demo")');
});
});
but with the same result. What i miss ?

All code in setup should be wrapped into Em.run
setup: function () {
Em.run(function () {
//code to prepare environment
});
}

Jasmine failing with Uncaught Reference Error

I am trying to get a project to work properly with Jasmine. I am using the project that I downloaded from here. I added another spec file, PatientSpec.js:
describe('Patient :: Create', function() {
it("Must note be null", function() {
require(['models/Patient'], function(Patient) {
var patient1 = new Patient();
expect(patient).toBeDefined();
});
});
});
You see that my var is named patient1 and I am running the expectation on the variable name patient. When I look at my index.html, all of my tests are passing, and this is obviously not defined. I pull up my console and I here is my error:
What would cause this error? Why does it fail silently?

It fails silently cause the error happens in the callback of your require call not in your test. So when the error is thrown after your test has finished. You have to run your test inside of the callback:
require(['models/Patient'], function(Patient) {
describe('Patient :: Create', function() {
it("Must note be null", function() {
var patient1 = new Patient();
expect(patient).toBeDefined();
});
});
});
Take a look at this SO do understand how to test requireJs modules

Expected a spy, but got Function

I am trying to implement a test (1) for this module (2).
My purpose is to check if the collection is fetched when a particular event is triggered.
As you can see from my comment in (2) I get the message Error: Expected a spy, but got Function.
The module works but the test fails. any ideas?
(1)
// jasmine test module
describe('When onGivePoints is fired', function () {
beforeEach(function () {
spyOn(this.view.collection, 'restartPolling').andCallThrough();
app.vent.trigger('onGivePoints');
});
it('the board collection should be fetched', function () {
expect(this.view.collection.restartPolling).toHaveBeenCalled();
// Error: Expected a spy, but got Function.
});
});
(2)
// model view module
return Marionette.CompositeView.extend({
initialize: function () {
this.collection = new UserBoardCollection();
this.collection.startPolling();
app.vent.on('onGivePoints', this.collection.restartPolling);
},
// other code
});

You need to get into the actual method, which in this case is on the prototype.
describe('When onGivePoints is fired', function () {
beforeEach(function () {
spyOn(UsersBoardCollection.prototype, 'restartPolling').andCallThrough();
app.vent.trigger('onGivePoints');
});
it('the board collection should be fetched', function () {
expect(UsersBoardCollection.prototype.restartPolling).toHaveBeenCalled();
});
});
Spying on the prototype is a nice trick you can use when you can't get to the actual instance you want to spy on.

I was also getting the same issue but I resolved it by passing an argument in the function call. Then you have to write your test case like this in the it
var data = {name:"test"}
spyOn(UsersBoardCollection.prototype, "restartPolling").and.callThrough();
UsersBoardCollection.prototype.restartPolling(data);
expect(UsersBoardCollection.prototype.restartPolling).toHaveBeenCalled();

I had this bug because I had two versions of sinon loaded, or possibly i wasn't initialising sinon-jasmine correctly. When I explicitly loaded sinon and then sinon jasmine in my spec setup, it started running correctly.