Tests |
|
Downloads |
|
About |
|
Status |
|
Parallelizes test executions.
It allows to parallelize the integration/acceptance tests execution in different environments. This way they will took much less time to finish.
And it is based on plugins in order to support different languages or platforms.
ParaTest can be run under any Continuous Integration Server, like Jenkins, TeamCity, Go-CD, Bamboo, etc.
Why Paratest?
Almost all test runners allow you to paralellize the test execution, so… why Paratest?
Well… In some cases test execution cannot be parallelized because of depenencies: database access, legacy code, file creation, etc. Then, you need to create a full workspace whenever you want to test them.
This may be a hard task, and sadly Paratest cannot help there.
But with some scripts to clone an existent workspace, Paratest can divide the tests between any number of workspaces, creating them on demand, and running the tests on them. Resources put the limits.
Another advantage of Paratest is the test order: Paratest remembers the time spent in each test and will reorder them to get the most of your infrastructure.
And finally, Paratest can retry failed tests, in order to avoid unstable tests.
Usage
First of all, you need two things:
a source. This means to have a source with instructions to create a workspace
some scripts to setup/teardown the workspaces. This should translate the source into a workspace.
Then, Paratest will call the setup scripts in order to create the workspaces and will parallelize the test run between them.
Current plugins
ParaTest is in an early development stage and it still have no plugins to work. It is just a proof of concept.
Contribute
Plugins
Writting a plugin is quite easy. You can see the paratest-dummy as example. Just two steps are required:
Write the plugin methods
Currently, just one method is required:
def find(path, test_pattern, file_pattern, output_path)
It should return a dict or a generator for tuples.
Register the entrypoint
The second step is to create a pip package with the entrypoint find within the group paratest. This should be done in the setup.py file. Example:
from setuptools import setup, find_packages
setup(
name='whatever',
version='0.0.1',
entry_points={
'paratest': 'find = whatever:find'
}
)1 maintainer
Metadata
1 maintainer
Release files for paratest 2.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| paratest-2.1.2.tar.gz | 9.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| paratest-2.1.2-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 24.9 kB
Release files / paratest-2.1.2.tar.gz
| Download URL | paratest-2.1.2.tar.gz |
|---|---|
| Size | 9.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e8dda54fd4dc540959e32d92bcdae13a2f8368a34ae9868fdac519f67dd2e2a
|
|
BLAKE2b-256 checksum How to use checksums |
d18ef049cb8816b6e94e816bf99036d9abb078260f7d8e4f60122d99c9ea201f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / paratest-2.1.2-py2.py3-none-any.whl
| Download URL | paratest-2.1.2-py2.py3-none-any.whl |
|---|---|
| Size | 15.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
bf17e220145a3fb35e81a68d59e7219680811fc6d8c6df0f4b920bbde2739421
|
|
BLAKE2b-256 checksum How to use checksums |
4ec806f7bbfcbc673e8f5d9b588492936cee7eca267108acb488ab37c3929003
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for paratest 2.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
