I do have plans to refactor a bit so that we can have the best of both worlds. Ther'es an option we could take to pipe the output per-scenario rather than ignore it, but your console would be flooded with sumnmary output on every single scenario you run and would be unwieldy. And scraping that summary away from the text isn't a great solution because that could vary with a given version of cucumber and that'd be a bummer for compatability
In the meantime, instead of
console.log you could simply have a debug log file that you fs.appendFile to if that help? :/ Not the solution you probably were looking for, but I have this issue noted and planned to take care of soon
This issue's also listed within the readme, and we have another solution you could try listed here if you like: https://github.com/midniteio/multi-cuke#differences-from-standard-cucumber-js
but will be looking to support you're standard
console.log/warn/error commands when I get to refactoring this
However associating it with a step would be a little more difficult without explicitly changing the console calls, which I'd like to avoid so that step definitions work regardless of cucumber/multi-cuke/parallel/serial
It will print them in order, but theyd display in order after all of the steps
I suppose we could get a timestamp at the time of console log, and then try to appropriately place it within the order of steps based on the timestamp of each step
But in any case, this would require a refactor
worker.jsfrom spawning cucumber to instead spawning a worker that runs cucumber from node (The difference being spawning cucumber as a process won't let us capture console logs with a stub because all output comes from stdout, where from node we can actively monitor the function call)
I may have spoken too soon, I forgot the reason we moved away from the above approach was an issue a coworker and I discovered with cucumber itself when calling it from it's own api (See issue #2 here: https://github.com/cucumber/cucumber-js/issues/565). It's fixed in Cucumber v2.0, but that makes supporting both v1 and v2+ of cucumber difficult with that approach.
I'll look into other possibilities on ha doing this across all cucumber versions
@guilhotarras Sure, workerEnvVars will do pretty much what it sounds like: it exports environment variables to the spawned process. I actually just looked at this to double check and realized it wasn't setting them properly, just inheritting you're current environment variables (which apparently is why we missed this, since our team duplicates that code to both export the variables and pass them :angry:) In any case, that fix lands here: midniteio/multi-cuke#68
Moving past that though, assuming that fix gets in, you can access those in your world.js just as you would any other environment variable with
process.env.PROPERTYNAME or process.env['PROPERTYNAME'] or, if using es6, you can do object deconstruction and just simply let {PROPERTYNAME} = process.env (assuming in this case your workerEnvVars looked something like {
PROPERTYNAME: 'Some value'
}
this.afterHooks = {
"preAssessmentId": null,
"iebModule": null,
"deleteStudyPlan": false,
"userLogin": null,
"userPassword": null,
"screenShots": []
};
"preAssessmentId": null,
"iebModule": null,
"deleteStudyPlan": false,
"userLogin": null,
"userPassword": null,
"screenShots": []
};
My question is, when I run multi-cuke, each thread has its own this.afterHooks variable ?
or everything on world.js is shared between the threads ?
I have noticed that when you run test 1 and test2 and the report files are generated, next you run test3 and test 4, but the merged result file uses all test1, test2, test3 and test4. I would like to have the merged result file as an output of the last execution test suite. In this example, would be for only test 3 and test 4. Is this possible ?
Current behavior is grabbing all json files to generate the results.json, and in my case I would like to grab only the json files of the last execution.
The number of worker is pretty dependent on the machine running it. I have a long-standing issue here: midniteio/multi-cuke#11 that would sort of address this by introducing an abstract cost/resource system (where you could then basically spin up clients up until you reach some threshhold of performance basically and keep you leveled there automatically). That's not been worked on yet though
I'm not sure if I have recommendations on how many you should run because it's both machine and browser dependent. As an example, we use this in my company actually testing a custom version of CEF that has more overhead than Chrome or Firefox etc would have, so our number in parallel would differ
Re: afterhooks- yeah each thread runs its own instance of Cucumber so each has its own instance of world/afterhooks/etc. For a given scenario, you'll still have access to it across each step, but you wouldn't be able to pass data from scenario to scenario (which you shouldn't do fundamentally anyway really, and in Cucumber itself I believe it will reset world and hooks on each scenario as well)
Hi Guys, trying to use multi-cuke from the command line, like this
multi-cuke src/test/features/ -t @test. However I get the message command not found: multi-cuke. I have installed via npm and I can see the multi-cuke folder in node_modules. I have also tried installing globally but same issue. Anybody got any idea what I am doing wrong?