Microsoft Technology Licensing, LLC

Vijaya K Upadya

Shibani Basava

Dinesh Chandnani

Ram Kumar Donthula

Andrew Christopher Neil

Zhu Chen

Xin Shi

Brian W Boon

Shaun Miller

Geoffrey Staneff

Evgenia Steshenko

Matthew Sloan Theodore Evans

Carl Brochu

Eric I Maino

Daniel Moth

Ryan J Cavanaugh

Christopher A Smith

John F Lam

Safia Abdalla

Kwangje Cho

Katherine Kampf

Vaishnavi Sannidhanam

Barry Manh Tu

Kyrylo Osenkov

Dileep Yavanmandha

Gabriel Esparza-Romero

Damon C Tivel

Some embodiments support embedding of a notebooks software component in a surrounding host application, thereby promoting consistency of notebook user interfaces and user experiences between different kinds of applications. For instance, the notebook access added to an integrated development environment (IDE) may be aesthetically consistent with the notebook access added to a business analytics tool from the same vendor as the IDE. Departures from the aesthetic are still supported, e.g., a notebook access provided in a video gaming environment to teach gamers programming skills may have the same aesthetic as the simulated world of the video game, rather than an IDE aesthetic or an enterprise software aesthetic. Direct integration or proxied integration architectures may be used. Efficiencies may be gained by distinguishing between notebook viewing, editing, and executing operations, and providing more computationally expensive resources only as needed for the notebook access being performed.

Embeddable notebook access support

A rule-based attribution mechanism analyzes documents having different types of data in different formats through the application of script-based rules that apply a tag to the document identifying the type of sensitive data that is contained in the document. Documents having similar tags are aggregated so that the sensitive data is scrubbed from the document leaving the telemetric data available for downstream processing. The scrubbing entails different actions, such as, eliminating the sensitive data, obfuscating the sensitive data, and converting the sensitive data into a non-sensitive value.

Rule-based document scrubbing of sensitive data

A test case is abstracted into a re-useable script or other declarative form that expresses the intent of a task rather that defining how the test will be performed. Tools translate the declarative test into a series of steps corresponding to code that implements the action indicated in the declarative test. The schema for the tests can be dynamic. New forms of test cases can take advantage of new actions so that the library of actions can be extended. Libraries are interchangeable. Test cases can be generated using a state machine. New test cases can be composed dynamically using a state machine to create new test cases.

Using a DSL for calling APIS to test software

Growing community of inventors

Sammamish, WA, United States of America

Vijaya K Upadya