Skip to content

Commit ac68d90

Browse files
authored
New Doc: Useful Resources (#251)
* Cleaned :pypi: usage * New Doc: Useful Resources
1 parent 0b6e06c commit ac68d90

File tree

7 files changed

+24
-30
lines changed

7 files changed

+24
-30
lines changed

docs/faq.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ Integrating with Docker
140140
How do I get pytest-celery to work with Docker?
141141
-----------------------------------------------
142142

143-
**Answer:** The engine behind the plugin's docker integration is :pypi:`pytest-docker-tools`.
143+
**Answer:** The engine behind the plugin's docker integration is :pypi:`pytest-docker-tools <pytest-docker-tools>`.
144144

145145
It does not interact with Docker directly.
146146

@@ -165,7 +165,7 @@ What are the common pitfalls when integrating pytest-celery with Docker, and how
165165
To avoid these, you may:
166166

167167
1. Increase the resources available to Docker.
168-
2. Use the :pypi:`pytest-rerunfailures` pytest plugin to retry failed tests with:
168+
2. Use the :pypi:`pytest-rerunfailures <pytest-rerunfailures>` pytest plugin to retry failed tests with:
169169

170170
.. code-block:: console
171171

docs/getting-started/introduction.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -215,7 +215,7 @@ Features
215215

216216
- **Tests as first class citizens**
217217

218-
The plugin is designed to enhance testing capabilities by :ref:`first-class-citizen`.
218+
The plugin is designed to enhance testing capabilities by treating tests as first-class citizens.
219219
It uses advanced mechanisms to encapsulate the complexity of setting up a Celery environment, thus
220220
allowing the developer to focus on the test case itself and leave the hard lifting to the plugin.
221221

docs/includes/installation.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,8 @@ This command installs **pytest-celery** along with its required dependencies.
1616

1717
This will include:
1818

19-
- Latest version of :pypi:`celery`.
20-
- RabbitMQ broker via :pypi:`kombu`, installed as a dependency of Celery.
19+
- Latest version of :pypi:`celery <celery>`.
20+
- RabbitMQ broker via :pypi:`kombu <kombu>`, installed as a dependency of Celery.
2121

2222
Installing pytest-celery vendors
2323
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/userguide/advanced-installation.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -39,8 +39,8 @@ automatically add the matching components to the default setup matrix.
3939

4040
For example, let's assume you want to use the RabbitMQ/Redis combination.
4141

42-
1. For RabbitMQ we will need :pypi:`kombu`.
43-
2. For Redis we will need :pypi:`redis`.
42+
1. For RabbitMQ we will need :pypi:`kombu <kombu>`.
43+
2. For Redis we will need :pypi:`redis <redis>`.
4444

4545
To install the plugin with the RabbitMQ/Redis combination, you will need to install the following dependencies:
4646

@@ -51,7 +51,7 @@ To install the plugin with the RabbitMQ/Redis combination, you will need to inst
5151
Let's break down the command:
5252

5353
- The ``pytest-celery`` is the plugin package, it will install the plugin alongside Celery and its dependencies,including **Kombu** (if not installed already).
54-
- The ``[redis]`` is the feature flag for the Redis vendor, it will install the :pypi:`redis` package and configure the plugin to use it which will add the Redis backend and Redis broker components to the default setup matrix.
54+
- The ``[redis]`` is the feature flag for the Redis vendor, it will install the :pypi:`redis <redis>` package and configure the plugin to use it which will add the Redis backend and Redis broker components to the default setup matrix.
5555

5656
Experimental Vendors
5757
~~~~~~~~~~~~~~~~~~~~

docs/userguide/examples/hybrid_setup.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Highlights
3737

3838
1. No default components.
3939
2. Session broker and backend components.
40-
- Shared between tests, but not between :pypi:`pytest-xdist` sessions.
40+
- Shared between tests, but not between :pypi:`pytest-xdist <pytest-xdist>` sessions.
4141
- Only the workers are created again for each test case.
4242
3. Injects tasks and signal handlers modules to all workers.
4343

@@ -83,7 +83,7 @@ Take a look at the requirements file for this example:
8383
:language: text
8484
:caption: examples.hybrid_setup.requirements.txt
8585

86-
Take note the :pypi:`gevent` can be installed independently from the :pypi:`celery` package.
86+
Take note the :pypi:`gevent <gevent>` can be installed independently from the :pypi:`celery <celery>` package.
8787

8888
conftest.py
8989
~~~~~~~~~~~

docs/userguide/resources/first-class-citizen.rst

Lines changed: 0 additions & 17 deletions
This file was deleted.

docs/userguide/resources/index.rst

Lines changed: 14 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,18 @@
77
:Release: |version|
88
:Date: |today|
99

10-
.. toctree::
11-
:maxdepth: 1
10+
This section contains additional resources that may be useful when developing tests with :pypi:`pytest <pytest>`,
11+
:pypi:`pytest-celery <pytest-celery>`, and general :pypi:`celery <celery>` related testing articles, guides and tutorials.
1212

13-
first-class-citizen
13+
**You're welcome to contribute to this list!**
14+
15+
.. contents::
16+
:local:
17+
:depth: 2
18+
19+
Other Plugins
20+
~~~~~~~~~~~~~
21+
22+
- :pypi:`pytest-rerunfailures <pytest-rerunfailures>`: Do to the natural sensitivity of simulating Celery environments over Docker, it's
23+
common to have flaky tests due to failing docker resources. This plugin provide useful features to rerun failed tests, skipping tests that
24+
failed due to actual assertion errors.

0 commit comments

Comments
 (0)