Executing jest test statements from the node repl - javascript

Is there any way to execute jest test statements line by line (either using a jest setting or through the node repl)?

you need to use node debugging, like: https://nodejs.org/en/docs/guides/debugging-getting-started/ . Then, you can set a breakpoint at the first line of your test and step through from there.
Visual Studio code has a debugger that makes this easy, and you can use extensions like Ora's popular jest extension to auto run all your tests and add a link to easily launch debugging on any failing test.

Related

How to run a single .feature file in a Playwright + Cucumber automation testing framework?

I create Automation testing framework with Playwright + Cucumber.js written in Javascript language.
Everytime I type npm run test in the Console all the Cucumber scenarios (.feature files) are ran. But how can I run only one .feature scenario? Is there a command for this?
It would be really nice if you give me a tip how to run tests with tags, too.
I tried to run different commands but didn't succeed in running a single .feature test.
I tried to run tests with tags, but couldn't do it.
Sure you can, for running one feature it`s
npm run test <FullPathOfFeature>.feature
For running even only one scenario in feature it`s
npm run test <FullPathOfFeature>.feature:<LineOfCodeWhereScenarioIsDefined>

Triggering Karma tests in the test runner

I am having a small issue with WebStorm that I am hoping someone has experienced and solved before.
I am using WebStorm to build a angular.js app and I have it set up to use Karma to run my tests. This is fine for the most part: I have a Karma configuration setup and I can get to to run the tests or debug them with no issue.
My problem is that when I try to run a test individually by clicking on one of the test in the "Test Run" tree it goes off to a node configuration, tries to run it and fails (because its looking for js dependencies). After that I just go back to my 'karma config' and it runs through the whole of the test no problem.
Does anyone know how I can get the IDE hooked up so that I can trigger my tests from the UI?
Running tests from file right-click menu is only supported for those runners that allow executing individual tests (JSTestDriver, for example). There is currently no such possibility for Karma (WEB-13173). See the discussion at https://github.com/karma-runner/karma/issues/1235.
to run individual test files, you can have several karma configuration files with different sets of tests included. Plus you can rename individual tests/suits in the way mentioned in https://github.com/karma-runner/karma/issues/553

When using (substack's) Tape module for testing, how do I run only one test in a file?

When using Tape how do I run a specific test and ignore all other tests?
According to the docs: Change that test's code from test(//etc) to test.only(//etc). It will be the only test run for that process.
Otherwise, you can put a certain test or tests in a separate file and just run that file alone.

Debugging mocha tests in IntelliJ: doesn't stop on breakpoints

I'm trying to debug my Mocha test in IntelliJ 13.1.4 so I put breakpoints in my test/test.js file.
In my Node.js Run/Debug Configurations, I've correctly set the Node interpreter and the Working directory points to my project root.
The JavaScript file to execute is set to ./node_modules/.bin/mocha.
If I click on the "Debug" button, my test is executed, but my breakpoints are ignored.
Does someone know why?
Actually, it seems to be more a Mocha problem.
Here is what I did thanks to that other similar SO answer: adding --debug-brk to the Application parameters in the Run/Debug Configuration.

Trying to debug program through mocha (using --debug-brk) debugs mocha itself

I installed this open source projects and mocha tests run but I want to debug the functions called by the tests but when I try to debug (using mocha --debug-brk), i see that debug is in the mocha code itself..
How do i accomplish this?
I get past this same issue by using node-inspector to add my real breakpoint, and just click pause/continue, which will stop at the real breakpoint then.

Categories

Resources