Nice! You using git to track your changes is super easy for me to work with. If you want to make it really easy for me and other git users, just push your active branch to public. Very easy if you register on github.
For example, assuming that you have set up a github account with your remote called 'SARG', and you have an active branch called 'gas64':
$ git push SARG gas64
This will make your changes available on github. On my end, I then do:
$ git remote add SARG https://github.com/SARG/fbc
$ git fetch SARG
$ git branch gas64 SARG/gas64
$ git checkout gas64
This allows me to compile your changes, even rebase or merge them in with other changes and test it out.
I am not sure what you are asking about the test suite. In general, you should try and run the test suite locally to ensure all the tests pass. Or if the tests don't pass, at least understand why, and you can possibly block out the failing tests with a '#if ENABLE_CHECK_BUGS' block, if it is impossible to fix the bugs.
Maybe if you have a specific question about the test suite (it requires 'make' and a few other unix-y tools like 'sed', 'xargs', etc to run) I could answer to that.