docs(best practices): refactor code or tests, not both at once

[HonkingGoose]

Changes

• Explain that you should refactor the tests or the code, but not both

Context

@rarkins and @zharinov have a unwritten refactoring rule: ¹

OK so I believe you are describing a kind of unwritten refactoring rule which @zharinov and I have, which is: refactor the code, or refactor the tests - but avoid refactoring both at the same time or you can accidentally mask regression errors

This rule should be explained in our developing docs. 😉

Related to issue:

• Contributing docs: clarify to toMatchSnapshot, toMatchInlineSnapshot, toMatchObject, toEqual #25106

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

Footnotes

1. https://github.com/renovatebot/renovate/issues/25106#issuecomment-1759310483 ↩

[renovate-release]

🎉 This PR is included in version 37.26.0 🎉

The release is available on:

• GitHub release
• 37.26.0

Your semantic-release bot 📦🚀