This is a continuous test runner plugin for PyCharm.
It tracks which tests are affected by code change and automatically runs only impacted tests. (Similar to NCrunch for .Net)
What's the difference between this Python project and similar ones?
What covers what - Opposite to simple line coverage, PyCrunch tracks and records coverage for each test individually.
Coverage markers are added to the editor gutter. Clicking on the coverage marker to overview the tests that are potentially failing on the current line.
Engine keeps track of dependencies between code and tests - this allows to run only impacted tests.
Can be used as a drop-in replacement for Django test command. (Also it will not recreate database to further speed up test execution)
Faster execution - tests will run using multiple processes by default.
No need to switch context during writing code. Tests will rerun after saving file and shows coverage immediately
Anyone who agrees with this pull request could submit an Approve review to it.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/vinta/awesome-python/pull/1572
**Author:** [@gleb-sevruk](https://github.com/gleb-sevruk)
**Created:** 7/9/2020
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `added-pycrunch-v2`
---
### 📝 Commits (1)
- [`2ec7bc4`](https://github.com/vinta/awesome-python/commit/2ec7bc4638bc4a87c4ac7548c1a2d5bc8f9425ce) Added pycrunch
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
## What is this Python project?
This is a continuous test runner plugin for PyCharm.
It tracks which tests are affected by code change and automatically runs only impacted tests. (Similar to NCrunch for .Net)
## What's the difference between this Python project and similar ones?
What covers what - Opposite to simple line coverage, PyCrunch tracks and records coverage for each test individually.
Coverage markers are added to the editor gutter. Clicking on the coverage marker to overview the tests that are potentially failing on the current line.
Engine keeps track of dependencies between code and tests - this allows to run only impacted tests.
Can be used as a drop-in replacement for Django test command. (Also it will not recreate database to further speed up test execution)
Faster execution - tests will run using multiple processes by default.
No need to switch context during writing code. Tests will rerun after saving file and shows coverage immediately
More info and documentation: https://pycrunch.com/
--
Anyone who agrees with this pull request could submit an *Approve* review to it.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/vinta/awesome-python/pull/1572
Author: @gleb-sevruk
Created: 7/9/2020
Status: ❌ Closed
Base:
master← Head:added-pycrunch-v2📝 Commits (1)
2ec7bc4Added pycrunch📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
What is this Python project?
This is a continuous test runner plugin for PyCharm.
It tracks which tests are affected by code change and automatically runs only impacted tests. (Similar to NCrunch for .Net)
What's the difference between this Python project and similar ones?
What covers what - Opposite to simple line coverage, PyCrunch tracks and records coverage for each test individually.
Coverage markers are added to the editor gutter. Clicking on the coverage marker to overview the tests that are potentially failing on the current line.
Engine keeps track of dependencies between code and tests - this allows to run only impacted tests.
Can be used as a drop-in replacement for Django test command. (Also it will not recreate database to further speed up test execution)
Faster execution - tests will run using multiple processes by default.
No need to switch context during writing code. Tests will rerun after saving file and shows coverage immediately
More info and documentation: https://pycrunch.com/
--
Anyone who agrees with this pull request could submit an Approve review to it.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.