The client arguments (clientArgs) given to "karma run" have no effect when I'm using RequireJS -

-

i'm trying pass grep argument karma-mocha plugin pass mocha , run tests match grep. command line this:

./node_modules/.bin/karma run -- --grep='one'

however, karma goes on tests, in same way if not use --grep. according karma run --help, after -- should client arguments. (it referred clientarg in , in discussions how run karma run.) tried small project without requirejs , worked. seems adding requirejs causes problem. here small setup reproduces issue:

karma.conf.js:

module.exports = function(config) {   config.set({     basepath: '',     frameworks: ['mocha', 'requirejs'],     files: [       'test-main.js',       { pattern: 'test/**/*.js', included: false }     ],     exclude: [],     preprocessors: {},     reporters: ['progress'],     port: 9876,     colors: true,     loglevel: config.log_info,     autowatch: false,     browsers: ['chrome'],     singlerun: false,     concurrency: infinity   }); };

test-main.js:

var alltestfiles = []; var test_regexp = /(spec|test)\.js$/i;  object.keys(window.__karma__.files).foreach(function (file) {   if (test_regexp.test(file)) {     var normalizedtestmodule = file.replace(/^\/base\/|\.js$/g, '');     alltestfiles.push(normalizedtestmodule);   } });  require.config({   baseurl: '/base',   deps: alltestfiles,   callback: window.__karma__.start });

what see here functionally equivalent stock test-main.js generated karma init. edited remove comments, normalize space, , add semi-colons.

the test/test.js file contains:

it("one", function () {}); it("two", function () {});

explanation

this problem how karma init generates test-main.js file used configure requirejs , kick off test. issue not specific mocha happen other runners accept parameters passed through clientargs.

the test-main.js generated karma init broken. you can see here when karma calls start itself, it calls own configuration:

this.loaded = function () {   // has error -> cancel   if (!haserror) {     this.start(this.config)   } [...]

however, test-main.js created karma init calls start without argument, , why plugin not getting arguments should getting.

solution

modify test-main.js have callback in requirejs config:

callback: window.__karma__.start.bind(window.__karma__, window.__karma__.config)

this cause start called in same way in code snippet shown earlier. if reason not bind or need more in callback, do:

callback: function () {   // other stuff...   window.__karma__.start.call(window.__karma__, window.__karma__.config); },

Comments

Post a Comment

Popular posts from this blog

sql - invalid in the select list because it is not contained in either an aggregate function -

-
i can't figure out rewrite sql statement avoid error below msg 8120, level 16, state 1, line 26 column 'staffmember.staffmemberid' invalid in select list because not contained in either aggregate function or group clause. sql statment select (select [dbo].[udf_readstaffmemberbasic](sm.staffmemberid) xml path ('staffmembersummary'), root ('items'), type ), count(sm.staffmemberid) totalresults, ceiling(cast(count(sm.staffmemberid) decimal)/ @pagesize) totalpages staffmember sm inner join staffmembertoadditionalrole ar on sm.staffmemberid = ar.staffmemberid (sm.firstname '%' + @name + '%' or sm.surname '%' + @name + '%') , (@floorid null or sm.floorid = @floorid) , (@directorateid null or sm.directorateid = @directorateid) , (@additionalroleid null or ar.additionalroleid = @additionalroleid) order sm.staffmemberid offset @page * @pagesize rows fe...
Read more

Angularjs unit testing - ng-disabled not working when adding text to textarea -

-
i trying test angularjs component using karma, mocha, power-assert. have textarea , button in component, button disabled based on length of text in textarea. when run component in browser works perfectly. can't figure out how test functionality. here's bit of code. inquiryform.js function inquiryform($scope) { // plan add logic here } angular.module('myapp').component('inquiryform', { controller: inquiryform, controlleras: 'inquiryform', templateurl: 'inquiryform.html' }); inquiryform.html <div class="contact"> <div>thanks contacting us.</div> <form> <textarea ng-model="inquiryform.inquirytext" name=""></textarea> <input type="submit" value="send" ng-disabled="!inquiryform.inquirytext.length"> </form> </div> inquiryformtest.js describe('inquiry form ', () => { let $r...
Read more

How to start daemon on android by adb -

-
can me please, head swollen... i trying run daemon on android emu/device command: adb -s <device_name> shell su -c /dir/daemon <port_number> but nothink happens, , no errors! if do: adb -s <device> shell and form shell cmdline: su -c /dir/daemon <port_number> than work fine. try use shell-script , run: adb -s <device_name> shell sh su -c /dir/script.sh <port_number> and try generate script qt code port number , use: adb -s <device_name> shell sh su -c /dir/script.sh but not helped... problem if enter adb shell previous run daemon - work. problem on different device/emu/iso_image different command format not work. example: adb -s <device_name> shell su -c /dir/daemon <port_number> // work @ emu, not @ iso and vice: adb -s <device_name> shell su -c "/dir/daemon <port_number>" // work @ iso etc. everybody can answer what's matter? sorry english adb shell su -c ...
Read more