search

amahabal / PySeqsee

Python framework for writing programs to solve complex problems not amenable to brute force. The architecture is a descendant of Douglas Hofstadter and Melanie Mitchell's Copycat architecture.
http://amahabal.github.com/PySeqsee/
GNU General Public License v3.0
32 stars 10 forks source link

Add the subcommand "farg test" #31

Closed amahabal closed 7 years ago

amahabal commented 7 years ago

Currently, I use nosetests, and do the following:

nosetests --pdb tests/ tests/seqsee

It would be nice to have "farg test", and best if it picked up files in the current directory instead of installed files.

superMDguy commented 7 years ago

I'll work on that.

Also, I was thinking it'd be nice to have commands that can be executed in the project directory, so typing out the name of the project isn't necessary. I'll try to get that working as well.

amahabal commented 7 years ago

Awesome, I am glad that you are here 👍

One aspect that bothered me with the tests was that it was picking up, I think, the globally installed farg modules rather than those in the current directory. This new command would help avoid that error.

While you are at it, could you also move tests from tests/seqsee to farg/apps/seqsee/tests?

On Sat, Jan 14, 2017, 6:17 AM Matthew D. notifications@github.com wrote:

I'll work on that.

Also, I was thinking it'd be nice to have commands that can be executed in the project directory, so typing out the name of the project isn't necessary. I'll try to get that working as well.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/amahabal/PySeqsee/issues/31#issuecomment-272626877, or mute the thread https://github.com/notifications/unsubscribe-auth/AADFvJMaenORv8NMNyTGZioAa7__5Wtfks5rSNkSgaJpZM4LjjVj .

superMDguy commented 7 years ago

I moved around the test folders a little bit (See commit 0bdcb53), and I was just about to add the farg test command. I just wanted to make sure I got it right. Did you want the command to execute tests in the project in the current directory (for example running nosetests --pdb ./tests), or did you want it running the tests in a specified project (like farg test seqsee)? Or, I could make both work.

amahabal commented 7 years ago

The best would be to make both work, perhaps controlled by a flag.

On Sat, Jan 14, 2017, 10:57 AM Matthew D. notifications@github.com wrote:

I moved around the test folders a little bit (See commit 0bdcb53 https://github.com/amahabal/PySeqsee/commit/0bdcb53091f1d6db498ee5e8a06efc981722e83e), and I was just about to add the farg test command. I just wanted to make sure I got it right. Did you want the command to execute tests in the project in the current directory (for example running nosetests --pdb ./tests), or did you want it running the tests in a specified project (like farg test seqsee)? Or, I could make both work.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/amahabal/PySeqsee/issues/31#issuecomment-272644994, or mute the thread https://github.com/notifications/unsubscribe-auth/AADFvEsYDMwkEOMa04xPYFqKC9ZXIrEVks5rSRqFgaJpZM4LjjVj .

amahabal commented 7 years ago

superMDguy did all the work (e.g., "farg core seqsee"), I enabled "farg test core". Closing this...