Tester and Designer Handbook for Otter

What problem does this address?

We should have some docs about best practices for testers and designers to report issues to developers and vice versa. Some small things can save a lot of time when done right.

Example for testing:

No helpful	Helpful
No clear indication about the error	Clear indication about the error with console that also highlights the file where the problem is produced

Example for design:

⚠️ The biggest obstacle is that besides the developer, other people are not aware of different things. While in time, people involved in the project get the knowledge, which might reduce the inconsistency, sometimes new people might be involved or a person has not been in touch with the project and might not be aware of the changes.

What is your proposed solution?

Docs with clear examples about good communication with the developer and vice versa.

Will this feature require documentation? (Optional)

None

The issue does not name a documentation path, file, or test to use. Start by locating the project's existing documentation structure and deciding where a tester and designer handbook belongs. Done means publishing clear, consistent examples for reporting issues and giving actionable feedback between testers, designers, and developers.