You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
help="Key of the test plan ticket where to add new test execution for the test results from a JUnit xml",
75
+
required=False,
76
+
default=None,
77
+
type=click.STRING,
78
+
)
72
79
@click.option(
73
80
"-m",
74
81
"--merge-xml-files",
@@ -91,6 +98,7 @@ def cli_upload(
91
98
test_execution_key: str,
92
99
test_execution_description: str,
93
100
test_execution_summary: str,
101
+
test_plan_key: str,
94
102
merge_xml_files: bool,
95
103
not_append_test_results: bool,
96
104
) ->None:
@@ -101,10 +109,15 @@ def cli_upload(
101
109
:param test_execution_key: test execution key where to upload the test results
102
110
:param test_execution_description: update the test execution ticket description - otherwise, keep current description
103
111
:param test_execution_summary: update the test execution ticket summary - otherwise, keep current summary
112
+
:param test_plan_key: test plan key where to create a new test execution ticket for the test results
104
113
:param merge_xml_files: if True, merge the xml files, else do nothing
105
114
:param not_append_test_results: if True, only overwrite the existing ones (update only), else append the new results from the .xml file(s) to the test execution
106
115
107
116
"""
117
+
iftest_plan_keyandtest_execution_key:
118
+
raiseValueError(
119
+
"You cannot specify both a test plan key and a test execution key. ""Please use either one or the other."
120
+
)
108
121
# If a new test execution ticket is being created (no key), the user should pass a description and a summary.
0 commit comments