microsoft / testapi

TestApi is a library of test and utility APIs that enables developers and testers to create testing tools and automated tests for .NET and Win32 applications. TestApi provides a set of common test building blocks -- types, data-structures and algorithms -- in a simple, layered, componentized and documented stack.

TestApi is...

TestApi is a library of test and utility APIs that enables developers and testers to create testing tools and automated tests for .NET and Win32 applications. TestApi provides a set of common test building blocks -- types, data-structures and algorithms -- in a simple, layered, componentized and documented stack.

Get started

• Get the latest release.
• Read the following blog articles for a quick introduction to some of the available features:
  • Overview of TestApi
  • Input Injection APIs
  • Command-Line Parsing APIs
  • Visual Verification APIs
  • Combinatorial Variation Generation APIs
  • Managed Code Fault Injection APIs
  • Text String Generation APIs
  • Memory Leak Detection APIs
  • Object Comparison APIs
  • Part 9: Application Control APIs
• Read the documentation, experiment with the samples, check out the source code.
• Let us know what features you would like to see in future releases.

Vote

Please vote on http://testapi.uservoice.com for specific features, or just send us feedback on the usefulness, architecture, and relevance of the provided APIs, and let us know what APIs you need for your work. The library will evolve based on user feedback.

Roadmap

• Existing APIs

  • Application control API
  • Combinatorial variation generation API
  • Commandline parsing API
  • Input API
  • Leak detection API
  • Managed code fault injection API
  • Object comparison API
  • Text string generation API
  • Theme API
  • UIA utility API
  • Visual verification API
  • WPF dispatcher operations API

• Suggested Future APIs

  • Concurrency API
  • Controls verifications API
  • Cross-platform support
  • Fuzzing API
  • Input injection API (additions)
  • Media verification API
  • Mocking API
  • Performance API
  • Screen resolution API
  • Setup validation API
  • State management API
  • Stress and load testing API
  • UIA utility API (additions)
  • Unmanaged code fault injection API
  • Unmanaged API interface

• Package Components

  • Acceptance tests
  • Binaries
  • Documentation
  • MSTest samples
  • Sources
  • xUnit and NUnit samples

Contributors

Project Development:

• Alexis Roosa
• Andrey Arkharov
• Anne Gao
• Bill Liu (blog)
• Daniel Marley
• Dennis Deng
• Eddie Li
• Eugene Zakhareyev (CARBON!)
• Ivo Manolov (blog)
• Jared Moore
• Nathan Anderson
• Peter Antal (blog)
• Ranjesh Jaganathan
• Sam Terilli
• Shozub Qureshi
• Tim Cowley
• Vincent Sibal (blog)
• William Han

Reviewers:

• Abhishek Kumar Mishra, Adam Ulrich, Adrian Vinca, Alexis Roosa, Brad Van Ee, Brian McMaster, Christine Warren, Daniel Marley, Dawn Wood, Dennis Cheng, Dwayne Need, Krasimir Alexandrov, Ian Ellison-Taylor, Jim Galasyn, John Gossman ([blog), Lester Lobo (blog), Mak Agashe, Matt Galbraith, Michael Hunter (blog), Mike Pope, Patrick Danino (blog, Peter Antal, Robert Lyon, Rossen Atanassov, Scott Shigeta, Scott Wadsworth, Sue Dernbach, Yong Lee.

testapi's Issues

License file is missing

This repository misses the license file.
The severity of that varies from project to project, but my goal here is to attract some attention.

If it's not a problem, this issue can be closed.

I'm leaving it here just in case: https://help.github.com/articles/adding-a-license-to-a-repository/.

Thanks.

Codeplex is gone. How do we download this library now?

Codeplex is gone. How do we download this library now?

Split Out CommandLineParser to it's own library

I've been using TestApi for years now. Solely for the CommandLineParser classes. I use it for any command line utility I build.

I'd love to have this functionality split out to it's own NuGet package. And possibly it's own project altogether so I don't have to take in all the testing stuff I don't need (like WPF Visual Verification) just for the command parsing functionality.

I've considered doing this fork myself, but would rather it be done officially so we don't get feature drift.

This repo is missing important files

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

.NET Core Compatibility for Fault Injection

I am trying to use it with a .NET Core app, but apparently the Fault Injection is not taking place. The .rul file as well as the .mfi file are successfully being created but still the fault injection itself is not happening. Is there any way around to make it work for .NET Core apps?