allure-framework
Sending artifacts does not work for Cucumber on Ruby out of the box
Current behaviour
Sending artifacts does not work for Cucumber on Ruby from the box
“ERROR -- : Can't add attachment, no test, step or fixture is running” during running the method “Allure.add_attachment(name: "Attachment Video", source: video_log_path, type: Allure::ContentType::TXT, test_case: true)” - just trying to send the text with name and link as txt content type
I am running a test with: “--format AllureCucumber::CucumberFormatter” and use the latest Allure gem version
Expected behaviour
artefacts are attached to test results
Would You be able to provide an example that reproduces it? From the error it seems you are trying to add attachment before a test case is actually started.
I was not able to reproduce it via example repo: https://github.com/allure-examples/allure-cucumber-example/blob/master/features/step_definitions/common_steps.rb#L41
Originally, I could reproduce the issue within our project. Let me try with the demo example: it could be the case that we use a customized Cucumber framework on our project and some allure internal code requires minor adoption or patch within our project. I will try first with the demo project, then continue with debugging on our project, and come back to you guys with the results. Thank you for providing the example code.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Until there is a reproducible example, I don't think there is anything to do with this issue. I'm fairly certain, that and some allure internal code requires minor adoption or patch within our project is a big factor here.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days
Originally, I could reproduce the issue within our project. Let me try with the demo example: it could be the case that we use a customized Cucumber framework on our project and some allure internal code requires minor adoption or patch within our project. I will try first with the demo project, then continue with debugging on our project, and come back to you guys with the results. Thank you for providing the example code. @agileseph could you please provide the reproducible example for the issue?
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days