On 21/10/16 17:20, Stian Soiland-Reyes wrote:
+1 to remove any outdated bin-test/ scripts, they have confused me as well..
Test resources should ideally be in src/test/resources in Maven, and the
test can then use getClass().getResource*() to get it from class path
copying to a Files.createTempFile if needing a Path or File instance.
That's not how the tests work.
They read files. With base URIs.
They run outside maven as well.
Andy
On 21 Oct 2016 6:13 pm, "A. Soroka" <[email protected]> wrote:
Maybe better to prune them, since the knowledge will remain in VC?
Whatever.
---
A. Soroka
The University of Virginia Library
On Oct 21, 2016, at 12:06 PM, Andy Seaborne <[email protected]> wrote:
Several module have "testing/" directories. They are for any one the
test wants to work from files, including the W3C test manifest.
bin-test/ are old scripts to help run helpers used during development. I
doubt they work (cmd/classpath changes) but they do record knowledge.
Andy
On 21/10/16 15:38, A. Soroka wrote:
Looking in TDB's source, I see folders bin-test and testing, which seem
to contain testing scripts and manifests and data. I was wondering how to
run these? I can't seem to find a place to begin. {grin}
---
A. Soroka
The University of Virginia Library
