View Full Version : Use API to add tests of a specific subtype to a container
Scrapper
February 1 2012, 02:12 PM
I can list all the exchange related tests using test.list "testname=*", "testtype=wmi", "subtype=exch*", "devicename=*", but I can't use the subtype parameter to add tests to an existing container. Does anyone know of another way to do this?
Thanks,
Dan
rajib
February 1 2012, 03:41 PM
Hi Dan,
The container.update command does not provide test type/sub-type specific filter at this time although it is definitely a suitable candidate for a future enhancement. You may be able to accomplish the same using test name filter:
container.update "serviceName=Your Container", "serviceType=test", "memberListMethod=manual", "memberList=Server*", "testListMethod=manual", "testName=Exch*"
Regards - Rajib
Scrapper
February 2 2012, 09:01 AM
Unfortunately the 36 tests we've discovered so far don't have any commonality in theirname that I can leverage to filter them (none of them actually have "EXCH" in their name).
Dan
rajib
February 8 2012, 11:02 PM
Hi Dan,
You can specify multiple tests for container.create/update commands separated by comma (,) for the "testName" parameter. Alternatively, you can use the "testType" parameter and specify specific test categories:
container.update "serviceName=Your Container", "serviceType=test", "memberListMethod=manual", "memberList=Server1,Server2", "testListMethod=manual", "testType=wmi/exch_proto_sess,wmi/exch_is_latency,ping/rtt"
- Rajib
Scrapper
February 9 2012, 10:00 AM
I tried the following command:
container.update "servicename=Mobile ActiveSync (iPad) - Synth Tests", "servicetype=test", "memberlistmethod=manual", "memberlist=EXCCAS02.hoc-cdc.ca", "testListMethod=manual", "testName=*", "testtype=wmi/exch_avail_proctime", "memberListAppend=true"
The response was "OK 201 request accepted and processed, ready for next request", but the container didn't update
It seems to work with testtype=wmi, but if I add in the subtype (e.g. "testtype=wmi/exch_avail_proctime") it doesn't seem to work.
Powered by vBulletin® Version 4.1.10 Copyright © 2012 vBulletin Solutions, Inc. All rights reserved.