$summary, allows mixing network types (eg. fibre and copper where no fibre<->copper interconect exsits.
A work-around exists currently by running each test individually and resetting the --server option each time: > hts certify --test network --device eth0 --server server1 > hts certify --test network --device eth1 --server server2 The fix would be to allow the syntax for test planning: > hts plan --test network --device eth0 --server server1 > hts plan --test network --device eth1 --server server2 So that the --server option could be left off the "hts certify" runs.
*** Bug 437874 has been marked as a duplicate of this bug. ***
Created attachment 319778 [details] hardwaretest.py patch adding per-test server setting This patch allows the hts server to be set for individual tests, via the syntax: hts plan --test <testname> ( --device <device name> | --udi <udi> ) --server <server name or IP address> If a server is set for a test, it overrides the default setting via the plan or certify command.
Created attachment 319779 [details] certificationtest.py patch to add per-test server setting to xml storage
Created attachment 319780 [details] xml DTD changes for added server attribute
Verified --server can be set for individual tests with hts-5.3-12.