[schemepy] Migration from py.test to nose
Chiyuan Zhang pluskid at gmail.comThu May 15 06:12:38 EDT 2008
- Previous message: [schemepy] Migration from py.test to nose
- Next message: [schemepy] Continuation in Schemepy
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, May 15, 2008 at 1:39 PM, Tim Ansell <mithro at mithis.com> wrote: > On Mon, 2008-05-12 at 14:35 +0800, Chiyuan Zhang wrote: >> Hi, >> >> I migrated the test cases from py.test to nose. I suppose you've already >> known nose before, if you don't, just run >> >> easy_install nose >> >> to get it and run `nosetests' to run the testcases. also, the default >> target of the top-level Makefile runs the testcases against the guile >> backend. >> >> nose is very similar to py.test, so the migration is almost trivial. I >> renamed the environment from MODULE to BACKEND. I also renamed those >> methods like passthru_test to check_passthru because I (and nose) am >> confused by whether xxx_test or test_xxx should be run as the test method. >> >> In fact, I don't like py.test. The output is sometimes too clean but >> sometimes too verbose. Until today it just fails silently on the >> multi_vm testcase. I don't know what's wrong, I guess there are some >> bugs in the vm, but when I added the verbose option, it runs perfectly. >> However, I think I also need more consideration on this -- it may be >> a very bad bug that is hard to find. > > This seems all pretty reasonable. Nose even has a deb package, you can > do an "apt-get install python-nose" on debian systems. > >> Back to the test case. I arranged those existing test cases for schemepy >> to the schemepy sub-directory. They'll be test suites for the interface. >> I'll start to borrow test cases from PyPy Scheme. And most of the test >> cases of pyscheme is merely Scheme code. They'll be put in the sub-directory >> scheme. > > How is this going? I only converted PyPy Scheme's test case currently. Most of the test cases of PyPy Scheme is in test_eval.py. It is converted to the Schemepy interface and passed with the guile backend. However, I have problem with the continuation test case, so that is not included yet. I'm currently working on porting pyscheme to schemepy's interface. As soon as this is finished, I can port pyscheme's test cases too. > > I see that you have two directories now, they are > test_scheme > test_schemepy > > Can you add to the README what the various directories mean? Some better > documentation about what you are actually testing (IE This file tests > the conversion to the conversion to schemepy.cons class) in each file > would be good too. OK. That's a good idea. > > Tim 'Mithro' Ansell > > _______________________________________________ > schemepy mailing list > schemepy at thousandparsec.net > http://mail.thousandparsec.net/tp/mailman.php/listinfo/schemepy > -- pluskid
- Previous message: [schemepy] Migration from py.test to nose
- Next message: [schemepy] Continuation in Schemepy
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the schemepy mailing list
