This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients alexis, eric.araujo, francismb, python-dev, shane.moore, tarek
Date 2012-02-27.11:22:08
SpamBayes Score 1.2945323e-09
Marked as misclassified No
Message-id <1330341730.18.0.549794058583.issue14140@psf.upfronthosting.co.za>
In-reply-to
Content
Many packaging tests use functions like os.mkdir and open to create files in order to test commands or actions, or slightly higher-level helpers like packaging.tests.support.TempdirManager.write_file.

I think this could be much more automated.  There should be an helper function which could accept a string with a custom format describing directories, files and their contents, then create the files in a temp directory and later cleans it all.  Likewise, it should be easier to check what new files are created (i.e. in the build or dist directory) and what their contents are.

My ultimate goal is to move from low-level tests which use command objects directly to higher-level tests which actually run the pysetup script and check the results, so that tests get closer to what people do.  This will also remove cruft in the tests, and let us change details more easily (because we’ll be testing behavior, not internal attributes or exact output).
History
Date User Action Args
2012-02-27 11:22:10eric.araujosetrecipients: + eric.araujo, tarek, alexis, python-dev, francismb, shane.moore
2012-02-27 11:22:10eric.araujosetmessageid: <1330341730.18.0.549794058583.issue14140@psf.upfronthosting.co.za>
2012-02-27 11:22:09eric.araujolinkissue14140 messages
2012-02-27 11:22:09eric.araujocreate