allure-framework / allure-framework/allure-python

Allure-pytest: report.longrepr information just available in allure web app if test fails with an exception

未关闭
#558 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
task:new feature theme:pytest
主要语言
Python
星标
814
派生
260
PR 合并指标
30 天内没有已合并 PR

描述

[//]: # (
. Note: for support questions, please use Stackoverflow or Gitter**.
. This repository's issues are reserved for feature requests and bug reports.
.
. In case of any problems with Allure Jenkins plugin** please use the following repository
. to create an issue: https://github.com/jenkinsci/allure-plugin/issues
.
. Make sure you have a clear name for your issue. The name should start with a capital
. letter and no dot is required in the end of the sentence. An example of good issue names:
.
. - The report is broken in IE11
. - Add an ability to disable default plugins
. - Support emoji in test descriptions
)

#### I'm submitting a ...
- [ ] bug report
- [X] feature request
- [ ] support request => Please do not submit support request here, see note at the top of this template.

#### What is the current behavior?

Allure-pytest plugin just show failure information if the test throws an exception.

https://github.com/allure-framework/allure-python/blob/5e7bc860b5ddc1e072b0302022669183f2c4321f/allure-pytest/src/listener.py#L161-L182

#### What is the motivation / use case for changing the behavior?
Some useful plugins, like [pytest-check](https://github.com/okken/pytest-check), allow a non-fatal assertion behaviour modifying "report.longrepr" variable. "report.longrepr" could be valuable to get extra information in case of fail without exception information.

#### Please tell us about your environment:

- Allure version: 2.13.8
- Test framework: pytest@6.2.2
- Allure adaptor: allure-pytest@2.8.32

贡献指南

打开贡献指南

调研方向

从 allure-pytest/src/listener.py 的第 161-182 行开始,检查当前如何收集失败信息。跟踪 pytest 对无异常失败的报告处理流程,然后让 report.longrepr 在 Allure Web 报告中可用;当显示 pytest-check 等插件产生的非致命断言详细信息时,即表示完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
python
领域
testing
Issue 类型
功能
难度
3/5
预计耗时
1-2 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
45/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。