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
XMLParser's XML-Tests-Conformance project, which is automatically generated
from the W3C's Conformance Test Suites project (https://www.w3.org/XML/Test/),
stores the contents of its files in class methods. This way it's
self-contained, portable, and the actual files only need to be downloaded an
ah ok that changes everything, I agree. Why use an XML file instead of a ST
source file ? maybe using ST may be faster ?
On Mon, Apr 17, 2017 at 7:02 PM Peter Uhnak wrote:
> On Mon, Apr 17, 2017 at 12:56:42PM +, Dimitris Chloupis wrote:
> > 1 mb is not big for git , 1 gb is. It's small.
>
>
On Mon, Apr 17, 2017 at 12:56:42PM +, Dimitris Chloupis wrote:
> 1 mb is not big for git , 1 gb is. It's small.
I meant big for Pharo/to be compiled as a method source code, i.e.
Something>>xmlFile ^ ' ... 1MB of string...'
>
> I version control blender files of 100-500mbs with ease . Git i
1 mb is not big for git , 1 gb is. It's small.
I version control blender files of 100-500mbs with ease . Git is always
very fast.
I have used image files (PNG) for my project ChronosManager ,it fetches
them together with the repo, they sit in their own image folder inside the
repo folder that con
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 :
> Hi,
>
> is there a common/best practice for using external files in tests?
>
> In my
