Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Customize test path per framework

未關閉
#930 3 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
30/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
python
領域
testing

研究方向

The payload names no source files. The request is that the test path shown and copied in the report should follow each framework's convention, such as pytest's folder/file::test_function instead of module.module#test. Start by finding where the Python adapters build the test's full name and path, and whether the report viewer or the adapter decides the displayed format. Confirm with maintainers which side owns the change before editing. Done means a pytest run shows the pytest-style path and the copy action produces it.

由索引模型根據 Issue 內容生成。

描述

What problem should this solve?

In the current report, the test path is shown at the top of the test view and can be copied to the clipboard. It has the abstract syntax module.module#test. In pytest, the syntax for specifying test cases is different: folder/folder/filename::test_function. It would be useful if I could copy this path to the clipboard instead.

What would you like to happen?

The test path displayed in the report is customized based on the framework convention.

Alternatives considered

No response

Additional context

No response

主要語言
Python
星號
820
分支
262
平均合併
3 小時 20 分鐘
30 天內合併 PR
3

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

allure-framework/allure-python 的其他 Issue

查看 allure-framework/allure-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。