Okay, here are a couple questions,
Q1. Are you interested in bug reports at your github?
Q2. Do you mind contributions from others?
Q2. a. Even from individuals who are obviously less capable programmers than yourself? It might require some patience on your part, especially in the beginning.
Q3. I might want to add some features that some may think is really goofy (like play sounds when trades execute),

let's say I make some changes to stragegy.py, and I want to test them. We can consider several testing strategies

• Test on historical data from mtgox.
  
  • interesting since goxtool grabs this data when it connects, and because this data is real, and relevant to current mkt conditions
  • bad because it's not a controlled test, and therefore difficult to compare strategies
  • dangerous since we're connected to a live account. Maybe we should make for ourselves different API access for testing vs trading

• Test on fake data we make ourselves. This could be:
  
  • Old data we've saved
  • Data collected from other exchanges
  • Fake sample data sets.

There is also various levels of diligence to consider,

• simply iterate over the data?
• iterate, and try to account for realistic mkt timings, liquidity, etc.

Do you think it would be easier to write a new program for testing that imports some strategy.py, or add testing functionality to goxtool?
Is that a feature that you might be personally interested in, or would consider adding to the codebase?