Prettify json (tests)

[epenet]

Proposed change

Preliminary work for #68877

Should we or should we not prettify the tests/* ?

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.
• 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.

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.

[epenet]

I've marked this as ready for review, but should we or should we not prettify the tests/* ?

[frenck]

Tricky one. I think we should, mainly because... standardize all the things 🎉

But they are testing fixtures. Formatting could break specific tests (but should/probably won't). For example, testing a bad json file/fixture.

[epenet]

IMO, if one is testing a bad json file/fixture then it should be a text file and not a json file.

[frenck]

IMO, if one is testing a bad json file/fixture then it should be a text file and not a json file.

Dunno... maybe :) But for now its not an issue, so lets merge it.

[epenet]

Thanks, I've marked #68891 and #68892 as ready accordingly