Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1462
mockit is for unit test, not for system test. It is just like
[AbstractTestRestApi](https://github.com/apache/zeppelin/blob/master/zeppelin-server/src/test/java/org/apache/zeppelin/rest/AbstractTestRestApi.java)
where we will launch real spark cluster and ZeppelinServer. Using mockit can
not cover lots of cases in real enviroment (e.g. how can I test livy handle
comment correctly (considering we are doing some preprocessing), how can I test
SparkContext is shared correctly between %livy.spark and %livy.sql) . I know
committing jars are not good practise, but these jars won't be available in
public repository in short time.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
