pyg icon indicating copy to clipboard operation
pyg copied to clipboard

Write tests

Open rubik opened this issue 13 years ago • 8 comments

We should write some tests for Pyg. I still don't know what test suite to use, but I would suggest py.test or lettuce. I never tried lettuce but it looks interesting! We can leave this for Pyg 1.0.

rubik avatar May 23 '11 14:05 rubik

We may have a list of options 100% covered for next version, then we will add less critic feature tests, don't you think ?

fdev31 avatar Jul 05 '11 00:07 fdev31

Yes, such as installing, removing, upgrading, requirement files, searching, and bundles. I think these are the most important features, aren't they?

rubik avatar Jul 05 '11 06:07 rubik

About the tests, I think we need to focus on the "test bed" first, making tests fast with "fake" packages in fake pypi server OR use a real http_proxy. In all cases, we will probably need "100% controled" packages to test if they are running fine or not. For instance, a test could do a pyg pack then expect some output calling run_pyg.py -h, things like that... but for other packages it may require some maintenance... what do you think ?

fdev31 avatar Jul 27 '11 12:07 fdev31

It is an interesting idea! :) We could upload to PyPI fake packages like pyg-testegg, pyg-testsource, etc. They will have the same interface, so that we can fully test them.

rubik avatar Aug 03 '11 19:08 rubik

I like this option, sounds better than embedding controled packages :)

fdev31 avatar Aug 04 '11 07:08 fdev31

Good! I'll open a new repository, maybe pyg-testpackages (is there a better name?) with a script to automate packages creation and upload.

rubik avatar Aug 04 '11 12:08 rubik

pyg-xp-tests ? pyg-xp-testpackages ? I like the "xp", "wip", "fix", etc infix to sort the branches... don't you ?

fdev31 avatar Aug 04 '11 18:08 fdev31

I'll go for pyg-xp-testpackages (though I preferred pyg-xp-tests but it could be misleading).

rubik avatar Aug 05 '11 13:08 rubik