I am using cucumber and watir with Ruby for test automation and pretty much new to it.
I am trying to rerun failed tests for which I am using cucumber rerun formatter.
Tests are rerunning fine on Firefox, but on chrome not all failed tests are getting re-executed.
Is there any dependency of cucumber with chrome for rerun to happen?
My bad , this was design issue rather than browser specific issue. :/
After redesigning the rerun feature flow , the issue is resolved.
The reason this was happening was multi-threading issue since multiple docker containers are involved.
Thank you for looking into it.
Related
I'm using cypress-allure-plugin in order to generate allure reports for cypress tests.
When I try to run all the specs in headed mode automatically I don't get a full report as every other test except the last has a "skipped" status in the report despite that not being the case when I watch the tests being executed.
This issue seems to be exclusive to using the "Run x integrations specs" since running them one by one manually in headed mode doesn't produce this issue and neither does running them in headless mode.
Has anybody encountered a similar issue?
EDIT: I think I found the issue. Sometimes the tests reload wipping current test results and only results that were generated afterwards are used in the report.
Well, I am able to launch my Cucumber features in parallel using Maven Surefire Plugin. I am also able to launch these tests remotely in containers using Selenoid as well.
However, when I launch my tests, they are only launched in Chrome as per my default configuration. I want to launch different tests in different browsers. Is there any dynamic way of doing it?
I did a bit of research and found that tagging each scenario with browser name like #chrome or #firefox. If I adopt the same methodology, my scenarios will always run in the same dedicated browsers.
I'm trying to run a set of cucumber selenium tests as part of a build in TFS2015, but it doesn't appear to be running them at all. I only get a timeout error. What I can conclude is that it is having difficulty starting up the browsers. I suspect that it is not running them properly from the script. Any idea how to fix?
We include Selenium tests in our feature test build by wrapping each Selenium test with MSTest and/or CodedUI attributes which works perfectly. You do have to make sure the build/test agent is configured to run in Interactive mode otherwise the test run won't have access to the desktop to automate the browser.
http://donovanbrown.com/post/2015/08/28/auto-start-build-agent-in-interactive-mode
We don't use Cucumber however so that may be the issue for you, not sure.
I'm trying to setup Jenkins to execute our UI automation(Ranorex) tests. When the job runs, the IE browser does NOT launch, thus the tests don't run.
Is there some setting that I'm missing here?
The UI automation code is built into a .exe, which is called from a .bat file.
Thanks for any help.
Have you already read the blog Integrating Ranorex Automation in Jenkins CI Process on the Ranorex website?
It looks like cucumber is caching .rb files between runs. I'm making updates to my step definitions, but I'm not seeing any changes in test behavior. Is there any way to stop cucumber from caching?
I restarted my computer, and this seemed to work. Very scientific.
You can clean the workspace after every build, you can configure this for every job you have in Jenkins, this will remove your problem. This, of course, if you are using Jenkins.