Re: EDE documentation

On 08/09/2015 11:22 AM, Stephen Leake wrote:
>>> >>      In addition, there's a problem with the Arduino auto-detect on
>>> >>      Windows; the sketchbook directory has \ in preferences.txt, but it
>>> >>      is compared to buffer-file-name, which has /. So ede/auto.el
>>> >>      ede-do-dirmatch needs an 'expand-file-name' in (setq matchstring
>>> >>      ...). I didn't actually edit the code and test, because I'm not sure
>>> >>      that change is ok in general.
>> >
>> >Expanding the file seams reasonable since most tests are just
>> >(file-exists-p) which is vaguely similar.
>> >
>> >I did this and it passed all my tests on Linux.
> Ok. I'll see if I can run tests on Windows.
>
> How do you run the tests?
>
> 'make test' in cedet/Makefile says "no target test". Same for "tests".
> There are a couple utest-* and several itest-*; do you just run each?
>
> Ah; there's a tests/Makefile with an 'all' target. That gives an error
> for recursive require for speedbar. Maybe I need to pull.

At the top level:

make utest-batch

runs the a set of unit tests, basically testing all the APIs.

make itest-batch

runs all the interactive tests, and is quite time consuming.  It 
programatically runs the interactive commands in EDE, such as adding 
files to targets, and creating projects.

Together they run almost everything.

Eric




------------------------------------------------------------------------------