Add vscode task code coverage

[mib1185]

Proposed change

This will add a new VSCode task to start code coverage report for a specific integration:

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[janiversen]

LGTM. A nice addition !! Thanks @mib1185

[ludeeus]

component -> integration

[chemelli74]

Test discovery task fails here, reverting this change make it works again.

Simone

[ludeeus]

There is no "Test discovery" task

[chemelli74]

There is no "Test discovery" task

Is part of VScode:

Here's the reference PR in witch pytest was configured to make it working out of the box: #53203

Simone

[ludeeus]

That is still working on current dev.

[janiversen]

I can confirm that it works!

could the problem be a failing test, in that case “test discovery” fails.

[chemelli74]

That is still working on current dev.

Did you rebuild the dev container ?
Here it still gives error:

Will investigate further asap.

Simone

[ludeeus]

On a fresh devcontainer you need to install bluez as bluetoothctl is used when scanning the tests for fjaraskupan

[chemelli74]

On a fresh devcontainer you need to install bluez as bluetoothctl is used when scanning the tests for fjaraskupan

Oh really ? Since when ?
And why is not in the requirements ?

Simone

[ludeeus]

Yes, I don't know.
I don't know.

[chemelli74]

On a fresh devcontainer you need to install bluez as bluetoothctl is used when scanning the tests for fjaraskupan

Running apt-get install bluez fixed it. Thx for the hint.
May we consider add it to Dockerfile.dev as additional run task ?

could the problem be a failing test, in that case “test discovery” fails.

Nope, I have a failing test but discovery worked fine; is just a matter of dependecies.

Simone

[ludeeus]

I don't see an issue with adding it, make a PR to have that discussion there instead of here.

[chemelli74]

I don't see an issue with adding it, make a PR to have that discussion there instead of here.

Done: #55469

Simone