I am trying to show Jasmine SpecRunner style page using karma-jasmine, karma and gulp plugins but not able to see all the specs listing all of the test that passed on failed. I used karma-jasmine-reporter node module to get a report of the tests that ran but how can I rerun an individual test. I am looking to generate a page like this where I can see the result and rerun individual tests.
I've found that https://www.npmjs.com/package/karma-jasmine-html-reporter the karma-jasmine-html-reporter is the best UI reporter that gets close to the default jasmine html file look.
Your question is old, but it's what I was trying to find myself.
If you found a better solution since posting I'd like to know. One thing that this HTML reporter doesn't do is refresh if you updated the tests.
So if you run 'karma start' then it will run the tests, open your browser then you have to click on the debug button to show the UI reporting of your tests.
Then if you update the tests, the cmd window will refresh to reflect your new tests but the browser window will not. You must refresh it manually. Would be awesome to not have to do that.
Related
So I have a Cypress Automation that we recently refactored to use Background at the top of each feature file so that it is called with each Scenario.
However, now we need only certain tests in the scenario to utilize the Background Event at the top.
I've been reviewing Cypress documentation and cannot see if this is possible but can the Cypress Background event be limited to only certain Tags used for a scenario (i.e. #NormalLoad, #HighLoad, etc.)
Currently using Cypress/Cucumber with Gherkin design.
Instead of using the Background statement, which would run in every scenario of this feature, I propose you to run a Before targeting a tag at the feature, and the script would be doing the same as Background. The main difference between background and Before is that you can run the Before on any feature that have the appropriate tag.
We are using grapesjs to create an application editor. We want to validate that all the components we create can be used in Grapesjs. To do it, we want to write e2e tests using UI to simulate a final user. I'm using Cypress for automation but didn't have any luck dropping block inside the grapes iframe. Any help regarding this would be highly appreciated.
Me and my coworker tryied for 2 weeks, both Cypress and the rest of the tools on the market couldn't drag and drop a block of GrapesJs inside it's iframe :/
You can follow the issue from GrapesJs: https://github.com/artf/grapesjs/issues/3721
And a discussion i opened in Cypress's repo:
https://github.com/cypress-io/cypress/discussions/17979
Last month, i find this option, but i didn't try to set it as false on grapesjs.init, can you test it?
https://github.com/artf/grapesjs/blob/dev/src/editor/config/config.js#L111
I am trying to automate a website using cypress and I came across a problem where in I have to handle below tag. On click, new window gets opened which gets displayed out of the test runner.
a href="javascript:ContextTradeMenuPopup('View/Edit Trade')">View/Edit
Trade /a
I understand Cypress does not support multi window but as a workaround I can get the href tag and copy the URL and can open the URL in same runner, but in the above example there is no URL.
Can anyone help with different ways available in Cypress to handle multi window/ multiple tab behavior.
Thanks!
The work around you mentioned is currently the only work around that is available. So you should retrieve the URL of the new window/tab and visit that directly. If you can't do that you sadly can't automate it.
I am new to parasoft and trying to test some web UI functionality. I have used chrome to record the web session and it is working fine when run with chrome. But now I want to test the same on Firefox, but I am not getting any option to make it run on firefox. It always opens in chrome only.
So please, if anyone is aware of changing the browser preference to playback would be appreciated.
as the test case is bit big, I don't want to re-record using Firefox.
Thanks.
To change browser which you want to use during test, you should go to Test Configuration and select appropriate test configuration used to execute test.
Then in Execution view select browser which you want to use.Other option is to use built test configuration with selected browser already.
Is there a way to debug (set breakpoints, follow code step-by-step etc.) JavaScript code that was dynamically added via AJAX? I can't find it, seems like it only allows to review inline JS (main page source) and in external .js files.
It's currently not possible to debug dynamically evaluated scripts, because the Firefox debugger APIs Firebug is based on don't give access to them yet.
Though there's already a bug report at Mozilla asking for these APIs.
There's also a simple test case for eval()ed scripts on Jan 'Honza' Odvarko's website.
Edit:
Debugging dynamically evaluated scripts is possible. The only thing you have to take care of is that you choose the right evaluated script. E.g. when you click the "Eval!" button of the test case twice, you'll see two evaluated scripts inside the Script Location Menu, but just the latter is debuggable.
Sebastian