Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/619#issuecomment-170532356
Having test utils separated from the main body of test itself sounds like a
good idea.
More integration tests is very welcome, so thank you!
What do you think if instead of having `class TestUtils` +
`TestUtils.xxx(..., driver)` calls everywhere on the client, we move all those
goodies to something like `abstract class AbstractZeppelinIT` and have `class
ZeppelinIT extends AbstractZeppelinIT` ?
This way we can still have all that code separated and available as part of
skeletal implementation for every other test, each will possess a `driver`
instance and the client code will look simpler and shorter: `something(...)` vs
`TestUtils.something(..., driver)`
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
