Add tests using custom-components/integration_blueprint#50 as base

[raman325]

I just pulled the files over and replaced references to integration_blueprint with {{cookiecutter.project_name}} and IntegrationBlueprint/Blueprint with {{cookiecutter.class_name_prefix}}.

What might be missing is instructions on how to run the tests, check for coverage, etc but figured someone else could tackle that.

Resolves #10

[oncleben31]

Thank you very much for your contribution. Some general comments you can already process during my code review:

• The test folder is not at the right place. When generating a project with cookiecutter, only the files in {{cookiecutter.project_name}} will be processed for replacing Jinja tags and copied to the destination.
• Could you add some explanations about how to use the test suite in the {{cookiecutter.project_name}}/CONTRIBUTIN.mdfile ?
• It will be perfect if you can update ./docs/guide.rst to explain what is doing the test suite and how to do use it. Could be in another PR.

[raman325]

🤦🏾‍♂️ clearly I moved too quickly on this - I have resolved bullet 1.

I will add an item for bullet 2 tomorrow, and bullet 3 sometime this weekend. The code has a lot of comments so I will likely just be pulling those together and making them into a single doc

[oncleben31]

On top of minor updates or questions, you need to review the tag used from the cookiecutter setting to make it works:

• Friendly name for human readable (ex: My awesome Custom Component)
• Project name with "-" as GitHub request it (ex: my-awesome-custom-component)
• Domain name with "_" as Python package expect it (ex: my_awesome_custom_component)

I've tried my best to suggest modifications but I have perhaps miss some.

[oncleben31]

Thank you for the modifications. I'm trying to run the test suite with a generated project.

I've identified some improvement to make it works.

To solve an error, we need to add a dummy __init__.py file in custom_components folder.

If you want to check the modification ? (you can test the generated project using this branch

[oncleben31]

Now the project generated by the cookiecutter template succeed to pass the test suite with 100% coverage. Houra !

There are some warnings with config_flow.py tests about some mocking function not awaited.
I'm not in my confort zone but I made some investigations and took inspiration from standard tests suite in Home Assistant core code and other custom component using pytest-homeassistant-custom-component

It seem's to be a best practice and make sens in config_flow test suite to avoid calling the async_setup and async_setup_entry coroutines. So I implement a patch and warnings are gone.

@raman325 Can you check the modification I suggest in this commit ?

[raman325]

good find and good fix. I will submit the same change here

[raman325]

Only thing to note is that you do not need to pass the fixture in as a parameter to test_successful_config_flow because you have already set autouse to True for the fixture

[oncleben31]

Thank you for your contribution