Hi Grace, >> The team here has been noticing that there are a number of commits that have been breaking existing open-source unit tests.
I noticed the same and it can be observed on the commit-build failing often. https://builds.apache.org/job/Ambari-trunk-Commit/ The idea is trunk should be always clean and there are a few of activities to avoid those issues. https://issues.apache.org/jira/browse/AMBARI-7209 https://issues.apache.org/jira/browse/AMBARI-7476 I would like get this work done on longer than a couple of weeks. Please share any feedback to make it even better! On Fri, Sep 26, 2014 at 1:38 PM, Grace Li <[email protected]> wrote: > Hi Yusaku, > > We're developing Ambari UI in Toronto for Pivotal; we met briefly at > Hortonworks back in July. > > The team here has been noticing that there are a number of commits that > have been breaking existing open-source unit tests. We believe coding > against and maintaining a set of unit tests is essential for delivering a > solid product. Does your team typically run code against these tests > before submitting patches? Additionally, we were wondering whether > Hortonworks is using any internal automated tests for testing UI features. > If so, do you have any plans to share them with the open-source community? > > Thanks, > > Grace > -- -jun
