[tahoe-lafs-trac-stream] [tahoe-lafs] #2049: Decide where "packaging tests" should live.

[tahoe-lafs]

#2049: Decide where "packaging tests" should live.
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  daira
  nejucomo               |     Status:  new
         Type:  task     |  Milestone:  undecided
     Priority:  normal   |    Version:  1.10.0
    Component:  unknown  |   Keywords:  packaging dev-infrastructure
   Resolution:           |  buildbot pypi
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by nejucomo):

 Note: We might have some tests that are abstracted over the target
 package.  For example a distribution test which takes as input a PyPI
 package named $PKG:

  1. Create a new pristine virtualenv; activate it.
  1. $ pip install $pkg
  1. Fail if the installation fails.
  1. Fail if `http` connections were attempted without `ssl`.
  1. Run the installed packages unit tests; fail if they fail.
  1. Otherwise, pass.

 If this were adopted as a packaging goal/specification, we could apply it
 to `allmydata-tahoe`, `zfec`, `pyutil`, `pycryptopp`, etc...

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2049#comment:1>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage