Microsoft Technology Licensing, LLC

Kristopher Makey

Dmitri A Klementiev

Scott M Louvau

Eric I Maino

Ryan J Cavanaugh

Xuechun Li

Robert Mitchell Smith

Warren Alpert

Alexis Descre

William Sean Sheehan

Donald T Sprague

Arnav Kumar Agrawal

Aspects of the present disclosure relate to adverse user behavior detection and mitigation. In examples, a user account of a social platform may be trusted or untrusted. If the user account is untrusted, activity of the user account may be buffered so as to not directly affect social metrics of the social platform. For example, if the untrusted user account follows a target user account, the untrusted user account may be added to a separate set of followers or otherwise separated from a set of trusted followers of the target user account. Eventually, each user account in the separate set is evaluated to determine whether the user account has transitioned to a trusted user. If the user account is now trusted, it may be migrated to the set of trusted followers. However, if the user account is untrusted, it may be removed from the separate set, thereby reverting the activity.

Adverse user behavior detection and mitigation

A generated object model engine abstracts actions, used in test cases, in a manner to produce new object model types that are independent of an underlying code implementation. The generated object model engine analyzes action classes to aggregate a set of actions having similarly-related class types. Action classes having similarly-related class types are then used to form a new object model type. The new object model type may be used in a test case to hide the action's code implementation from the test case.

Generated object model for test automation

A test case can be run with actions from the test case being executed in multiple execution paths. This can be done with the aid of an action broker. For example, the broker may identify available automation implementations for the actions and use a priority list to select between available automation implementations for executing an action from the test case. The broker may also perform conversions of results of actions for use by implementations executing other actions in different execution paths, as well as passing results between implementations in different execution paths.

Multi-path brokered test automation execution

Growing community of inventors

Kirkland, WA, United States of America

Kristopher Makey