Repository navigation
Rewrite testing adapter #17242
Copy link
Copy link
Closed
Labels
area-testingfeature-requestRequest for new features or functionalityRequest for new features or functionalitymetaIssue that is tracking an overall projectIssue that is tracking an overall projectneeds PRReady to be worked onReady to be worked on
Description
Meta-issue: #16936
Unittest
- Test discovery with unittest - Unittest discovery using the new test adapter #18253
- Test execution with unittest - Refactor unittest test execution #19098
- Test debugging with unittest
Pytest
- Prototyping pytest plugin Prototype
pytestplugin for test discovery/execution. #19790 - Add pytest plugin Review and Commit Pytest Plugin (without enabling) #20077
- Test discovery with pytest
- Write discovery logic for pytest plugin Finalize Pytest Discovery Logic #20078
- Display discovered test on UI Connect Pytest Discovery Plugin to Testing UI #20079
- Test execution with pytest
- Create pytest run tests call Create Pytest Plugin Call for Run Test #20080
- Write run tests plugin logic Pytest Run Tests Logic #20081
- Display run test info on UI Surface Test Results to UI #20082
- Pytest error handling Error Handling Pytest Discovery #20083
- Complete pytest testing suite Write testing for pytest discovery #20085
- Enable pytest rewrite to users Enable Pytest Rewrite to Users #20086
- Test debugging with pytest
Cleanup
- Clean up unittest-related issues
- Clean up pytest-related issues
- Make sure there are tests for the test controller after the rewrite
Notes
Public issues
- python.testing.cwd ignored when discovering or running tests #8678
- Tests not discovered, but running tests anyway works fine. #16565
- Handle exclude lists in a test run request #16929
- Go to Test doesn't work for test class items in Test Explorer #17107
- Tests are discovered correctly but then an incorrect argument is supplied to PyTest, leading test-result discovery to fail (Git Submodules?) #17903
- Unittest discovery not working when sys.stdout is set in global scope #17957
Issues we expect this rewrite will fix
- Problem with test IDs
- Problems with other plugins or python or libs printing to output
- Problems with test discovery
- pytest discovery error #19809
- Improve python test discovery error reporting #19978
- Group test explorer test by workspace in multi-root workspace #20345
- unexpected situation while processing a pytest node during test discovery #19804
- Test discovery should be fault tolerant and display all successfully imported files #13301
- Problems with testing output
- Problems with remote setups
- Problems with testing args
- Performance Concerns
- Problems with Running Tests
pytest feedback on how to things the "right way"
- What is the preferred way for editors/tools to interact with pytest? pytest-dev/pytest#8458
- What is the minimum amount of pytest's CLI that should be supported by integrating editors? pytest-dev/pytest#8506
- visualstudio_py_testlauncher.py - format_exception() missing 3 required positional arguments: 'etype', 'value', and 'tb' #3305
- Red test failure output in editor gets wrapped over lines #18047
unittest missing features
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area-testingfeature-requestRequest for new features or functionalityRequest for new features or functionalitymetaIssue that is tracking an overall projectIssue that is tracking an overall projectneeds PRReady to be worked onReady to be worked on
Activity
Bilalh commentedon Sep 25, 2021
It would be nice if other python testing frameworks such as behave (a BDD framework) https://behave.readthedocs.io/en/stable/index.html were supported by the testing adapter.
kimadeline commentedon Sep 27, 2021
Hi Bilal Syed Hussain (@Bilalh), support for
behaveis not within scope of this issue. Feel free to open a feature request on the repo and we'll take a look at it. Thanks!55 remaining items
JensMadsen commentedon Aug 21, 2024
Eleanor Boyd (@eleanorjboyd) I have enabled the pythonTestAdapter. I still see that the startup time is very long. I use unittest. When I run a single unit test stuff related to tests elsewhere (e.g. other folders) is initialized. Example: I run a straightforward test that tests some simple string gymnastics. Before the test starts I see in the output terminal that e.g. Pytorch is imported which takes a long time.
Please let me know if I can help in any way debugging this :-)
eleanorjboyd commentedon Aug 21, 2024
Hi Jens Madsen (@JensMadsen)! Could you open a new issue and include some of these logs? From there I can help you out a bit more- thanks!
JensMadsen commentedon Aug 22, 2024
Eleanor Boyd (@eleanorjboyd) I will do that but I am unsure what logs you refer to.
eleanorjboyd commentedon Aug 28, 2024
If you go to the command palette and look for the command-
python: report issue...that is the best way submit all the logs and info to us as a new issue so I can take a look. Hopefully that would work- thanks!JensMadsen commentedon Aug 29, 2024
Eleanor Boyd (@eleanorjboyd) done #24022
ssbarnea commentedon Dec 3, 2024
Apparently vscode complains about not being able to activate the experimental feature when configuring at folder level.... and guess what, most people use multi-root workspaces.
eleanorjboyd commentedon Dec 4, 2024
Sorin Sbarnea (@ssbarnea) would it work to put it in your user settings or is there a use-case where that isn't functional?
remove pre-rewrite testing code (microsoft#24568)