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

When the version of behave is v1.2.7.dev5, an error will appear when running using allure_behave as the report formatter. #771

Closed
gaomengsuijia opened this issue Oct 9, 2023 · 1 comment · Fixed by #798
Labels
task:new feature Requesting new capability or software feature theme:behave

Comments

@gaomengsuijia
Copy link

gaomengsuijia commented Oct 9, 2023

When the version of behave is v1.2.7.dev5, an error will appear when running using allure_behave as the report formatter.

The following is the error log:

File "Lib\site-packages\allure_behave\listener.py", line 100, in stop_scenario
should_run = (scenario.should_run_with_tags(self.behave_config.tags) and

File "Lib\site-packages\behave\model_core.py", line 398, in should_run_with_tags
return tag_expression.check(self.effective_tags)

AttributeError: 'list' object has no attribute 'check'
@lindaandiyani
Copy link

I am having the same problem, how to solve it ? @gaomengsuijia

@delatrie delatrie added bug Something isn't working theme:behave labels Mar 14, 2024
IvanBuruyane pushed a commit to IvanBuruyane/allure-python that referenced this issue Mar 19, 2024
…v1.2.7.dev5 (allure-framework#798)

Co-authored-by: Maxim <17935127+delatrie@users.noreply.github.com>
@delatrie delatrie added task:new feature Requesting new capability or software feature and removed bug Something isn't working labels Mar 25, 2024
@delatrie delatrie linked a pull request Mar 25, 2024 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task:new feature Requesting new capability or software feature theme:behave
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants