Github user kxepal commented on the pull request:
https://github.com/apache/couchdb/pull/394#issuecomment-197440993
I would like to suggest a bit different way, again a bit complicated, but
with more potential in future. We eventually have a
https://github.com/apache/couchdb-erlang-tests repository which is eventually
empty. I planned to use it exactly for the purpose you propose here: all the
common helpers, patterns, abstract common things that helps to keep our tests
more specific on what they doing and not pollute you editor space with
implementation specifics, especially when they get repeated all the time
(recall how we test chttpd resources...).
Suddenly, my work on that idea stopped right there because lack of time and
great ideas decomposition done right. But I would be happy if you take this
flag while it left all alone.
I still think that this would be better way to go, because we actually
shouldn't keep too much logic in here with our current design whatever we think
about it. Also, if one day we'll try to make each app to be tested in
standalone mode, we wouldn't have to take this big repo into the dependencies,
but use another one, more specific and his goals.
Sound good for you? (:
---
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.
---
