[
https://issues.apache.org/jira/browse/AMBARI-25150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763575#comment-16763575
]
Hudson commented on AMBARI-25150:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10460 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10460/])
AMBARI-25150 Implement additional error reporting for ambari-web unit
(ababiichuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=2bd65e811d26210a507ee92a2da421756ebffe1b])
* (edit) ambari-web/app/assets/test/tests.js
> Implement additional error reporting for ambari-web unit tests
> --------------------------------------------------------------
>
> Key: AMBARI-25150
> URL: https://issues.apache.org/jira/browse/AMBARI-25150
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.8.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> If ambari-web unit tests fail because of JS error thrown in test files
> outside the callbacks passed to
> {{it}}/{{before}}/{{beforeEach}}/{{after}}/{{afterEach}} methods, the
> execution is just stopped without reporting the cause. This might be
> confusing because failure isn't reported if none of the previous tests failed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
