Measurement in this device are often made by connecting the unknown component to +5V (through the microcontroller pins at logic 1). The current is then measured, or maybe the raise or the decay time in an RC circuit is measured.
The 5V has to be perfectly flat and constant during a measurement. If, for no matter what reason, the +5V voltage has spikes, or small voltage variations, or noise, these might lead to innacurate results, because all the calculations are made assuming the voltage is constant.
Possible reasons for voltage variations while a measurement is in progress:
- voltage ripple (at mains frequency when using a transformer + regulator, or at high frequency when using a switching power supply)
- any variation in current consumption will also affect the +5V regulated voltage, not much, but voltage regulators are not perfect. When the load current varies, voltage varies, too, thought +5V will vary only with a little bit.
- most input lines in almost any IC, will have internal protection diodes (clamping diodes), like this:
https://electronics.stackexchange.com/questions/324285/internal-clamping-circuit-at-the-input-pins-of-an-mcu. So, if you feed a 3.3V input with 5V, that voltage will pass through the internal protection diode of the input, and it will arrive at the +3.3V supply, creating perturbances in current and in voltage.
- even the microcontroller itself creates current spikes, when its internal gates switches between 0->1 or 1->0. Current spikes induces noises in any high impedance traces, and induces voltage spikes in voltage regulators.
- different MCU instructions during the executed code also have different current consumption, the power save states of the MCU also means very different current, and so on.
There are many reasons why the voltage will not be a perfectly constant 5.00000000V at all times during a measurement.
These variations are all in theory, and each type is mitigated in one way or another. Which one of these possible perturbations will produce visible measurement deviations (and which one will pass unobserved) is hard to tell, other than by experimenting in practice.
Anyway, this tester is not an ultra high accuracy scientific instrument.
The merit of this tester is that it is very clever, clever in hardware and clever in software. It is very easy to use, and a very practical tester to have in the lab. Its precision is good enough for day to day practical electronics.
So, don't overthink the precision, accuracy and resolution. Your initial plan (to use the modules you already have) seems like a good plan to me. In case it doesn't work from the first try, I would start another topic, to ask for advice about the particular design you may have, because this topic is not about designing new clones of the tester.
Build your own if you have the time, and if you like tinkering with electronics. If you just need a tester, and not interested much in experimenting (and maybe sometimes failing and fixing) while making your own tester, then buy one.
If I were to buy today, I would probably ask
indman if he has any for sale, or which one he recommends (because he's a developer of this tester).