javascript - Cucumber Js callback issue? or feature issue? -


i'd write feature this:

scenario: new singleton create   when new, unmatchable identity received   new tin record should created    , new bronze record should created    , new gold record should created

which tie steps this:

definesupportcode(function ({ before, given, then, when }) {    var expect = require('chai').expect;   var chancegenerator = require('./helpers/chancegenerator')   var request = require('./helpers/requestgenerator')    let identmap;    // reset identmap before each scenario    before(function () {     identmap = [];   });    // should generate valid identity   // persist in local variable can tested in later steps   // , persist db via public endpoint   when('a new, unmatchable identity received', function (callback) {     identmap.push(chancegenerator.identity());     request.pubpostidentity(identmap[identmap.length-1], callback);   });    // use local variable retrieve tin persisted   // validate tin persisted props should have   then('a new tin record should created', function (callback) {     request.pubgetidentity(identmap[identmap.length-1], callback);      // var self = this;      // request.pubgetidentity(identmap[identmap.length-1], callback, () => {     //   console.log('never gets here...');     //   self.callback();     //   callback();     // });      // request.pubgetidentity(identmap[identmap.length-1], (callback) => {     //   console.log('never gets here...');     //   self.callback();     //   callback();     // });    });

the issue i'm having can't in callback. i'd able verify response has right data.

here relevant excerpts helper files:

var pubpostidentity = function (ident, callback) {   console.log('pubidentity');   var options = {     method: 'post',     url: 'http://cucumber.utu.ai:4020/identity/' + ident.platform + '/' + ident.platformid,     headers: {       'x-consumer-custom-id': ident.botid + '_' + ident.botid     },     body: json.stringify(ident)   };   console.log('ident: ', ident);   request(options, (err, response, body) => {     if (err) {       console.log('pubpostidentity: ', err);       callback(err);     }     console.log('pubpostidentity: ', response.statuscode);     callback();   }); }  // accept identity , retrieve staging via identity public endpoint var pubgetidentity = function (ident, callback) {   console.log('pubgetidentity');   var options = {     method: 'get',     url: 'http://cucumber.utu.ai:4020/identity/' + ident.platform + '/' + ident.platformid,     headers: {       'x-consumer-custom-id': ident.botid + '_' + ident.botid     }   };   request(options, (err, response) => {     if (err) {       console.log('pubgetidentity: ', err);       callback(err);     }     console.log('pubgetidentity: ', response.body);     callback();   }); }

something considering option re-write feature fit different step definition structure. if re-wrote feature this:

scenario: new singleton create     when new, unmatchable 'tin_record' received     identity record should created     when identity record retreived 'tin'     new 'tin' should created     when identity record retreived 'bronze'     new 'bronze' should created     when identity record retreived 'gold'     new 'gold' should created

i believe bypasses instep callback issue wrestling with, hate breakdown of feature. makes feature less readable , comprehensible business.

so... question, summary feature presented first, written wrong? trying step definitions shouldn't? or lack of js skills shining bright, , should doable, i'm screwing callbacks?

firstly, i'd rewritten feature wrong. should never go in progression given, when, then. going when, wrong.

given used setting preconditions. when used actual test. used assertions. each scenario should single test, should have few when clauses. if want, can use scenario outlines mix several similar tests together.

in case, recommend take first principles , see if works. build out working.

i suspect in case problem in exception being thrown isn't handled. try rewriting use promises instead, rejected on error. gives better error reporting.


Comments

Post a Comment

Popular posts from this blog

android - InAppBilling registering BroadcastReceiver in AndroidManifest -

i'm implementing inapp billing in android app. works well, however, i'm trying decouple broadcast receiver activity manifest. suggestion in android's trivialdrive sample: // important: dynamically register broadcast messages updated purchases. // register receiver here instead of <receiver> in manifest // because call getpurchases() @ startup, therefore can ignore // broadcasts sent while app isn't running. // note: registering listener in activity bad idea, done here // because sample. regardless, receiver must registered after // iabhelper setup, before first call getpurchases(). currently there's class extends broadcastreceiver : public class iabbroadcastreceiver extends broadcastreceiver { /** * intent action receiver should filter for. */ public static final string action = "com.android.vending.billing.purchases_updated"; private final iabbroadcastlistener mlistener; public iabbroadcastreceiver(iabbroadcastlistener listener) { m...
Read more

python Tkinter Capturing keyboard events save as one single string -

is possible store keyboard events 1 string? code below stores 1 char , prints it. card reader or bar code reader, contains collection of character/ string not 1 character @ time. goal save char pressed text variable. from tkinter import * root = tk() def key(event): text= event.char text+= event.char print ("pressed", text) def callback(event): frame.focus_set() print ("clicked at", event.x, event.y) frame = frame(root, width=100, height=100) frame.bind("<key>", key) frame.bind("<button-1>", callback) frame.pack() root.mainloop() currently, creating text variable , everytime key() function gets called, , text stores last character typed. you can define text module level variable , , use module level text inside key function - text = '' def key(event): global text text+= event.char print("pressed", text)
Read more

sql server - Why does Linq-to-SQL add unnecessary COUNT()? -

here tables: create table customer ( cid int primary key, name varchar(32) ) create table ord ( oid int primary key, cid int foreign key references customer, address varchar(20) ) here's linq-to-sql statement: var aaa = c in db.customer select new { c, o = c.ord.tolist() }; and here's inexplicable query generated linq-to-sql: select [t0].[cid] [cid], [t0].[name] [name], [t1].[oid] [oid], [t1].[cid] [cid2], [t1].[address] [address], (select count(*) [dbo].[ord] [t2] [t2].[cid] = [t0].[cid]) [value] [dbo].[customer] [t0] left outer join [dbo].[ord] [t1] on [t1].[cid] = [t0].[cid] order [t0].[cid], [t1].[oid] i want understand how rid of count(*) part. it's entirely uncalled for! linq needs count(*) in order determine number of entries returned o = c.ord.tolist() .
Read more