[Gump-develop] How do I test?

[Steve M. <sm...@ne...>]

This is not a blocker for me but something that needs to be thought
about soon.

Procedural question:

OK... I've made some initial changes to isolate global.c, namely I
have made various functions static so they don't show up as externals
in the C symbol tables. In the process I changed one of the header
files that are used everywhere. I have also made minor changes to get
rid of some gcc warnings (declared main to return int as it should
etc.) Now I have something that should be functionally identical to
where I started almost to the point of matching byte by byte in the
executable. I have more work to do (external functions and global
data) but this is a nice break and normally I would be looking to do a
little testing and then checkin what I've done before moving forward.

So what is the drill for testing? I do a make and get lots of errors:

/bin/sh: ../exec_qa: not found

What is this telling me? Is it attempting to run our test suite? Is
there a different test suite that I should be running.

I am used to, when there is a shared but relatively stable repository,
that there is a minimum test suite requirement before people are
allowed to commit. (This is frequently called the checkin test suite.)
Is the one in the makefile (but broken) the correct one to use for
this?