TPI: fifo test communication (unittest)

[eleanorjboyd]

Refs: 23279

• macOS @aiday-mar
• linux @joshspicer
• windows @karthiknadig

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

[aiday-mar]

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]

Ran into the exact same issues as Aiday.