I think the best way would be to profile it I guess, or try all options... my idea was that I will keep with the repo (because I don't want to pull off-site resources every time the test suite runs (e.g. on travis), and at the same time I didn't want to make the source code big... but I guess I could also download the file from the repo itself (if it won't be accessible locally...) which I guess would make most sense.
Thank you all for ideas. :) Peter On Mon, Apr 17, 2017 at 09:09:15AM -0300, Hernán Morales Durand wrote: > Hi Peter, > > In BioSmalltalk I download and extract all test files in the Configuration > and then use a method in abstract test class to access test files. > Cheers, > > Hernán > > > 2017-04-15 13:52 GMT-03:00 Peter Uhnak <i.uh...@gmail.com>: > > > Hi, > > > > is there a common/best practice for using external files in tests? > > > > In my specific case I am interested in git-based projects, where I have a > > big (~1MB) file stored in repository and I would like to use it in my tests. > > > > For GitFileTree project I could presumably use the following to access it: > > > > 'OP-XMI' asPackage mcPackage workingCopy repositoryGroup remotes first > > directory / 'tests' / 'my-test-file.xmi' > > > > This will retrieve the MCPackage of the Package and then retireve where it > > the repo is actually stored on the disk. > > > > Are there better ways to do this? Could something similar be done with > > IceBerg? > > > > (p.s. in theory I could compile the entire file (e.g. 1MB) to a method, > > but that is very ugly to me) > > > > Thanks, > > Peter > > > >
