★ wanayoo — archive 1999 https://github.com/allure-framework/allure-codeception/issues/28Nouvelle recherche | Portail wanayoo
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The allure report doesn't take into account Gherkin feature files #28

Open
alexrotaru opened this issue May 5, 2017 · 4 comments
Open

The allure report doesn't take into account Gherkin feature files #28

alexrotaru opened this issue May 5, 2017 · 4 comments

Comments

@alexrotaru
Copy link

@alexrotaru alexrotaru commented May 5, 2017

Hi all,

We've configured the latest dev version with codeception 2.2.10

extensions:
    enabled: 
        - Codeception\Extension\RunFailed
        - Yandex\Allure\Adapter\AllureAdapter
    config:
        Yandex\Allure\Adapter\AllureAdapter:
            deletePreviousResults: false
            outputDirectory: allure-results

We have the following feature file in tests/acceptance:

@login
Feature: login
  As a registered user
  I want the ability to login
  Using email and password

  Scenario Outline: Login
    Given that I am on "Home Page"
    When I go to "Login Page"
      And I enter <email> as the email address
      And I enter <password> as the password
      And I login
    Then I should be on <page>

    Examples:
      | email                                  | password            | page                     |
      | "email@email.com"          | "pass1!"     | "Account Dashboard Page" |
      | "incorect@email.com"     | "pass1!"     | "Login Page"             |
      | "email@email.com"          | "incorrectPassword" | "Login Page"             |

We can run the tests and they behave as expected.
When I run allure generate tests/_output/allure-results (I have on my mac allure command line tools 1.4.23 installed with brew) I get a report with the following issues:

  • there's no feature name
  • there's no story name
  • the Feature description from my feature file appear as steps in the report
  • none of the steps defined in the Scenario Outline appear in the report
  • only Actor actions appear in the report (for example $I->click()).

Please see a screenshot with the obtained report:
codeception_gherking_allure_report

I also attached the xml file (you need to change the extension from .txt to .xml).
4f8a921d-2dfe-48c3-a065-008b71f1c234-testsuite.txt

@nicholascus
Copy link
Contributor

@nicholascus nicholascus commented Nov 1, 2017

Can you provide an example project on that? Recently I've been fixing issues of allure adapter on parametrised tests. I think the parameterised gherkin need to also be addressed in my fix. I can also have a look at other issues you listed.

@nicholascus
Copy link
Contributor

@nicholascus nicholascus commented Nov 5, 2017

More changes need to be done to solve all problems you list here. My pull request only solves test level reporting for explicit and example driven scenarios.

@alexrotaru It would be wonderful if you can test the version of the adapter from my pull request.

#39

image

image

Regards
Nikolay

@Rekadze
Copy link

@Rekadze Rekadze commented Dec 27, 2017

@vania-pooh, @baev, @nicholascus Hi!
Do you know when the PR #39 will be merged? I'm really waiting it!

@baev
Copy link
Member

@baev baev commented Dec 27, 2017

Do you know when the PR #39 will be merged? I'm really waiting it!

done https://github.com/allure-framework/allure-codeception/releases/tag/1.2.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.