accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3456) Accumulo client configuration affects unit tests
Date Tue, 30 Dec 2014 22:54:13 GMT


Christopher Tubbs commented on ACCUMULO-3456:

Which specific tests are affected? In my view, it seems odd that a unit test (unless it's
a very specific one, testing the ZKInstance) should be affected, since unit tests should be
written to be more narrow in their scope. It makes sense that integration tests would be affected,
though. There are three solutions, I can think of:

# Add a test resource for the client configuration, and use that first in the configuration
search path.
# Fix tests to only use Instance / Connector options which accept the configuration directly
and bypass the search path.
# Add a system property, {{-Daccumulo.config=<some location>}}, to use explicitly which
will bypass the search path, and set that in our surefire configuration.

I like option #3, generally, even beyond this issue, because it makes it easier to create
service launch scripts.

> Accumulo client configuration affects unit tests
> ------------------------------------------------
>                 Key: ACCUMULO-3456
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>            Reporter: Josh Elser
>             Fix For: 1.6.2, 1.7.0
> Accumulo unit tests (and probably integration tests, too) will fail if a client configuration
file exists in the default location on the local filesystem {{~/.accumulo/config}}.
> Our tests shouldn't be affected by the presence of these files on the local filesystem.

This message was sent by Atlassian JIRA

View raw message