How to take screenshot in this version?

Hello!

I'm using version 2.13.4.
My current setup is:

• at Gemfile:
  gem 'allure-rspec', '= 2.13.4'

• at .rspec file:

--require spec_helper
--color
--format documentation
--format AllureRspecFormatter

• at spec_helper.rb:

require 'allure-rspec'

Allure.configure do |c|
  c.results_directory = 'results/allure-results'
  c.clean_results_directory = true
  c.logging_level = Logger::DEBUG
  c.link_tms_pattern = 'https://....testrail.net/index.php?/cases/view/{}'
  c.link_issue_pattern = 'https://trello.com/c/{}'
end

RSpec.configure do |config|
 config.formatter = AllureRspecFormatter

config.after do |e|
    Allure.step name: e
    Allure.add_attachment(
      name: e.full_description,
      source: @browser.screenshot.png,
      type: Allure::ContentType::PNG,
      test_case: true
    )
  end

  config.after :all do
    @browser.close
    envfile = FileWrite.new 'results/allure-results/environment.properties'
    envfile.write_allure_env
  end
end

• at any_spec file:

describe '[Smoke] Client', :smoke do

it 'logs into their account', tms: '12149' do
    # test code and assertions
  end

When I'm trying to update to latest version 2.15, I'm struggling with an error:

Failure/Error: Allure.step name: e

     NoMethodError:
       undefined method `steps' for nil:NilClass
     # ./spec/spec_helper.rb:99:in `block (2 levels) in <top (required)>'

Could you please help! Many thanks in advance!

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "allure-rspec":
  In Gemfile:
    allure-ruby was resolved to 0.0.1, which depends on
      allure-rspec (= 0.0.1)

Could not find gem 'allure-rspec (= 0.0.1)', which is required by gem 'allure-ruby', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

Cucumber adapter uses some internal cucumber logic which will be removed in 4.0 release.
Adjust the adapter to support cucumber 4.0.

I am not able to add attachment using allure-ruby bindings, as i am getting below message while adding attachments.
E, [2020-10-22T19:06:34.186470 #56285] ERROR -- : Can't add attachment, no test, step or fixture is running

while debugging Allure.add_attachment i found that executable_item returns nil executable_item = (test_case && @current_test_case) || current_executable

ruby version: 2.7.2
allure-rspec (2.13.6.3)
allure-ruby-commons (2.13.6.3)

Code snippet:

config.after(:each) do |example|
    clear_data
    if example.exception != nil
      screenshot_file_name = save_screenshot(file_path)
      Allure.add_attachment(name: screenshot_file_name, source: File.open(screenshot_file_name) , type: Allure::ContentType::PNG, test_case: true)
    end
end

Point is example project run fine locally.

Please help me to resolve this issue.

Hello!
In other languages we have annotations for nested steps like 'Step' in java, 'allure.step' in python and etc.
So how can i make nested steps in Ruby?

Shure i can make it like this:

# @param [String] name - name of a step
def run_step(name)
 Allure.run_step name do
    step name
  end
end


# Nested steps realization

Given(/^Make two steps$/) do
  run_step 'First step'
  run_step 'Second step'
end

And i`ll have something like this

Also i can just pass blocks of code into Allure.run_step method with name param

But it only works for void methods, cause run_step method uses yield, right?
In Java i can write something like this

    @BeforeTest
    public void setUp() {
        saySomething();
    }

    @Step(value = "With name as a annotation value")
    private String saySomethingWithName() {
        return "keke";
    }

    @Step
    private void saySomething() {
        System.out.println(saySomethingWithName());
    }

And i`ll have this result

So can you help me with solution of my problem?

1. Or i`m doing something wrong
2. Or would you kindly to answer: will this functionality ever be added?

Noticed that some items from history are duplicated.
Let's take first occurrence. We have 2 items duplicated here, report shows that they are from different runs: one from 106 and second from 107. But this test case was executed in 106 run only (sets of test cases for 106 and 107 are absolutely different).

So somehow Allure took result from 106 run and duplicate it to 107 run.

Any ideas?

Add Rspec support to latest version of allure-ruby-commons

Hi,
I'm using:
allure-ruby-commons v2.13.2
allure-rspec v2.13.0

I'm trying to attach a screenshot to the report and i get the following error:

ERROR -- : Can't add attachment, no test, step or fixture is running

The code I'm using is:

RSpec.configure do |config|
  config.include Allure
  config.after :each do |e|
  Allure.add_attachment(name: e.description, source: take_screenshot, type: Allure::ContentType::PNG)
  end
end

take_screenshot it's method that takes screenshots.

the test looks like this:
context 'some context' do it 'some test' do expect(true).to be false end end

Coveralls seems to be unmaintained and limits ability to update simplecov to get branch level coverage metrics.

Switch to CodeClimate

Currently when rspec-retry is used, retries are not registered in report. Investigate possibility of properly supporting rspec-retry.

In RSpec 3.3 its now possible to group multiple failures using aggregrate_failures metadata. How can this be handle in allure report. It just raises RSpec::Expectations::MultipleExpectationsNotMetError and doesn't show any failures. Is there a way this can be integrated?

Hi!

We have faced a problem in our RSpec tests when someone try to travel in time and then forgot to travel back. I mean these helpers https://api.rubyonrails.org/classes/ActiveSupport/Testing/TimeHelpers.html

Also there is another good reason not to use Time.now to get elapsed time https://blog.dnsimple.com/2018/03/elapsed-time-with-ruby-the-right-way/

Scenario:

• Start test
• Start step
• Run filed assertion in scope of the step

Expected result:

• Step and Test are failed

Actual result:

• Test is failed, Step is broken.

As workaround I've over override method:

module AllureRspec
  class RSpecFormatter
    def update_test_proc(result)
      Allure::ResultUtils.status_details(result.exception).then do |status_detail|
        proc do |test_case|
          step = test_case.steps.last
          if step != nil
            update_proc(step, status_detail, result)
          end
          update_proc(test_case, status_detail, result)
        end
      end
    end

    private

    def update_proc(proc, status_detail, result)
      proc.stage = Allure::Stage::FINISHED
      proc.status = status(result)
      proc.status_details.message = status_detail.message
      proc.status_details.trace = status_detail.trace
    end
  end
end

I see this has been completed - #3, but unless I'm missing something the gem for Rspec allure hasn't actually been updated yet? Will this be done soon?

We have a retries(2) option that is configured in our framework to retry when we have a failed test. Recently, we upgraded the allure-cucumber gem from 2.14.3 to 2.23.0, and due to this we see the allure report showing all the retries in the report which leads to wrong calculation of failures

Also, the report shows that failure even though the test passed a second-time retry

Ex: Test 1 - Failed
Retry Test 1 - Passed
The report shows that both Test 1 passed and Retry 1 failed

Ruby 2.7.0 is out, update project to support it

When I run my suite, After the first step is done, I'm getting a cryptic error
Could not update fixture, fixture is not started

env.rb

AllureCucumber.configure do |config|
  config.results_directory = './reports'
  config.clean_results_directory = true
  config.logging_level = Logger::INFO
  # these are used for creating links to bugs or test cases where {} is replaced with keys of relevant items
  config.link_tms_pattern = 'https://xxxx.atlassian.net/browse/{}'
  config.link_issue_pattern = 'https://xxxx.atlassian.net/browse/{}'
  config.issue_prefix = 'PI_'
end

cucumber.yml

normal: --no-source --color -p pretty

# Typical selected profiles to run against
default: -p normal -p env_trg -p user_2 --tags 'not @wip and not @broken and not @framework' --format AllureCucumber::CucumberFormatter```

So I saw this error when running my tests.

Nesting of 100 is too deep
/usr/local/bundle/gems/allure-ruby-commons-2.13.1/lib/allure_ruby_commons/model/jsonable.rb:17:in `to_json'
/usr/local/bundle/gems/allure-ruby-commons-2.13.1/lib/allure_ruby_commons/model/jsonable.rb:17:in `to_json'
/usr/local/bundle/gems/allure-ruby-commons-2.13.1/lib/allure_ruby_commons/file_writer.rb:17:in `write_test_result'
/usr/local/bundle/gems/allure-ruby-commons-2.13.1/lib/allure_ruby_commons/allure_lifecycle.rb:88:in `stop_test_case'
/usr/local/bundle/gems/allure-rspec-2.13.1/lib/allure_rspec/formatter.rb:55:in `example_finished'
/usr/local/bundle/gems/rspec-core-3.8.2/lib/rspec/core/reporter.rb:201:in `block in notify'
/usr/local/bundle/gems/rspec-core-3.8.2/lib/rspec/core/reporter.rb:200:in `each'
/usr/local/bundle/gems/rspec-core-3.8.2/lib/rspec/core/reporter.rb:200:in `notify'
/usr/local/bundle/gems/rspec-core-3.8.2/lib/rspec/core/reporter.rb:126:in `example_finished'
/usr/local/bundle/gems/rspec-core-3.8.2/lib/rspec/core/example.rb:492:in `record_finished'
/usr/local/bundle/gems/rspec-core-3.8.2/lib/rspec/core/example.rb:484:in `finish'
/usr/local/bundle/gems/rspec-core-3.8.2/lib/rspec/core/example.rb:286:in `run'

On 2.13.1.

I believe the issue is here.
https://github.com/allure-framework/allure-ruby/blob/master/allure-ruby-commons/lib/allure_ruby_commons/model/jsonable.rb#L22

Can we add max_nesting: false ?

Minitest is a fairly popular framework. Creating minitest adapter could be beneficial.

Hello!

I'm using version 2.13.4.
My current setup is:

• at Gemfile:
  gem 'allure-rspec', '= 2.13.4'

• at .rspec file:

--require spec_helper
--color
--format documentation
--format AllureRspecFormatter

• at spec_helper.rb:

require 'allure-rspec'

Allure.configure do |c|
  c.results_directory = 'results/allure-results'
  c.clean_results_directory = true
  c.logging_level = Logger::DEBUG
  c.link_tms_pattern = 'https://....testrail.net/index.php?/cases/view/{}'
  c.link_issue_pattern = 'https://trello.com/c/{}'
end

RSpec.configure do |config|
 config.formatter = AllureRspecFormatter

config.after do |e|
    Allure.step name: e
    Allure.add_attachment(
      name: e.full_description,
      source: @browser.screenshot.png,
      type: Allure::ContentType::PNG,
      test_case: true
    )
  end

  config.after :all do
    @browser.close
    envfile = FileWrite.new 'results/allure-results/environment.properties'
    envfile.write_allure_env
  end
end

• at any_spec file:

describe '[Smoke] Client', :smoke do

it 'logs into their account', tms: '12149' do
    # test code and assertions
  end

I'm struggling with:

1. Suites names are not displayed on Overview page:
   

2. component.tree.unknown is displayed on Suites page:
   

Could you please support me how to setup suites names and not having: component.tree.unknown?
I could not find solution at official documentation, neither at stackoverflow.

Many thanks in advance!

We have 2 analytics labels that should be added: language and framework.

See https://github.com/allure-framework/allure2/blob/master/Analytics.md for more details

The workflow test.yml is referencing action paambaati/codeclimate-action using references v2.7.5. However this reference is missing the commit 62e5eab9c1f8c952f64862c152e205c9c835b755 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "allure-rspec":
  In Gemfile:
    allure-ruby was resolved to 0.0.1, which depends on
      allure-rspec (= 0.0.1)

Could not find gem 'allure-rspec (= 0.0.1)', which is required by gem 'allure-ruby', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

Description

I'm trying to add allure-cucumber to an existing codebase. This codebase does not use RSpec, and test failures are triggered as explicit raise "error message" calls.
The problem: if a test fails, the failing step is correctly reported as failed, but the test itself is reported as broken.

The cause: I've narrowed this down to the on_test_case_finished method. Unlike on_test_step_finished, this method additionally calls ResultUtils.status for failed tests, which checks the failure exception against RSpec::Expectations::ExpectationNotMetError. Without RSpec, my exception is a standard RuntimeError, therefore the condition fails, and the test is labeled as broken.

I would like to clarify if this behavior is expected.

Expected Behavior

Both the step and test itself are assigned the same status - either failed or broken.

Alternative Solutions

For now I've added an override for the status method, which resolves my problem:

module Allure
  module ResultUtils
    class << self
      def status(exception)
        exception.is_a?(StandardError) ? Allure::Status::FAILED : Allure::Status::BROKEN
      end
    end
  end
end

👋 Hi there! First off thanks for creating and maintaining this incredible tool.

We are seeing a bug where the suites page completely 404s because of some missing data. Having just one test like the following

describe
   it

rather than

describe
  context
     it

will break the whole suites page. On the overview page this looks like:

Clicking on any of the above links will lead to a 404 page.
When i look at the generated allure report i'm finding a missing name field in the suites.json. I assume because it's being set to nil by the formatter.

Also here's an example of the formatter produced result of one of these breaking test cases

fdescribe "Should break suites" do
  it "test passes" do
    expect(1).to be(1)
  end
end

result:
{
  "name": "test passes",
  "description": "Location - spec/break_suites_spec.rb:2",
  "descriptionHtml": "Location - spec/break_suites_spec.rb:2",
  "status": "passed",
  "statusDetails": {
    "known": false,
    "muted": false,
    "flaky": false
  },
  "stage": "finished",
  "steps": [],
  "attachments": [],
  "parameters": [],
  "uuid": "3d21cdd0-979d-0138-e6eb-2cde48001122",
  "historyId": "33e575d46ea1f03a61ac4560da35536a",
  "fullName": "Should break suites test passes",
  "labels": [
    {
      "name": "framework",
      "value": "rspec"
    },
    {
      "name": "feature",
      "value": "Should break suites"
    },
    {
      "name": "package",
      "value": "spec"
    },
    {
      "name": "story",
      "value": "test passes"
    },
    {
      "name": "testClass",
      "value": "break_suites_spec"
    },
    {
      "name": "severity",
      "value": "normal"
    },
    {
      "name": "suite",
      "value": "Should break suites"
    },
    {
      "name": "parentSuite"
    },
    {
      "name": "subSuite"
    },
    {
      "name": "thread",
      "value": 52140
    },
    {
      "name": "host",
      "value": "WalterBenson-35215.local"
    },
    {
      "name": "language",
      "value": "ruby"
    }
  ],
  "links": [],
  "start": 1592930028708,
  "stop": 1592930028709
}

Locally works fine, but in Jenkins results do not generated.
Latest lines from Jenkins log:

Took 16 seconds
[CucumberReport] Using Cucumber Reports version 4.11.0
[CucumberReport] JSON report directory is "reports"
[CucumberReport] Copied 1 json files from workspace "/var/lib/jenkins/workspace/Allure POC/reports" to reports directory "/var/lib/jenkins/jobs/Allure POC/builds/6/cucumber-html-reports/.cache"
[CucumberReport] Copied 0 properties files from workspace "/var/lib/jenkins/workspace/Allure POC/reports" to reports directory "/var/lib/jenkins/jobs/Allure POC/builds/6/cucumber-html-reports/.cache"
[CucumberReport] Processing 1 json files:
[CucumberReport] /var/lib/jenkins/jobs/Allure POC/builds/6/cucumber-html-reports/.cache/cucumber.json
[Allure POC] $ /var/lib/jenkins/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/Allure_2.13.4/bin/allure generate "/var/lib/jenkins/workspace/Allure POC/allure/results" -c -o "/var/lib/jenkins/workspace/Allure POC/allure/report"
Report successfully generated to /var/lib/jenkins/workspace/Allure POC/allure/report
Allure report was successfully generated.
Creating artifact for the build.
Artifact was added to the build.
Finished: SUCCESS

Configuration was done as per doc, current setting (tried different folders):

Resulted Allure report:

I use
allure-rspec 2.17.0
rspec 3.11.0

STR

• configure allure and rspec

AllureRspec.configure do |config|
  config.results_directory = "report/allure-results"
  config.clean_results_directory = true
  config.logging_level = Logger::WARN

  logger = Logger.new($stdout)
  logger.sev_threshold = Logger::WARN
  config.logger = logger
end

RSpec.configure do |config|
  # Enable flags like --only-failures and --next-failure
  config.example_status_persistence_file_path = ".rspec_status"

  # Disable RSpec exposing methods globally on `Module` and `main`
  config.disable_monkey_patching!

  config.expect_with :rspec do |c|
    c.syntax = :expect
  end
end

• create test method

class TestUtils
  extend AllureStepAnnotation

  step("do something")
  def do_something
    # do something
  end
end

• Use this method in before

RSpec.describe Tests do
  before :all do
    TestUtils.new.do_something
  end

  describe "describe_1" do
    it "test_1" do
      # test something
    end
  end
end

Result:

There is no "do something" step in Allure report

Also see errors in console

E, [2022-08-25T16:37:56.794116 #8687] ERROR -- : Could not start test step, no test case is running
E, [2022-08-25T16:37:56.794143 #8687] ERROR -- : Could not start test step, no test case is running

Hello,

I have an error with codecov and allure, I don't know how to fix it, it does not happen every time.

 / ____|        | |
| |     ___   __| | ___  ___ _____   __
| |    / _ \ / _\`|/ _ \/ __/ _ \ \ / /
| |___| (_) | (_| |  __/ (_| (_) \ V /
 \_____\___/ \__,_|\___|\___\___/ \_/
                               Ruby-0.2.11
==> Circle CI detected
==> Appending file network
==> Gzipping contents
==> Uploading reports
Stopped processing SimpleCov as a previous error not related to SimpleCov has been detected

     
     Encoding::UndefinedConversionError:
       "\xE2" from ASCII-8BIT to UTF-8
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/activesupport-5.2.4/lib/active_support/core_ext/object/json.rb:38:in `to_json'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/activesupport-5.2.4/lib/active_support/core_ext/object/json.rb:38:in `to_json'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/allure-ruby-commons-2.13.6.3/lib/allure_ruby_commons/model/jsonable.rb:23:in `to_json'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/activesupport-5.2.4/lib/active_support/core_ext/object/json.rb:38:in `to_json'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/activesupport-5.2.4/lib/active_support/core_ext/object/json.rb:38:in `to_json'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/allure-ruby-commons-2.13.6.3/lib/allure_ruby_commons/model/jsonable.rb:23:in `to_json'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/json_pure-2.3.0/lib/json/common.rb:224:in `generate'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/json_pure-2.3.0/lib/json/common.rb:224:in `generate'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/allure-ruby-commons-2.13.6.3/lib/allure_ruby_commons/file_writer.rb:21:in `write_test_result'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/allure-ruby-commons-2.13.6.3/lib/allure_ruby_commons/allure_lifecycle.rb:100:in `stop_test_case'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/allure-rspec-2.13.6.3/lib/allure_rspec/formatter.rb:59:in `example_finished'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/reporter.rb:209:in `block in notify'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/reporter.rb:208:in `each'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/reporter.rb:208:in `notify'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/reporter.rb:134:in `example_finished'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/example.rb:497:in `record_finished'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/example.rb:480:in `finish'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/example.rb:440:in `fail_with_exception'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/example_group.rb:613:in `block in run'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/example_group.rb:654:in `each'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/example_group.rb:654:in `for_filtered_examples'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/example_group.rb:658:in `block in for_filtered_examples'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/example_group.rb:656:in `each'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/example_group.rb:656:in `for_filtered_examples'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/example_group.rb:613:in `rescue in run'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/example_group.rb:609:in `run'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/example_group.rb:607:in `block in run'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/example_group.rb:607:in `map'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/example_group.rb:607:in `run'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/runner.rb:121:in `block (3 levels) in run_specs'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/runner.rb:121:in `map'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/runner.rb:121:in `block (2 levels) in run_specs'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/configuration.rb:2061:in `with_suite_hooks'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/runner.rb:116:in `block in run_specs'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/reporter.rb:74:in `report'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/runner.rb:115:in `run_specs'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/runner.rb:89:in `run'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/runner.rb:71:in `run'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/lib/rspec/core/runner.rb:45:in `invoke'
     # /path_to_project/vendor/bundle/ruby/2.7.0/gems/rspec-core-3.9.3/exe/rspec:4:in `<top (required)>'
     # /path_to_project/vendor/bundle/ruby/2.7.0/bin/rspec:23:in `load'
     # /path_to_project/vendor/bundle/ruby/2.7.0/bin/rspec:23:in `<top (required)>'
     # /usr/local/lib/ruby/2.7.0/bundler/cli/exec.rb:63:in `load'
     # /usr/local/lib/ruby/2.7.0/bundler/cli/exec.rb:63:in `kernel_load'
     # /usr/local/lib/ruby/2.7.0/bundler/cli/exec.rb:28:in `run'
     # /usr/local/lib/ruby/2.7.0/bundler/cli.rb:476:in `exec'
     # /usr/local/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
     # /usr/local/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
     # /usr/local/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor.rb:399:in `dispatch'
     # /usr/local/lib/ruby/2.7.0/bundler/cli.rb:30:in `dispatch'
     # /usr/local/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor/base.rb:476:in `start'
     # /usr/local/lib/ruby/2.7.0/bundler/cli.rb:24:in `start'
     # /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/libexec/bundle:46:in `block in <top (required)>'
     # /usr/local/lib/ruby/2.7.0/bundler/friendly_errors.rb:123:in `with_friendly_errors'
     # /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/libexec/bundle:34:in `<top (required)>'
     # /usr/local/bin/bundle:23:in `load'
     # /usr/local/bin/bundle:23:in `<main>'
     # 
     #   Showing full backtrace because every line was filtered out.
     #   See docs for RSpec::Configuration#backtrace_exclusion_patterns and
     #   RSpec::Configuration#backtrace_inclusion_patterns for more information.
     # ------------------
     # --- Caused by: ---
     # Encoding::UndefinedConversionError:
     #   "\xE2" from ASCII-8BIT to UTF-8
     #   /path_to_project/vendor/bundle/ruby/2.7.0/gems/activesupport-5.2.4/lib/active_support/core_ext/object/json.rb:38:in `to_json'

Do you have any hint to solve it ?

We are bringing a new feature that allows users to run only selected test cases. How it works:

1. User uses Allure EE to select exact test cases he need to run
2. Allure EE triggers CI job and provides testplan.json file to workspace and sets ALLURE_TESTPLAN_PATH environment variable that points to testplan file.
3. Allure Test Framework Integration detects ALLURE_TESTPLAN_PATH environment and reads test plan. The format of testplan.json file:

{
   "version": "1.0", 
   "tests": [{
       "id": "test case id, aka allure id",
        "selector": "some unique id or selector that can be used to run particular test case"
    }]
}

4. Only tests that match specified id or selector should be run. The match rules:
   • if no ALLURE_TESTPLAN_PATH` specified or no file found at specified path - run all tests
   • in case of test plan parse errors - run all tests
   • in no tests specified - run all tests
   • If id is the same, include test into run
   • if selector is equals test's full name or test's uniqueId, include test into run
   • skip test execution otherwise

Reference implementation can be found here https://github.com/allure-framework/allure-java/compare/test-filter

Current implementation of allure-ruby-commons doesn't support nested steps.
Need to implement more sophisticated current step context storage in order to be able to add step inside current step etc.

Hi,
trying to implement allure-cucumber in my current project.
We use cucumber 3.1.2, so i installed allure-cucumber 2.13.4, more details below.

Tried to run test case and got an error:

undefined method `results_directory=' for AllureCucumber::CucumberConfig:Class (NoMethodError)

What may be a reason? Appreciate any suggestion.

beginning of env.rb (error appears in the line config.results_directory = "reports/allure-results"):

require 'page-object'
require 'page-object/page_factory'
require 'rspec/expectations'
require 'rspec/matchers'
require 'pp'
require 'securerandom'
require 'rest-client'
require 'json'
require 'webdrivers'
require 'allure-cucumber'
require 'capybara/cucumber'
require_relative 'test_context'
require_relative '../pages/common/base_page'
require_relative '../pages/signupv3/signupv3_base_page'
require_relative '../support/ossdb'
require_relative '../pages/oom_admin/settings/system/system_page'
require_relative '../pages/oom_admin/store/store'

World(PageObject::PageFactory)

AllureCucumber.configure do |config|
  config.results_directory = "reports/allure-results"
  config.clean_results_directory = true
  config.logging_level = Logger::INFO
  # these are used for creating links to bugs or test cases where {} is replaced with keys of relevant items
  config.link_tms_pattern = "http://www.jira.com/browse/{}"
  config.link_issue_pattern = "http://www.jira.com/browse/{}"
  c.tms_prefix = 'TMS_'
  c.issue_prefix = 'ISSUE_'
end

Capybara.configure do |config|
  config.app_host = 'https://office-qa.ooma.com'
  config.default_driver = :selenium
end

Capybara.register_driver(:selenium) do
  Capybara::Selenium::Driver.new(
      nil,
      browser: :chrome,
      clear_local_storage: true,
      clear_session_storage: true,
      desired_capabilities: {
          :browserName => 'chrome'#,
          # 'goog:chromeOptions' => { args: ['--headless'] }
      }
  )
end

Gemfile:

source 'https://rubygems.org'

ruby '2.5.3'
gem 'cucumber', '3.1.2'
gem 'selenium-webdriver', '3.142.7'
gem 'test-unit', '3.2.7'
gem 'page-object', '2.2.6'
gem 'rspec-expectations', '3.8.3'
gem 'faker'
gem 'mysql2', '0.5.2'
gem 'byebug'
gem 'ffi'
gem 'nokogiri'
gem 'activesupport'
gem 'phony'
gem 'rest-client'
gem 'faraday'
gem 'google-api-client', '~> 0.34'
gem 'webdrivers'
gem 'parallel_tests', '2.32.0'
gem 'allure-cucumber', '2.13.4'
gem 'capybara'
gem 'rspec'

My worflows file:
report:
name: Allure test report
runs-on: ubuntu-latest
needs: rspec
if: always()
steps:
- name: Download allure-results
uses: actions/download-artifact@v3
with:
name: allure-results
- name: Publish allure report
uses: andrcuns/[email protected]
env:
AWS_ACCESS_KEY_ID: ${{ secrets.QE_AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.QE_AWS_SECRET_ACCESS_KEY }}
GITHUB_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
AWS_REGION: ap-south-1
with:
storageType: s3
resultsGlob: "reports/allure-results/*"
bucket:
updatePr: actions
copyLatest: true
ignoreMissingResults: true

Error:
Glob 'reports/allure-results/*' did not match any files!

I am getting this error only when i am running this as a separate job. If i run all the tests in the same job as rspec tests it is successful

Allure Report supports parameters in steps. It would be very useful to display the parameters in each step for easier debugging

Update to latest simplecov version once issue with code climate is resolved:
codeclimate/test-reporter#413

If step is added manually using Allure.step method, it's not stopped which leads to all next steps being nested under it.
Make sure step is added and stopped immediately to prevent such behaviour.

i have already done everything to generate allure rspec report, it is very nice and cool.But I see an examplereport in : http://ci.qatools.ru/job/allure-core_master-deploy/Allure_report/.

it shows the environment information in report, but i can't be able to do it.I change the report xml to realize the target，but each running result will cover the report xml and the environment will lost.
so i want to know how to record environment information and shows it in allure rspec report?
the following is my report :

Previously When I'm running any spec files which contains test steps, I was able to see the starting and stopping steps logs on allure-rspec v0.8.0 - Now I don't see it after upgrading to latest version of allure-rspec to 2.13.6..

Please help me If I need to update some configs in my spec_helper or somewhere to get to see the logs

Hello i'm looking for compatibility with JRuby
I tried with JRuby 9.4.0.0 (Ruby 3.1.0) and JRuby 9.3.10.0 (Ruby 2.6.0 and stays in sync with C Ruby)
Exemple :
java -jar jruby-complete-9.4.0.0.jar -S gem install allure-cucumber
or
java -jar jruby-complete-9.3.10.0.jar -S gem install allure-cucumber

I always facing an issue with "Oj" and it's seems to be not be compatible with JRuby:

Is it possible to not use C extensions when installing allure-cucumber ?

Hi There,

I am using allure-rspec (0.8.0) for rspec tests and allure-cucumber(2.13.4) for cucumber tests. I am able to see the tags displayed in allure report for cucumber tests eg in output.json.

 },
    "tags" : [ "sidekiq", "js" ]
  },
  "source" : "fdd25b33e227a5b5.json",

But for rspec I see an empty array "tags": []

Currently have few rspec test with tags as context "test case", important: true do and it "new test case", data: "postgres" do.
I would like these tags to display in the output json.
I tried upgrading to allure-rspec 2.13.4 but no luck & face 404 when clicked on tests in allure report so have to go with 0.8.0

Could you please help or suggest !!

Scenario:

When running the same test suite against in parallel against different host operating systems (i.e. mac/linux/windows), I noticed that the some test results were missing from the generated suites page after generating the allure report - but the test runs were available in the timeline view

I tracked this down to the results historyId being re-used multiple times across my runners:

{
  // ...
  "parameters": [
    {
      "name": "environment",
      "value": "darwin19"
    }
  ],
  "uuid": "6c9a7870-dff7-013b-1c3f-005056a70044",
  "historyId": "5fadf4ef80bc505e534df630bc674529",
  // ...
}

Digging deeper, I noticed that the value being generated is based on the example.id, i.e. "./spec/acceptance/foo_spec.rb[1:2:1:1:11:1] - which won't be unique when running the test suite on different github action runners in parallel against windows/linux/macos

It would be great if we could influence the history id in some capacity, so that the environment properties could be considered too

Hello, good afternoon!

I've tried so far quite a lot, and i really have difficulties to establish a correct reporting for distributed execution.
Quick context: i have a pipeline which executes the same test on different drivers on separate nodes and afterwards aggregates results and generates report.

gem "allure-cucumber", "2.13.6"
first execution yields:
*-result.json
{ "name": "[chrome]::Test Case", "description": "Location - Test_Case_path:5", "descriptionHtml": "Location - Test_Case_path:5", "status": "passed", "statusDetails": { "known": false, "muted": false, "flaky": false }, "stage": "finished", "steps": [ { "name": "Given user is on the home page", "status": "passed", "statusDetails": { "known": false, "muted": false, "flaky": false }, "stage": "finished", "steps": [], "attachments": [], "parameters": [], "start": 1628172063660, "stop": 1628172067761 } ], "attachments": [], "parameters": [], "uuid": "7cbe0fc0-d823-0139-9e5b-2cde48001122", "historyId": "3afbc22fe9895d3cfa2743a512c8854c", "fullName": "Static pages: [chrome]::Test Case", "labels": [ { "name": "framework", "value": "cucumber" }, { "name": "feature", "value": "[chrome]::Static pages" }, { "name": "package", "value": "[chrome]::static_pages" }, { "name": "suite", "value": "[chrome]::Static pages" }, { "name": "story", "value": "[chrome]::User closes Cookie Banner modal" }, { "name": "testClass", "value": "[chrome]::cookie_banner" }, { "name": "tag", "value": "regression" }, { "name": "severity", "value": "normal" }, { "name": "thread", "value": 70365359570900 }, { "name": "language", "value": "ruby" }, { "name": "host", "value": "chrome" } ], "links": [], "start": 1628172060079, "stop": 1628172074768 }

*-container.json
{ "uuid": "7cbe0620-d823-0139-9e5b-2cde48001122", "name": "[chrome]::Test Case", "children": [ "7cbe0fc0-d823-0139-9e5b-2cde48001122" ], "befores": [ { "name": "hooks.rb:9", "status": "passed", "statusDetails": { "known": false, "muted": false, "flaky": false }, "stage": "finished", "steps": [], "attachments": [], "parameters": [], "start": 1628172060079, "stop": 1628172063041 }, { "name": "hooks.rb:33", "status": "passed", "statusDetails": { "known": false, "muted": false, "flaky": false }, "stage": "finished", "steps": [], "attachments": [], "parameters": [], "start": 1628172063041, "stop": 1628172063660 } ], "afters": [ { "name": "hooks.rb:20", "status": "passed", "statusDetails": { "known": false, "muted": false, "flaky": false }, "stage": "finished", "steps": [], "attachments": [], "parameters": [], "start": 1628172074570, "stop": 1628172074767 } ], "links": [], "start": 1628172060079, "stop": 1628172074770 }

second execution yields:

*-results.json
{ "name": "[chrome_iphone_x]::Test Case", "description": "Location - Test_Case_path:5", "descriptionHtml": "Location - Test_Case_path:5", "status": "passed", "statusDetails": { "known": false, "muted": false, "flaky": false }, "stage": "finished", "steps": [ { "name": "Given user is on the home page", "status": "passed", "statusDetails": { "known": false, "muted": false, "flaky": false }, "stage": "finished", "steps": [], "attachments": [], "parameters": [], "start": 1628172124046, "stop": 1628172128148 } ], "attachments": [], "parameters": [], "uuid": "a0fb4080-d823-0139-9e5c-2cde48001122", "historyId": "3afbc22fe9895d3cfa2743a512c8854c", "fullName": "Static pages: [chrome_iphone_x]::Test Case", "labels": [ { "name": "framework", "value": "cucumber" }, { "name": "feature", "value": "[chrome_iphone_x]::Static pages" }, { "name": "package", "value": "[chrome_iphone_x]::static_pages" }, { "name": "suite", "value": "[chrome_iphone_x]::Static pages" }, { "name": "story", "value": "[chrome_iphone_x]::Test Case" }, { "name": "testClass", "value": "[chrome_iphone_x]::Test Case" }, { "name": "tag", "value": "regression" }, { "name": "severity", "value": "normal" }, { "name": "thread", "value": 70176993378260 }, { "name": "language", "value": "ruby" }, { "name": "host", "value": "chrome_iphone_x" } ], "links": [], "start": 1628172120878, "stop": 1628172134911 }
*-container.json
{ "uuid": "a0fb3740-d823-0139-9e5c-2cde48001122", "name": "[chrome_iphone_x]::Test Case", "children": [ "a0fb4080-d823-0139-9e5c-2cde48001122" ], "befores": [ { "name": "hooks.rb:9", "status": "passed", "statusDetails": { "known": false, "muted": false, "flaky": false }, "stage": "finished", "steps": [], "attachments": [], "parameters": [], "start": 1628172120878, "stop": 1628172123420 }, { "name": "hooks.rb:33", "status": "passed", "statusDetails": { "known": false, "muted": false, "flaky": false }, "stage": "finished", "steps": [], "attachments": [], "parameters": [], "start": 1628172123420, "stop": 1628172124046 } ], "afters": [ { "name": "hooks.rb:20", "status": "passed", "statusDetails": { "known": false, "muted": false, "flaky": false }, "stage": "finished", "steps": [], "attachments": [], "parameters": [], "start": 1628172134727, "stop": 1628172134911 } ], "links": [], "start": 1628172120878, "stop": 1628172134915 }

As you can see almost every attribute is unique, key word here almost.

I've tried the same on last allure-cucumber version and i get the same results.

Describe the bug
Allure report not able to print values in expect of rspec from array and hash of ruby

To Reproduce
Steps to reproduce the behavior:

1. Using Allure report with Rspec and Ruby
2. Return an array or hash from method into expect of rspec
3. ex: expect(@obj.methodCallsArray).to eq true
4. If i run above command, allure report should be able to generate an array of elements raised by methodCallsArray, but No values are getting generated.

Expected behavior
An array of elements raised by method need to be displayed by allure report

Screenshots
In below screenshot near red arrow data should be available ex: "array[0]","array[1]","array[2]" what ever i had return from methodCallsArray

Environment (please complete the following information):

| Generate report using |allure-rspec (0.8.0)|

Additional context
Add any other context about the problem here.

Hello!

when allure-rspec is 2.13.6.3 or before
at Gemfile:
gem 'allure-rspec', '= 2.13.6.3'
gem 'allure-ruby-commons', '= 2.13.6.3'

at spec_helper.rb:

require 'allure-rspec'
Allure.configure do |config|
  config.results_directory = ALLURE_RESULTS_PATH
  config.clean_results_directory = true
  config.logging_level = Logger::INFO
end

RSpec.configure do |config|
	config.formatter = AllureRspecFormatter

allure-results file format is json and allure report displays correctly

{"name":"test_name","children":["e5c50e10-ec52-0139-2ffd-2cde48001122"],"befores":[],"afters":[],"links":[],"start":1630391445856,"stop":1630391454280}

I try to update 2.13.6.4
at Gemfile:
gem 'allure-rspec', '= 2.13.6.4'
gem 'allure-ruby-commons', '= 2.13.6.4'

allure-results file become to hash
"#<Allure::TestResult:0x00007fcd31cc6bf8>"

and allure report does not display correctly

When allure-rspec version is 2.15.0, allure-results file is also hash format.

Is there a way to output json?

Can you tell me what the problem with starting and generating reports might be ? For reports, I use
allure-rspec with stack - ruby + rspec + capybara.

The installation process was performed in the following order

brew install allure - (Version 2.13.2)
allure generate path

enabled dependencies in spec_helper:
require 'allure-rspec'

RSpec.configure do |config|
  include AllureRSpec::Adaptor
  config.formatter = AllureRspecFormatter
...
end

AllureRSpec.configure do |config|
  config.output_dir = 'report/allure-results'
  config.clean_dir = false
  config.logging_level = Logger::DEBUG
end

1. When I running the test, HEADLESS= "MY_ARTEC_URL= 'URI' rspec /absolute path to the file --format documentation --format AllurRspecFormatter --out rspec.xml, error => https://pastebin.com/NNrfn7Yq
   I see that there is a problem with allur_rspec_formatter, but I do not understand how to set something separately and prescribe it in the settings.
   I also took it out separately in Rakefile, but the error didn't disappear

RSpec::Core::RakeTask.new(:test) do |task|
task.rspec_opts = '--color --require spec_helper --format documentation --format AllureRspecFormatter'
task.verbose = false
end

2. When I running the test,
   HEADLESS='' rspec path --format documentation --out rspec_results.xml
   error already => 'title': wrong number of arguments https://pastebin.com/YWb20sEb`

3. When I running the test, HEADLESS='' rspec path, similar error => 'title': wrong number of arguments

Tell me where to dig or what I incorrectly configured / under- configured / under- installed / did not take into account ?

Hello dear acquaintance! 😄

In 2.13.9 it was possible to override output folder:
somewhere in cucumber.yml:

<%=
allure_reporter = "--format AllureCucumber::CucumberFormatter --out tmp/#{ENV['ALLURE_RESULTS'] || 'cucumber'}"
%>

in env.rb:

# Allure
AllureCucumber.configure do |c|
  c.results_directory = "tmp/cucumber"
  ...
end

i.e. if ALLURE_RESULTS env var is set to "hello" then output would be written to tmp/hello folder

but for same configuration code when using 2.13.10 output is written in tmp/cucumber

of course its an easy fix but is not this considered a regression from configuration point of view ? 🐛

Hi! I updated allure-rspec fron 0.8.0 -> 2.13.8.3 and found some strange behavior with tags. In particular feature and story tags.
Here code spec example for build report

describe 'Method', feature: '/some/method' do
  context 'GET', story: 'GET' do
    it 'should be success' do end
  end

  context 'POST', story: 'POST' do
    it 'should be success' do end
  end

  context 'PUT', story: 'PUT' do
    it 'should be success' do end
  end

  context 'DELETE', story: 'DELETE' do
    it 'should be success' do end
  end

  context 'PATCH', story: 'PATCH' do
    it 'should be success' do end
  end
end

On 0.8.0 version i got nice structure in Behavior section

But when i built report on last release version i found that structure is changed and started to look like this

Story has become a feature. Example name has become a story. Feature is go away :-)
Looks like a mess :-)

Or it's new cool allure ruby style?

We are currently using allure-spec (0.8.0) in our project and found that this version got deprecated. So, we are planning to upgrade allure to 2.13. Now, we are facing issue in run_step method.

Sample Code:

it "Sample code to check run_step method" do |t|
  t.run_step("Step 1") do
     p "print statement 1"
  end
end

Output:

LocalJumpError:
   no block given (yield)

Stack Trace:

# /Users/navinmuthu/.rvm/gems/ruby-2.5.1@falcon_allure_2.13.1/gems/allure-ruby-commons-2.13.1/lib/allure-ruby-commons.rb:156:in `run_step'
# /Users/navinmuthu/.rvm/gems/ruby-2.5.1@falcon_allure_2.13.1/gems/allure-rspec-2.13.1/lib/allure_rspec/formatter.rb:24:in `block (3 levels) in <class:RSpecFormatter>'

Please let me know how to use run_step method.

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "allure-rspec":
  In Gemfile:
    allure-ruby was resolved to 0.0.1, which depends on
      allure-rspec (= 0.0.1)

Could not find gem 'allure-rspec (= 0.0.1)', which is required by gem 'allure-ruby', in any of the sources.

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

Hi,
could you, please, release the current changes to make the method add_environment available?
I see it's currently in master and works fine.