Fix rerunning failed tests for all Doctest.
Do 'Doctest via pytest' option be available not only if a file/fun/class starts with `test_`.
Merge-request: IJ-MR-131237
Merged-by: Egor Eliseev <Egor.Eliseev@jetbrains.com>
GitOrigin-RevId: c1e1fda5f66d1e213f34a057175d8e8986a46647
Run Doctest via pytest configuration if `pytest` is installed and selected in settings
Merge-request: IJ-MR-130194
Merged-by: Egor Eliseev <Egor.Eliseev@jetbrains.com>
GitOrigin-RevId: 4c97411c3da69249e6b9ad886bcbd9a206db744b
When pytest stops with ``pytest.stop`` started test is not finished nor failed, so IJ shows it as "running". We now mark it as "ignored" explicitly.
(cherry picked from commit 83db3d319466ab25ce54bdcbff55bdc25f81d529)
IJ-MR-105333
GitOrigin-RevId: 68047929f947d9d9388389f9dddce896ce81bb72
Logic implemented in ``teamcity-messages``, see changes in diff_tools.py and pytest_plugin.py
GitOrigin-RevId: 8e9cc8cb350e33a9a1cb49ea78ed7ad29c4e1f96
With testdir fixture, pytest runs test under separate pytest (which may be inline or separate process).
Previously we monkeypatched prepareconfig not to call it twice.
But this approach fails with testdir, because same config returned twice leading to double plugin registration.
See comment in YT
GitOrigin-RevId: bd9f11a2a10900fa3c059791d7c0183a20b1ed70
- changed behaviour in safe way by introducing new method to check that particular expression does not depend
on committed PSI
GitOrigin-RevId: f5ec732613cdafdcef8a1d48eb8d04135c634047
- call `commitDocument` explicitly in cases when `calculateQuickResult` can redirect it's calculation to heavy `calculateResult`
GitOrigin-RevId: 41f0c47c57f4528d7d7a25208024ec28bb8c2e12
- removed `commitDocument` call when `isQuick` argument is passed
- pass `element` or `null` to `equalsToText` call (since there is not real need to take it for text comparison)
GitOrigin-RevId: 27c5e1a2f484fc56d41dfd210832ae94c9a9b7ab
With xdist, setupClass may be reported several times (one for each test). Next report leads to error since it is already
reported as closed.
We ignore setup methods: there is no sane place to display them in the test tree, anyway.
GitOrigin-RevId: 3c7bcf2f3942e78fcbfba5fb0cae1cbdb2c92730
Assume you have two elements with same name but in different folders.
Targets are same but resolved to different elements because of
different working directories.
We now check if configuration's target resolved to same file
before reusing it.
Any file that starts with "test_" may be used as pytest/nosetest target
regardless its content.
Unittest is skipped because of "testCaseClassRequired".
Trial is test framework for Twisted much like unittests.
It is fully supported on Leonid side, we only need to create wrappers.
There were too many places with framework naming code making
it pretty hard to support new frameworks.
It is now unified. Any service (except framework-specific) should work
via PyTestFrameworkService to obtain list of frameworks and its
When user clicks on some element PyCharm gets its qname and generates
test target based on it. But user may use file with dashes.
There is no qName in this case, but all test runners support such targets.
So we emulate it in "getEmulatedQNameParts"
