Unit tests fail if cannot connect to DROID update server

[ross-spencer]

Hi,

We've two issues which result in DROID being unable to connect to its update server. Proxy settings, and whitelisting of sites.

This isn't a problem running DROID standalone as we can download signature files manually. It is a problem when building the tool. As the Unit tests seem to fail when trying to connect to the server for updates.

I am unsure if this is a call for the issue to be fixed. I can see why the tests shouldn't fail if they cannot connect to the server, and equally exactly why they should! Is there a middle ground that ensures a graceful completion of the unit tests without them failing?

Attached screenshots.

[Brian-O-TNA]

Ross, With reference to the proxy issue,have you configured the proxy settings element in your Maven settings.xml file (in the conf subdirectory of the Maven install location)? Regards, Brian

[ross-spencer]

Yes. Maven is getting through the proxy and downloading dependencies ok. You will note that droid-container builds quite late in the build process. I think this issue affects both these tests and the PRONOM http service tests.

I note there are a number of TODO comments relating to proxy in one or both of these test files.

On 13/09/2014, at 0:31, snail1966 [email protected] wrote:

Ross, With reference to the proxy issue,have you configured the proxy settings element in your Maven settings.xml file (in the conf subdirectory of the Maven install location)? Regards, Brian

— Reply to this email directly or view it on GitHub.

[paulyoung84]

This issue has been added to the DROID backlog, it will be assigned an appropriate priority but is unlikely to be included in the next release.