Configure test command is not registered when the extension activates

[Tyriar]

Repro:

1. Reload window
2. Run Python: Configure Tests

[eleanorjboyd]

@Tyriar do you remember what your setup looked like when you got this notification? Was the python extension activated yet? Had you ever run / configured tests in this workspace before?

[Tyriar]

@eleanorjboyd I'm pretty sure it was happening because the python extension wasn't activated, meaning python.configureTests was not working properly as an activation event.

[eleanorjboyd]

To follow up on this, would the desired outcome just be for the action to not show in the command palette until the extension has activated?

[brettcannon]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

[Tyriar]

The user should never be able to see a message about a command missing. I think the right thing here is that all commands should be registered upon activation, otherwise there's a chance of this happening.