[Pytest-commit] commit/pytest: 3 new changesets
commits-noreply at bitbucket.org
commits-noreply at bitbucket.org
Fri Jul 26 08:59:15 CEST 2013
3 new commits in pytest:
https://bitbucket.org/hpk42/pytest/commits/1fdb76c818cc/
Changeset: 1fdb76c818cc
Branch: tox_reference
User: Anthon van der Neut
Date: 2013-07-26 08:14:49
Summary: updated tox to live on testrun.org (the old links are still
working on codespeak.net, but those docs are outdated)
Affected #: 3 files
diff -r abfc7dc64ed4f5a50e917ac8a30863be7e2361a7 -r 1fdb76c818cced9375ca593369558ac764280be1 doc/en/goodpractises.txt
--- a/doc/en/goodpractises.txt
+++ b/doc/en/goodpractises.txt
@@ -23,7 +23,7 @@
If you frequently release code to the public you
may want to look into `tox`_, the virtualenv test automation
-tool and its `pytest support <http://codespeak.net/tox/example/pytest.html>`_.
+tool and its `pytest support <http://testrun.org/tox/latest/example/pytest.html>`_.
The basic idea is to generate a JUnitXML file through the ``--junitxml=PATH`` option and have a continuous integration server like Jenkins_ pick it up
and generate reports.
diff -r abfc7dc64ed4f5a50e917ac8a30863be7e2361a7 -r 1fdb76c818cced9375ca593369558ac764280be1 doc/en/links.inc
--- a/doc/en/links.inc
+++ b/doc/en/links.inc
@@ -17,5 +17,5 @@
.. _`virtualenv`: http://pypi.python.org/pypi/virtualenv
.. _hudson: http://hudson-ci.org/
.. _jenkins: http://jenkins-ci.org/
-.. _tox: http://codespeak.net/tox
+.. _tox: http://testrun.org/tox
.. _pylib: http://pylib.org
diff -r abfc7dc64ed4f5a50e917ac8a30863be7e2361a7 -r 1fdb76c818cced9375ca593369558ac764280be1 doc/en/projects.txt
--- a/doc/en/projects.txt
+++ b/doc/en/projects.txt
@@ -26,7 +26,7 @@
`16000 tests <http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E>`_
* the `MoinMoin <http://moinmo.in>`_ Wiki Engine
* `sentry <https://getsentry.com/welcome/>`_, realtime app-maintenance and exception tracking
-* `tox <http://codespeak.net/tox>`_, virtualenv/Hudson integration tool
+* `tox <http://testrun.org/tox>`_, virtualenv/Hudson integration tool
* `PIDA <http://pida.co.uk>`_ framework for integrated development
* `PyPM <http://code.activestate.com/pypm/>`_ ActiveState's package manager
* `Fom <http://packages.python.org/Fom/>`_ a fluid object mapper for FluidDB
https://bitbucket.org/hpk42/pytest/commits/40a882235eae/
Changeset: 40a882235eae
Branch: tox_reference
User: Anthon van der Neut
Date: 2013-07-26 08:20:26
Summary: also update testrun.org in 日本語
Affected #: 3 files
diff -r 1fdb76c818cced9375ca593369558ac764280be1 -r 40a882235eaeb6553941602db8bd3bf1222eb876 doc/ja/goodpractises.txt
--- a/doc/ja/goodpractises.txt
+++ b/doc/ja/goodpractises.txt
@@ -39,11 +39,11 @@
..
If you frequently release code to the public you
may want to look into `tox`_, the virtualenv test automation
- tool and its `pytest support <http://codespeak.net/tox/example/pytest.html>`_.
+ tool and its `pytest support <http://testrun.org/tox/latest/example/pytest.html>`_.
The basic idea is to generate a JUnitXML file through the ``--junitxml=PATH`` option and have a continuous integration server like Jenkins_ pick it up
and generate reports.
-もし頻繁にコードを一般向けにリリースするなら、virtualenv のテスト自動化とその `pytest サポート <http://codespeak.net/tox/example/pytest.html>`_ を行う `tox`_ を調べてみたくなるでしょう。基本的な考え方は、 ``--junitxml=PATH`` オプションにより JUnitXML ファイルを生成します。そして Jenkins_ のような継続的インテグレーションサーバーがそのファイルを取得してレポートを生成します。
+もし頻繁にコードを一般向けにリリースするなら、virtualenv のテスト自動化とその `pytest サポート <http://testrun.org/tox/latest/example/pytest.html>`_ を行う `tox`_ を調べてみたくなるでしょう。基本的な考え方は、 ``--junitxml=PATH`` オプションにより JUnitXML ファイルを生成します。そして Jenkins_ のような継続的インテグレーションサーバーがそのファイルを取得してレポートを生成します。
.. _standalone:
.. _`genscript method`:
diff -r 1fdb76c818cced9375ca593369558ac764280be1 -r 40a882235eaeb6553941602db8bd3bf1222eb876 doc/ja/links.inc
--- a/doc/ja/links.inc
+++ b/doc/ja/links.inc
@@ -17,4 +17,4 @@
.. _`virtualenv`: http://pypi.python.org/pypi/virtualenv
.. _hudson: http://hudson-ci.org/
.. _jenkins: http://jenkins-ci.org/
-.. _tox: http://codespeak.net/tox
+.. _tox: http://testrun.org/tox
diff -r 1fdb76c818cced9375ca593369558ac764280be1 -r 40a882235eaeb6553941602db8bd3bf1222eb876 doc/ja/projects.txt
--- a/doc/ja/projects.txt
+++ b/doc/ja/projects.txt
@@ -16,7 +16,7 @@
* `PyPy <http://pypy.org>`_, Python with a JIT compiler, running over
`16000 tests <http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E>`_
* the `MoinMoin <http://moinmo.in>`_ Wiki Engine
- * `tox <http://codespeak.net/tox>`_, virtualenv/Hudson integration tool
+ * `tox <http://testrun.org/tox>`_, virtualenv/Hudson integration tool
* `PIDA <http://pida.co.uk>`_ framework for integrated development
* `PyPM <http://code.activestate.com/pypm/>`_ ActiveState's package manager
* `Fom <http://packages.python.org/Fom/>`_ a fluid object mapper for FluidDB
@@ -49,7 +49,7 @@
* `PyPy <http://pypy.org>`_: JIT コンパイラーを備えた Python、 `16000 テスト <http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E>`_ 以上を実行
* `MoinMoin <http://moinmo.in>`_: Wiki エンジン
-* `tox <http://codespeak.net/tox>`_: virtualenv/Jenkins インテグレーションツール
+* `tox <http://testrun.org/tox>`_: virtualenv/Jenkins インテグレーションツール
* `PIDA <http://pida.co.uk>`_: 統合開発フレームワーク
* `PyPM <http://code.activestate.com/pypm/>`_: Activestate 社のパッケージマネージャー
* `Fom <http://packages.python.org/Fom/>`_: FluidDB の fluid オブジェクトマッパー
https://bitbucket.org/hpk42/pytest/commits/e45e0210341c/
Changeset: e45e0210341c
User: hpk42
Date: 2013-07-26 08:59:12
Summary: Merged in anthon_van_der_neut/pytest/tox_reference (pull request #47)
update for links to tox
Affected #: 6 files
diff -r 4405d5fd6caec4072177911d9af4e1c57fe66cec -r e45e0210341cfc1bacfe27c3edf92079c3d40d4b doc/en/goodpractises.txt
--- a/doc/en/goodpractises.txt
+++ b/doc/en/goodpractises.txt
@@ -23,7 +23,7 @@
If you frequently release code to the public you
may want to look into `tox`_, the virtualenv test automation
-tool and its `pytest support <http://codespeak.net/tox/example/pytest.html>`_.
+tool and its `pytest support <http://testrun.org/tox/latest/example/pytest.html>`_.
The basic idea is to generate a JUnitXML file through the ``--junitxml=PATH`` option and have a continuous integration server like Jenkins_ pick it up
and generate reports.
diff -r 4405d5fd6caec4072177911d9af4e1c57fe66cec -r e45e0210341cfc1bacfe27c3edf92079c3d40d4b doc/en/links.inc
--- a/doc/en/links.inc
+++ b/doc/en/links.inc
@@ -17,5 +17,5 @@
.. _`virtualenv`: http://pypi.python.org/pypi/virtualenv
.. _hudson: http://hudson-ci.org/
.. _jenkins: http://jenkins-ci.org/
-.. _tox: http://codespeak.net/tox
+.. _tox: http://testrun.org/tox
.. _pylib: http://pylib.org
diff -r 4405d5fd6caec4072177911d9af4e1c57fe66cec -r e45e0210341cfc1bacfe27c3edf92079c3d40d4b doc/en/projects.txt
--- a/doc/en/projects.txt
+++ b/doc/en/projects.txt
@@ -26,7 +26,7 @@
`16000 tests <http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E>`_
* the `MoinMoin <http://moinmo.in>`_ Wiki Engine
* `sentry <https://getsentry.com/welcome/>`_, realtime app-maintenance and exception tracking
-* `tox <http://codespeak.net/tox>`_, virtualenv/Hudson integration tool
+* `tox <http://testrun.org/tox>`_, virtualenv/Hudson integration tool
* `PIDA <http://pida.co.uk>`_ framework for integrated development
* `PyPM <http://code.activestate.com/pypm/>`_ ActiveState's package manager
* `Fom <http://packages.python.org/Fom/>`_ a fluid object mapper for FluidDB
diff -r 4405d5fd6caec4072177911d9af4e1c57fe66cec -r e45e0210341cfc1bacfe27c3edf92079c3d40d4b doc/ja/goodpractises.txt
--- a/doc/ja/goodpractises.txt
+++ b/doc/ja/goodpractises.txt
@@ -39,11 +39,11 @@
..
If you frequently release code to the public you
may want to look into `tox`_, the virtualenv test automation
- tool and its `pytest support <http://codespeak.net/tox/example/pytest.html>`_.
+ tool and its `pytest support <http://testrun.org/tox/latest/example/pytest.html>`_.
The basic idea is to generate a JUnitXML file through the ``--junitxml=PATH`` option and have a continuous integration server like Jenkins_ pick it up
and generate reports.
-もし頻繁にコードを一般向けにリリースするなら、virtualenv のテスト自動化とその `pytest サポート <http://codespeak.net/tox/example/pytest.html>`_ を行う `tox`_ を調べてみたくなるでしょう。基本的な考え方は、 ``--junitxml=PATH`` オプションにより JUnitXML ファイルを生成します。そして Jenkins_ のような継続的インテグレーションサーバーがそのファイルを取得してレポートを生成します。
+もし頻繁にコードを一般向けにリリースするなら、virtualenv のテスト自動化とその `pytest サポート <http://testrun.org/tox/latest/example/pytest.html>`_ を行う `tox`_ を調べてみたくなるでしょう。基本的な考え方は、 ``--junitxml=PATH`` オプションにより JUnitXML ファイルを生成します。そして Jenkins_ のような継続的インテグレーションサーバーがそのファイルを取得してレポートを生成します。
.. _standalone:
.. _`genscript method`:
diff -r 4405d5fd6caec4072177911d9af4e1c57fe66cec -r e45e0210341cfc1bacfe27c3edf92079c3d40d4b doc/ja/links.inc
--- a/doc/ja/links.inc
+++ b/doc/ja/links.inc
@@ -17,4 +17,4 @@
.. _`virtualenv`: http://pypi.python.org/pypi/virtualenv
.. _hudson: http://hudson-ci.org/
.. _jenkins: http://jenkins-ci.org/
-.. _tox: http://codespeak.net/tox
+.. _tox: http://testrun.org/tox
diff -r 4405d5fd6caec4072177911d9af4e1c57fe66cec -r e45e0210341cfc1bacfe27c3edf92079c3d40d4b doc/ja/projects.txt
--- a/doc/ja/projects.txt
+++ b/doc/ja/projects.txt
@@ -16,7 +16,7 @@
* `PyPy <http://pypy.org>`_, Python with a JIT compiler, running over
`16000 tests <http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E>`_
* the `MoinMoin <http://moinmo.in>`_ Wiki Engine
- * `tox <http://codespeak.net/tox>`_, virtualenv/Hudson integration tool
+ * `tox <http://testrun.org/tox>`_, virtualenv/Hudson integration tool
* `PIDA <http://pida.co.uk>`_ framework for integrated development
* `PyPM <http://code.activestate.com/pypm/>`_ ActiveState's package manager
* `Fom <http://packages.python.org/Fom/>`_ a fluid object mapper for FluidDB
@@ -49,7 +49,7 @@
* `PyPy <http://pypy.org>`_: JIT コンパイラーを備えた Python、 `16000 テスト <http://buildbot.pypy.org/summary?branch=%3Ctrunk%3E>`_ 以上を実行
* `MoinMoin <http://moinmo.in>`_: Wiki エンジン
-* `tox <http://codespeak.net/tox>`_: virtualenv/Jenkins インテグレーションツール
+* `tox <http://testrun.org/tox>`_: virtualenv/Jenkins インテグレーションツール
* `PIDA <http://pida.co.uk>`_: 統合開発フレームワーク
* `PyPM <http://code.activestate.com/pypm/>`_: Activestate 社のパッケージマネージャー
* `Fom <http://packages.python.org/Fom/>`_: FluidDB の fluid オブジェクトマッパー
Repository URL: https://bitbucket.org/hpk42/pytest/
--
This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.
More information about the pytest-commit
mailing list