Pycrunch-engine

Latest version: v1.6.4

Safety actively analyzes 629959 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 3

0.7.2

Previously exception was raised when a file is deleted from project folder.

This was caused due to my switch to asyncio, and usually not happening during usage scenarios with adding\modification.

Now the issue is fixed.

0.7.1

Small fix to address false positive during failure in one of parametrized test

See https://github.com/gleb-sevruk/pycrunch-engine/issues/4 for details

0.7.0

following configuration parameters added into .pycrunch-config.yaml:
* `cpu-cores` - How many processes to use for test execution. (More processes != faster times)
* `multiprocessing-threshold` default is `5` - Try to not pipeline 5 or less tests into multiple processes. Use single executor instead. 6 or more tests will be split intelligently across your `cpu-cores`


engine:
runtime: pytest
maximum number of concurrent test runners
cpu-cores: 4
minimum number of tests to schedule per core (5 by default; if set to 1 - run each test in own process)
multiprocessing-threshold: 4



Some statistics (Intel i7 7700k 4-cores with multithreading enabled):

Total tests to run: 67

1 CPU
run tests - Duration - 7.775 seconds

2 CPU
run tests - Duration - 5.628 seconds

3 CPU
run tests - Duration - 3.709 seconds

4 CPU
run tests - Duration - 3.405 seconds
run tests - Duration - 3.37 seconds

5 CPU
run tests - Duration - 3.415 seconds

8 CPU
no improvement at that point...
run tests - Duration - 3.451 seconds

50 CPU
run tests - Duration - 10.258 seconds

0.6.1

* Rewritten communication protocols to use WebSockets only.
* Get fid of flask dependency
* Now engine will use aiohttp server instead of flask. (if you use aiohttp in your project, maybe it can conflict somehow, but this is no longer flask)
* Included web-ui into the pip bundle
* Web Ui will show more detailed timings statistics

* Improves Dark Theme in Pycharm

0.5.1

Adding test file previously didn't add this file to watch queue, therefore all new tests in that file were not visible until engine restart. This is fixed.

v_05

Page 3 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.