Add some myuplink tests

[astrandb]

Breaking change

Proposed change

Add some more test to myuplink.

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)
• Deprecation (breaking change to happen in the future)
• 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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format 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.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

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

[home-assistant]

Hey there @pajzo, mind taking a look at this pull request as it has been labeled with an integration (myuplink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of myuplink can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign myuplink Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[astrandb]

@MartinHjelmare

I'd break out all the fixture loading to separate pytest fixtures that are marked with scope "session". Then they will only be loaded once per test session instead of loaded every test.

The json.loads call should be done per test so that we can modify the Python objects in the tests without changing the loaded data from the session fixture.

I have broken out the fixture loading with session scope. But I don't get exactly what you mean by the second paragraph. Can you give a little example?

PS I messed up my branch in #110426 and i found it easiest to close and start over with this PR.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[astrandb]

Thank you for the assistance. Setting up the tests is a bit outside my comfort zone.

[MartinHjelmare]

Only the fixtures that return strings should be marked as scope session. The fixtures that return mutable objects should be scoped per test so we can modify the fixture data without risking affecting other tests.

[astrandb]

I think I am starting to understand the background...

[MartinHjelmare]

Thanks!

[astrandb]

Thank you @MartinHjelmare, I have learned a lot during this review and I hope that we soon will see more thorough tests for this integration.