allure-framework / allure-framework/allure-python
Path to feature file in allure report
- 主要言語
- 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?
I have tests in many directories (many repos, in fact). All get run together for a report we gen in Allure.
The report shows the feature name. However, there seems to be no way to display the path to the feature file.
Because the tests are in lots of dirs - it is then rather painful to find the right file.
#### If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
#### What is the expected behavior?
Would love for the plugin to also set the path to feature file in the allure report.
#### What is the motivation / use case for changing the behavior?
Ease of use for developers and QA folks.
#### Please tell us about your environment:
- Allure version: 2.1.0
- Test framework: pytest@3.0
- Allure adaptor: allure-pytest@2.0.0b1
#### Other information
[//]: # (
. e.g. detailed explanation, stacktraces, related issues, suggestions
. how to fix, links for us to have more context, eg. Stackoverflow, Gitter etc
)
コントリビューションガイド
調査の方向性
まず、allure-pytest が feature メタデータをどのように記録し、生成された Allure レポートがそれをどのように表示するかを追跡します。想定されるソースパスの形式を確認し、複数のディレクトリにあるテストから生成されたレポートに各 feature ファイルへのパスが表示されることを検証します。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- python
- 領域
- testing
- issue の種類
- 機能追加
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 38/100