jasmine

Pretty new to meteor, velocity and jasmine so not sure if I am doing something wrong, using Jasmine for something it's not designed for, or this is just the way it works. I am finding I need to set timeouts for pretty much all of my tests in order to get them to pass. Should this be the case or am I doing something incorrectly? For example some tests I am running to check validation messages: describe("add quote validation", function() { beforeEach(function (done) { Router.go('addQuote'); Tracker.afterFlush(function(){ done(); }); }); beforeEach(waitForRouter); it("should show validation when

Is there a way to have an expectation that an element is eventually on the page? e.g. a way for browser.wait(protractor.ExpectedConditions.presenceOf(element(by.partialLinkText('Continue'))), 1000, 'Unable to find continue link'); to fail with an expectation error instead of a timeout? Essentially a way to have a isEventuallyPresent() instead of isPresent() in the line below expect(element(by.partialLinkText('Continue')).isPresent()).toBe(true); For reference, I'm using browser.ignoreSynchronization = true even though it's an Angular app, and using Jasmine (at least for now). Using the facts

I have a very simple service call and a jasmine test for it. Service call: myServiceCall(testId: number) : void { const url = `${this.url}/paramX/${testId}`; this.http.put(url, {},{headers: this.headers}).subscribe(); } My Test Method: it('should call myServiceCall', inject([MyService], (service: MyService) => { let testId = undefined; service.myServiceCall(testId); let req = httpMock.expectOne(environment.baseUrl + "/paramX/123"); expect(req.request.url).toBe(environment.baseUrl + "/paramX/123"); expect(req.request.body).toEqual({}); req.flush({}); httpMock.verify(); })); I get of course an

I have a controller test that depends on the Angular $routeParams service: var $routeParams, MainCtrl, scope; beforeEach(inject(function ($controller, $rootScope, $injector, $templateCache) { scope = $rootScope.$new(); $routeParams = $injector.get('$routeParamsMock'); MainCtrl = $controller('MainCtrl', { $scope: scope, $routeParams: $routeParams, }); })); it('should load a pg from $routeParams', function(){ scope.userData = {}; $routeParams._setPg('PG_FIRST'); scope.$digest(); timeout.flush(); expect(scope.userData.pg).toBe(0); $routeParams._setPg('PG_SECOND'); scope.$digest(); timeout.flush()

So for some reason, when I run protractor, Firefox (32 latest) just opens with an empty browser and doesn't navigate to the baseURL. The tests I have written work fine with chrome, but not with firefox. It probably has something to do with the way the conf file is set up. Any ideas? Conf file: exports.config = { allScriptsTimeout: 11000, specs: [ 'e2e/*.js' ], multiCapabilities: [ { 'browserName': 'firefox' }, { 'browserName': 'chrome' } ], chromeOnly: false, chromeDriver: 'e2e/chromedriver/', baseUrl: 'http://localhost:9000/', framework: 'jasmine', jasmineNodeOpts: { defaultTimeoutInterval:

My Node-based project is implemented using native ES module support on Node thanks to the --experimental-modules CLI switch (i.e. node --experimental-modules ). Obviously, when I run a spec using Jasmine node --experimental-modules ./node_modules/jasmine/bin/jasmine I get the following error: Error [ERR_REQUIRE_ESM]: Must use import to load ES Module Is it ever possible to use Jasmine using ES modules in Node? If not, is there any alternative to don't use a framework (e.g. running tests with npm scripts)? It was easier than I thought. It's just about calling a file which you might call run.mjs

Vague version question: How can I use require inside a spec with grunt? Context: I'm working on an existent node project that has no tests yet, so I read some and realized to use karma and jasmine. I read some tutos (including these): http://kwilson.me.uk/blog/use-karma-and-grunt-to-run-your-jasmine-tests-in-real-time/ http://ahexamples.blogspot.com.br/2014/03/example-of-jasmine-karma-sonar-grunt.html So I'm trying to run my specs with grunt and getting this error: X encountered a declaration exception ReferenceError: Can't find variable: require in file:///(...)-spec.js (line 2) (1) The line