You have also forgotten the clocking of the processor (one-wire performs all communication based on timing since a single data line both sends and receives data bits and resets the sensor).

You have also forgotten the processor pins used.

Possibly the supply voltage used by the processor.

How the processor is going to report the result of the test - especially how to report a failure. You would probably like to know exactly where in the test sequence it fails.

How the processor will know when to start a test?

How the processor will differentiate between a failed cable (break) and no sensor connected.

If the test equipment is intended to pick up the serial number from the sensor and log ID and result somewhere for future reference.

Allowed cost for the test system (ok with LCD to display information, eeprom to store test results, printer to print test results, ...)

...

Do you soon see why no user has a test system available to post, and why the best solution is to retrieve already existing and tested onewire code and then adapt for correct timing and I/O pins and add the required back-end code for starting tests and for reporting results? Or why even such a "simple" thing as testing a one-wire assembly requires that either you or a consultant spends time and money on the problem.