Cucumber reports to include failure reasons when integrated with jenkins - selenium

i am using Selenium Web driver with Cucumber for test automation. To see the reports i am integrating with Jenkins. I am able to see the report from jenkins. It is providing the status as Passed or failed. I need to add the reasons for these failures in the report. A new column next to status has to be included for the reasons. Can anyone please help me on this as i am new to these topics?

It might be hard to include the reason of the feature failure because reason may be different for different scenarios.
What I recommend is to publish the report over Jenkins using plusgin such as Cucumber-JVM Reports

Related

How to share allure report to stakeholders?

I have generated the allure report from my webdriverio framework and configured the report in jenkins.
How can I share the allure report from jenkins to stakeholders?
Could you please help me?
Thank you for the question.
There are several ways to make this happen:
You may provide a link to the Jenkins job which contains the report but, usually, stakeholders don't want to dive into CI. Or they don't have the necessary credentials.
You may download and archive and send it. In case there are many tests in the suite, the archive might be massive. That's also an issue.
In case you need to share reports often, I would recommend trying Allure TestOps: it's an Allure Report-based management tool providing an extremely flexible report and dashboard sharing opportunities.

On running Selenium Test through Gitlab CI/CD Pipeline, Screenshots are not displaying within Extent Test Report

On running Selenium Test through Gitlab CI/CD Pipeline, Screenshots are not displaying within Extent Test Report. Test Report and Screenshots folder are getting generated separately as an artifact there but on running in local, it is displaying within test report.
I have tried base 64 encoded also for taking screenshots but it is not working. As path will change as it runs on different server when we run automation suite on Gitlab CI/CD pipeline, therefore I guess screenshots are not getting displayed within extent report.
Kindly please suggest what we can do here.
See GitLab 13.12 (May 2021)
Failed test screenshots in test report
GitLab makes it easy for teams to set up end-to-end testing with automation tools like Selenium that capture screenshots of failed tests as artifacts. This is great until you have to sort through a huge archive of screenshots looking for the specific one you need to debug a failing test. Eventually, you may give up due to frustration and just re-run the test locally to try and figure out the source of the issue instead of wasting more time.
Now, you can link directly to the captured screenshot from the details screen in the Unit Test report on the pipeline page. This lets you quickly review the captured screenshot alongside the stack trace to identify what failed as fast as possible.
See Documentation and Issue.

Can we execute/trigger selenium automation scripts through UFT

Using Webdriver, I have automated web based Application in eclipse and using QTP, I have automated Power Builder application(like desktop App).
Now both become depended module for me, from PB data's are flowing to web base application.
so, how can I achieve this. please someone provide me how to proceed with situation and give me some strategy to proceed
We have exactly the same situation where powerbuilder application is integrating with the web application, below is the solution we have followed
We are using jenkins for executions, but this can be done without jenkins also.
We have one jenkins job which executes a UFT test first and then executes the selenium test if UFT test is successfull.
At the end of test execution UFT test will generate a file with the information required by selenium test and then jenkins will trigger selenium test, selenium test will read this file to gather any required information.
Results are interpreted in the following way
If UFT test fails then jenkins will not trigger the selenium test. If the whole jenkins job is executed successfully then integration is working, if the UFT part failed then Powerbuilder is having issue and if selenium part failed then web application is having issue.

devops - selenium- jira integration into jenkins

I am working on one devops project, from selenium I am running test script and a log file is getting generated. How to configure jira to read the log file generated by selenium.. I want to go with API approch but unable to do so. Jenkins I am using as a CI tool here. Any suggestions ?
Hmm. Generally it's a better approach to display your test results in Jenkins instead of creating issues for them automatically. You didn't mention what technology you use (nodejs, java, ...), but typically you let your test runner generate a test results file that jenkins can interprete, so it will display the results nicely. There are various jenkins plugins that can help with that.
If you want to go a step further and still create issues automatically, you can script that in a separate step of your jenkins job, using the JIRA REST API and a scripting language of your choice. It just comes down to parsing the results file and let your script create issues for the failures.

Jenkins Test Result Management

I'm working with a Jenkins system, and I've recently started working to optimize the tests. There are almost a thousand Selenium tests and twice as many unit and integration tests.
I'm wondering if there is some way to find which tests are the most prone to failure so we can attack the worst offenders first. It would also be nice if there was an integrated way to track who is working on which test, and if a test has been fixed, what was done to fix it. I'm new to Jenkins, so please point me to some documentation or a plugin I can install that would help me with this.
I think what you are describing is JIRA which can tie SCMs to issues to releases to developers.
There is Jenkins to JIRA integration to create Jira issues out of Jenkins