IQ.Lvbs/pytest-xdist
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Apply small review requests

Browse Source 
* Fixed typo
* Removed superfluous introduction
This commit is contained in:
Bruno Oliveira
2015-12-09 19:00:20 -02:00
parent 10bc4b6e9a
commit b29ff73781
1 changed files with 1 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
OVERVIEW.md
View File

@@ -1,15 +1,12 @@
# Overview # # Overview #
Here it is described a brief overview of xdist's internal architecture.
`xdist` works by spawning one or more **worker nodes**, which are controlled `xdist` works by spawning one or more **worker nodes**, which are controlled
by the **master node**. Each **worker node** is responsible for performing by the **master node**. Each **worker node** is responsible for performing
a full test collection and afterwards running tests as dictated by the **master node**. a full test collection and afterwards running tests as dictated by the **master node**.
The execution flow is: The execution flow is:
1. **master node** spawns one or more **worker nodes** at the begginning of 1. **master node** spawns one or more **worker nodes** at the beginning of
the test session. The communication between **master** and **worker** nodes makes use of the test session. The communication between **master** and **worker** nodes makes use of
[execnet](http://codespeak.net/execnet/) and its [gateways](http://codespeak.net/execnet/basics.html#gateways-bootstrapping-python-interpreters). [execnet](http://codespeak.net/execnet/) and its [gateways](http://codespeak.net/execnet/basics.html#gateways-bootstrapping-python-interpreters).
The actual interpreters executing the code for the **worker nodes** might The actual interpreters executing the code for the **worker nodes** might