Testing software for hardware. What you need to know about testing software for peripherals?

Question

Software testing

Hello everyone, help me figure it out, find the right vector for thoughts.
Faced with the fact that in the future it will be necessary to test software for the periphery. Keyboards, mice, headphones, most likely for the gaming industry.
What are the basic principles, useful plugins, tools. What is the specificity?
Where can you find good information?
Everything will be useful.
I understand that activities remain the same, but nevertheless, there are approaches, specifics, for example, as in mobile.
I look forward to any information and clarifying questions, thanks!

Answer 1

Damn, did I press Preview then F5? I repeat.
1. Use this hardware yourself, build your own usage scenarios. b) Not quite, of course, software, but still. If the mouse has a configurable height, what happens if it crashes or the user sets a minimum height? Will we be left with an inactive mouse without the ability to start it again? c) It turned out that simmers on RGB keyboards need backlighting with zones. And from me: backlighting depending on the keyboard layout. 3. Such software, as a rule, is buggy, fat (as for a resident program) and poorly localized. Find out what's wrong with it. Here are my typical complaints.
2. Go to forums, find out other people's usage scenarios and why they buy such hardware.
a) My scenario for using a gaming mouse: under the thumb of the browser button. Tilt wheel - very fast scrolling. Plus fast switching between work and play (DPI/layout). Who has a large monitor and / or little space - smooth (in increments of no more than 100) DPI adjustment and save what DPI was. In a shooter, as you know, you need a large DPI, but it happens that then the cursor just drives in the menu - which means you need an easily accessible adjustment in both directions.
a) Cheap RGB LEDs have poor color reproduction. Can it be compensated programmatically? (Well, PWM stuck, but this is already hardware.)
b) Often you have to shift your hand from the keyboard to the mouse. It happens that the input is from the keyboard, and OK is the mouse.
c) Can the program be divided into a resident control utility and a non-resident configuration utility?
(I was lucky with Gigabyte software, except for usability - there is nothing resident there at all, all logic, even sensor recalibration, is in the mouse itself.)