Microsoft Technology Licensing, LLC

Jared W Wilson

Aaron R Birnbaum

Curtis Dean Anderson

Peter Gerber

Loren Merriman

Charles D McClintock

Alan T B Brown

Michael Paul Robinson

James Perry Rodrigues

Donald Gordon Hardy

Carlo Rivera

Gordon Hardy

Patrick Joseph Niemeyer

Micah Andrew Koffron

Dipak Boyed

Paul A Just

Ross F Smith, Jr

Richard L Wright, Iii

Richard Wright

Xun Zhang

Detecting machine utilization activity may be provided. Client machine activity within a computer network may be monitored to determine if the client machine is available for use, or if the computer is already engaged in one or more activities. During a predetermined receive period, machine activity information for a given client machine. The machine activity information for the client machine is compared to previously stored machine activity information to determine if an activity state for the client machine has changed. If the activity state of the client machine has changed, the activity state for the machine is updated. Machine activity information for all computers in the computer network may be used to track and optimize resources with the computer network.

Detecting machine utilization activity

Software (such as server products) operating in a complex networked environment often run on multi-machine installations that are known as machine clusters. A server product can be tested on a server machine type. The server product can be tested by tracking the constituent machines of a machine cluster, and configuring and recording the roles that each machine in the machine cluster plays. Scenarios targeting a single server machine-type can be seamlessly mapped from the single machine scenario to a machine cluster of any number of machines, while handling actions such as executing tests and gathering log files from all machines of a machine cluster as a unit.

Machine cluster topology representation for automated testing

Computing environments, each executing at least one software program, are monitored for failures occurring during execution of the software program. Information associated with the failure, such as an identification of the software program and a failure type describing the failure, is recorded. The failure information is quantified to report the number of times the software program has failed or the number of times a particular failure has occurred. The quantified data may provide help in prioritizing what program or what failures merit investigation and resolution. Reports may be received from failing computing systems stopped at a state following the occurrence of the failure. In response, hold information is checked to determine whether to instruct the failing computing system to hold a state existing upon the occurrence of the failure.

Tracking down elusive intermittent failures

Automated client recovery and service ticketing may be provided. Client computers in a lab environment that become disconnected from a client management system may be recovered using an automated client recovery. Computers in a computer lab may be monitored to determine if a computer becomes disconnected from the client management system. If a computer is unresponsive with the client management system, an automated client recovery and service ticketing script is implemented to recover the unresponsive computer. If solutions within in the automated client recovery and service ticketing script do not recover the unresponsive computer, a service call request is automatically generated for the computer for subsequent examination by a lab engineer.

Automated client recovery and service ticketing

Software automation testing and validation are provided according to a system that runs automation tests using multiple lab machines and allows the testing to be performed before checking in the code to a version control system. Code changes in a build of the software are provided on a computing device. Automation tests are selected from a list of available tests. When indicated by a job queue, the changed code of the build is forwarded to lab machines allocated by an automation system. An image of the build from the computing device is generated on the lab machines and the automation tests are run against the build. A report is generated and forwarded back to one or more recipients that notifies of the success or failure of the automation testing.

System and method for automation testing and validation

Growing community of inventors

Redmond, WA, United States of America

Jared W Wilson