This method is used to update one or more browser tests (Single Step or Multi-Step). Each update order is processed in its own transaction. The service processes all the update orders in sequence until all the update orders have been processed or a failure is encountered. The response shows the success or failure of each update order processed.





Input (literal)

This message contains a single UpdateTestsRequest element defining one or more monitor update orders (for Single or MultiStep browser tests).

Element Type Occurs Nillable? Description
SEQUENCE   1..1    
Credentials anyType (restriction) 1..1 No A Credentials element contains the username and password of an account user. The element is required in all requests to the Test Management Web Service.
UserName [element Credentials] string 1..1 No The UserName of an employee for an account (and used for authentication).
Password [element Credentials] string 1..1 No A secret used as part of user credentials for authentication. Every request to the Test Management API web service must include a Credentials element. That element itself contains a UserName and a Password element.
Monitors anyType (restriction) 1..1 No A Monitors element is a container of Monitor elements. It appears in a GetTests response and holds all the data that the query is expected to contain. It also appears in an UpdateTests request. There it contains all of the Monitor elements that are used to update the already provisioned tests.

Output (literal)

This message contains a single UpdateTestsResponse element containing one or more monitor update order responses. Each update order response shows the success or failure of the update attempt (whether it is an update or a deletion). The UpdateTestsResponse element never contains more than a single update order failure, because processing halts when a failure is encountered.

Element Type Occurs Nillable? Description
SEQUENCE   1..1    
ResponseStatus ResponseStatusType 1..1 No This element appears in most of the responses issued when the Test Management API operations are invoked.
ErrorMessage [type OperationResponseType] string 0..1 No The error message is provided if the ResponseStatus was FAILURE.
MonitorOrderResponses anyType (restriction) 1..1 No MonitorOrderResponses are collections of MonitorOrderResponse elements. They occur in the responses of both ProvisionTests and UpdateTests operation invocations. See the MonitorOrderResponse help pagefor more information.



<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
            <prov:Monitor name="Site Management Test SingleStepMonitor
              7/20/2012 11:55:55 AM" folder="Site Management Tests"
              agentType="IE" summaryFlag="On" includeRenderTimeFlag="On"
              frequencyInMins="60" expirationDate="2012-08-02T11:56:00"
              ipVersion="IPv4_only" monitorStatus="Active"
              folderStatus="Active" monitorId="264160"
              modifyDate="2012-07-22T00:05:00.62" scriptId="">
                  <prov:MonitorSite siteId="886"/>
                  <prov:Step stepSeqNum="0">
                     <prov:DisplayName>Compuware Test</prov:DisplayName>


<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
            <MonitorOrderResponse name="Site Management
              Test SingleStepMonitor 7/20/2012 11:55:55 AM"
              folder="Site Management Tests" monitorId="264160"
              monitorStatus="Active" orderStatus="SUCCESS">
               <Message>Successfully provisioned monitor:
                 AccountName = DEV - Eric Smith, MonitorName = Site
                 Management Test SingleStepMonitor 7/20/2012 11:55:55 AM,
                 MonitorId =264160</Message>