[
https://issues.apache.org/jira/browse/IMPALA-13985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18003502#comment-18003502
]
ASF subversion and git services commented on IMPALA-13985:
----------------------------------------------------------
Commit 08ae29f47b423d0e17a4e323f7fcae6d13fd2ca0 in impala's branch
refs/heads/master from Surya Hebbar
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=08ae29f47 ]
IMPALA-13985: Fix webUI JS tests naming scheme
The names of webUI's JS tests seem arbitrary and vary widely from the
the general naming scheme of other test framework generated JUnitXMLs.
This patch provides consistency to the naming scheme.
All the webUI JS tests follow the following naming scheme now.
webui.js_tests.<module>.<function>.<description>
jest-junit package has been configured to use the following config -
{
"classNameTemplate": "{classname}",
"titleTemplate": "{title}",
"ancestorSeparator": "."
}
Example:
Within JUnitXML,
<testsuites ... >
...
<testsuite
name = "webui.js_tests.fragment_diagram.getSvgTests"
... >
...
<testcase
classname="webui.js_tests.fragment_diagram.getSvgTests"
name="basic_case.SvgRect"
... >
</testcase>
...
</testsuite>
...
</testsuites>
Change-Id: I5715d47cef5c1c3c06b4f2de7fe467aee3de8868
Reviewed-on: http://gerrit.cloudera.org:8080/23071
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Riza Suminto <[email protected]>
> Rename JS Tests to better fit with general jenkins listings
> -----------------------------------------------------------
>
> Key: IMPALA-13985
> URL: https://issues.apache.org/jira/browse/IMPALA-13985
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Surya Hebbar
> Assignee: Surya Hebbar
> Priority: Minor
>
> The names of JS tests seem to vary from the other general tests on jenkins.
> They can be renamed to fit the general naming scheme.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
