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

Provide alternative identification mechanism for automated test cases #3932

Open
yurish opened this issue Mar 5, 2025 · 0 comments
Open

Comments

@yurish
Copy link
Contributor

yurish commented Mar 5, 2025

Is your feature request related to a problem? Please describe.
Test case identification for automated tests is using summary as ID of the test case. It makes it impossible to change the summary of the testcase after it was generated automatically, or make a summary human-readable if you prepare the case as automated

Describe the solution you'd like
Add reference ID field in the test case, which will be used for test case identification, if it is not empty. Such identification will provide possibility to use any summary you want and will also allow to identify the test case for runner plugins.

Describe alternatives you've considered
Not much alternatives. We can use testcase numerical ID from the database, but I am afraid, that it is not a good solution, because IDs can change if you migrate and numerical ID doesn't bring much information by itself.

Additional context
I am ready to implement this and provide pull request. Just need approve for such changes.

Scope of changes
TestCase model - add new CharField (max _length 255) reference_id
TCMS API - plugin_helpers add reference_id argument to test_case_get_or_create function and use it prior to summary (if reference_id was provided and is not empty)
Start implement this functionality in runner plugins (pytest and other).

@yurish yurish changed the title Provide alternative identification mechanism for test cases Provide alternative identification mechanism for automated test cases Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant