Skip to content

Error discovering pytest too aggressive #17100

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

Open
isidorn opened this issue Aug 24, 2021 · 2 comments
Open

Error discovering pytest too aggressive #17100

isidorn opened this issue Aug 24, 2021 · 2 comments
Assignees
Labels
area-testing bug Issue identified by VS Code Team member as probable bug needs proposal Need to make some design decisions partner ask

Comments

@isidorn
Copy link

isidorn commented Aug 24, 2021

Testing #17040

  1. Follow steps in the test plan item to setup pytest
  2. Start typing your test in the file
  3. As you are typing the following:
def test_math2():
    
  1. Notice an error in the Test view

The error reporting should be less aggressive. While the user is in the process of writing a test he or she should not be bothered with errors. I suggest the following heuristic:

  • While there are some tests discovered in the file do not show this error. Only show this error if the user explicitly clicks on the Run Tests action

Screenshot 2021-08-24 at 13 50 17

fyi @connor4312

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Aug 24, 2021
@karthiknadig
Copy link
Member

@isidorn Were you just typing or did you hit save or do you have autosave?

@isidorn
Copy link
Author

isidorn commented Aug 24, 2021

I have autosave. I was typing.

@karthiknadig karthiknadig removed their assignment Aug 24, 2021
@karthiknadig karthiknadig added area-testing bug Issue identified by VS Code Team member as probable bug needs decision partner ask and removed triage-needed Needs assignment to the proper sub-team labels Aug 24, 2021
@brettcannon brettcannon added needs proposal Need to make some design decisions and removed needs decision labels Feb 3, 2022
@eleanorjboyd eleanorjboyd self-assigned this Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-testing bug Issue identified by VS Code Team member as probable bug needs proposal Need to make some design decisions partner ask
Projects
None yet
Development

No branches or pull requests

4 participants