On 2014-11-17 22:07, rastersoft wrote:
The first one is how to define each unitary test; my original idea
was: one file, one test, so inside a folder called unitests will
be as many .vala files as unitary tests (even in subfolders). But
then
I considered that, maybe, some tests are so big
Hi all:
I'm working on adding unitary test support to autovala, but have some
doubts that I want to comment here, to ensure that the implementation is
right.
The first one is how to define each unitary test; my original idea was:
one file, one test, so inside a folder called unitests will
Not exactly sure what you mean, but a very common pattern is one unit test
file for each class (unit) you want to test. This has worked fine for me in
every language I've worked with.
On Nov 17, 2014 4:07 PM, rastersoft ras...@rastersoft.com wrote:
Hi all:
I'm working on adding unitary test
I would suggest one test per file. That seems to be the most common use
case in my opinion.
I also don't see why you couldn't in theory do both. All files in the top
directory are one test per file. Anything in a sub directory is treated as
all files are compiled to a test.
On Mon, Nov 17, 2014
