Differences between revisions 1 and 4 (spanning 3 versions)
Revision 1 as of 2011-03-21 10:09:38
Size: 107
Editor: ADijon-153-1-31-45
Comment:
Revision 4 as of 2011-03-22 20:36:00
Size: 1266
Editor: 2a01:e35:2ea4:b810:217:f2ff:fec5:3740
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
PyPi Test Server
================
= Create a server that tests uploaded packages on PyPI. =
Line 4: Line 3:
Create a server that test packages that are uploaded at PyPI == Work to be done ==
Line 6: Line 5:
XXX The work is separated into three steps:

 1. a solution capable of running scripts when an event occurs (a new release of project X is available on PyPI)
 2. a Continuous integration server able to run the testsuite for those distributions
 3. a quality mesurement tool, able to provide feedback and indicators on the code (compliance PEP8, pyflakes, potentially malicious softwares etc.)


== Resources ==

- [[http://tarekziade.wordpress.com/2010/03/21/another-gsoc-idea-a-pypi-testing-infrastructure/|2010 idea]] and [[https://bitbucket.org/mouad/pypi-testing-infrastructure-pyti/overview|code]]

- [[http://tarekziade.wordpress.com/2011/02/21/qa-portal-ideas/|2011 updated idea]]

- On this wiki: [[PyPITestingInfrastructure]]

== What do people want ==

=== What do people what to run ===

* Run quality indicators about the code
* Run quality indicators about the packaging (compat with du2 standards for instance)
* Run Test
* Run setup.

=== What do people what to know ===

* Report about the run itself (does the test pass ? does the install went well ?)
* Report about system access done (FS network)
* Report about resource used ? (bonus)

Create a server that tests uploaded packages on PyPI.

Work to be done

The work is separated into three steps:

  1. a solution capable of running scripts when an event occurs (a new release of project X is available on PyPI)
  2. a Continuous integration server able to run the testsuite for those distributions
  3. a quality mesurement tool, able to provide feedback and indicators on the code (compliance PEP8, pyflakes, potentially malicious softwares etc.)

Resources

- 2010 idea and code

- 2011 updated idea

- On this wiki: PyPITestingInfrastructure

What do people want

What do people what to run

* Run quality indicators about the code * Run quality indicators about the packaging (compat with du2 standards for instance) * Run Test * Run setup.

What do people what to know

* Report about the run itself (does the test pass ? does the install went well ?) * Report about system access done (FS network) * Report about resource used ? (bonus)

PyPiTestServer (last edited 2012-06-10 09:10:29 by techtonik)

Unable to edit the page? See the FrontPage for instructions.