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: Python testing using new EOT token UNITTEST #22081

Closed
3 tasks done
eleanorjboyd opened this issue Sep 26, 2023 · 2 comments
Closed
3 tasks done

TPI: Python testing using new EOT token UNITTEST #22081

eleanorjboyd opened this issue Sep 26, 2023 · 2 comments

Comments

@eleanorjboyd
Copy link
Member

eleanorjboyd commented Sep 26, 2023

Refs: #21876

Complexity: 4

Author: @eleanorjboyd

Create Issue


Thank you for doing this testing! I apologize for how long it is and please let me know if you have any questions!

  1. Setup:

    1. Clone the test repo from here or use your own repo of pytests.
    2. Launch VSCode and open the inc_dec_example_repo/inc_dec_example_test_suite testing repo 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. In the terminal, run python -m pip install pytest.
    6. From the command palette, run "python: configure tests", select unittest and then "." (root directory) and then *_test for the test pattern.
  2. General:

    1. Run the tests and then cancel the test run. Check that there are no spinning icons indicating unresolved actions.
    2. Debug the tests, then cancel. Again, ensure no spinning icons appear. You should try canceling using both the stop button in the test explorer panel and in the debug controller.
    3. Execute a large number of tests to ensure that the test run completes (see the subtest folder)
    4. Verify that test run and logging function correctly by referring to test_logging.py. Ensure that ALL the expected output gets printed. Compare the output in VSCode with what you get when running unittest directly from the command line for the test_logging file.
    5. Run a test that has a segmentation fault, make sure it resolves correctly and displays a helpful message.
@eleanorjboyd eleanorjboyd added the feature-request Request for new features or functionality label Sep 26, 2023
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Sep 26, 2023
@karthiknadig karthiknadig added testplan-item and removed feature-request Request for new features or functionality triage-needed Needs assignment to the proper sub-team labels Sep 26, 2023
@bhavyaus bhavyaus self-assigned this Sep 26, 2023
@meganrogge
Copy link

couldn't verify the segfault one because tests have stopped working for me since I reloaded the window.

Overall, works well 👏🏼

@bhavyaus bhavyaus added this to the September 2023 milestone Sep 26, 2023
@rebornix rebornix assigned rebornix and unassigned bhavyaus Sep 26, 2023
@bhavyaus
Copy link

bhavyaus commented Sep 26, 2023

@eleanorjboyd I'm not seeing test_logging.py in the repo anywhere?

@rebornix rebornix removed their assignment Sep 26, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants