Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TPI: fifo test communication (unittest) #24506

Closed
3 tasks done
eleanorjboyd opened this issue Dec 2, 2024 · 3 comments
Closed
3 tasks done

TPI: fifo test communication (unittest) #24506

eleanorjboyd opened this issue Dec 2, 2024 · 3 comments
Assignees
Milestone

Comments

@eleanorjboyd
Copy link
Member

eleanorjboyd commented Dec 2, 2024

Refs: 23279

Complexity: 5

Author: @eleanorjboyd

Create Issue


  1. Setup:

    1. Clone the test repo from here or use your own repo of pytests.
    2. Launch VSCode and open the python-ext-tester/python-testing/inc-dec-workspace folder.
    3. Add the following to your settings in VSCode: "python.experiments.optInto": ["pythonTestAdapter"],
    4. Use the "create environment" command from the command palette, select venv and a Python version >=3.7.
    5. click the test explorer icon (beaker)
    6. configure tests
      1. unittest: unittest → root → *test*.py
  2. Testing:

    1. Now play around with running the tests attempting to put "strain" on the testing flow to make sure it works as anticipated
    2. Ideas of what to do include:
      1. Run large number of tests and make sure it finishes successfully (see the subtests or the parameterized tests which should have 2000 tests that can be run)
      2. stop tests and restart them (NOTE: there is a know problem where if you restart a test 3 times during debugging it will freeze the window, see issue please comment on the issue if you hit something similar and your repro steps)
      3. debug tests, put break-points on and generally just start, restart, and stop tests in debug mode
      4. throw an error in a test or spin up a subprocess as part of a test
@eleanorjboyd eleanorjboyd added the feature-request Request for new features or functionality label Dec 2, 2024
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Dec 2, 2024
@eleanorjboyd eleanorjboyd added testplan-item and removed feature-request Request for new features or functionality triage-needed Needs assignment to the proper sub-team labels Dec 2, 2024
@eleanorjboyd eleanorjboyd added this to the November 2024 milestone Dec 2, 2024
@aiday-mar
Copy link

aiday-mar commented Dec 3, 2024

Note for testers: I had the error no module named pytest so I ran pip install pytest during the configuration

I assume the parameterized tests are those under the category NumbersTest

@karthiknadig
Copy link
Member

Ran into the exact same issues as Aiday.

@joshspicer
Copy link
Member

Chatted with @eleanorjboyd and it was also necessary to update the workspace settings accordingly (making sure unittestEnabled is true and pytestEnabled is false

{
  "python.testing.pytestArgs": ["."],
  "python.testing.unittestEnabled": true,
  "python.testing.pytestEnabled": false,
  "python.testing.unittestArgs": ["-v", "-s", ".", "-p", "test_*.py"]
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants