Cater for scenarios when device is no longer responding on resolved IP address #1365
Description
Describe the bug
Take a look at the report here.
The device in question requested an IP address during Startup, but then during Monitoring it abandoned its DHCP-allocated IP address, and reverted to using a completely different static IP address instead. This lasted for the remainder of the Monitoring phase, and then throughout all subsequent tests.
I'm not suggesting that this behaviour specifically should be captured/reported by Testrun, but the resulting report features a complete list of false negatives and false positives, for example the below suggesting that no HTTP server was found. It's not as simple as no HTTP server was found per se, the device wasn't even there on that IP address to begin with, and this is misleading.
Similar false negatives in the Services section of the report too, as elsewhere.
Expected behavior
You'll see throughout testrun.log that Testrun is very much aware that Resolved device IP: None, which is symptomatic of the above issue, and so there should be a mechanism in place to 'invalidate' or 'null' those relevant test modules or sections of the report, to prevent false negatives or false positives from being portrayed.
Error logs
report (69).zip