The Lightweight Test Automation Framework (LTAF) for ASP.NET is an open source project that was developed and is currently used by the ASP.NET QA Team to automate regression tests for the product. It is designed to run within an ASP.NET application.
Tests can be written in any .NET Framework language. Tests use an API to manipulate and verify the DOM of the browser. The Lightweight Test Automation Framework supports running tests in Microsoft Internet Explorer, Mozilla Firefox, Apple Safari, and Opera. In addition, LTAF provides an emulated UI-less version of the browser, that simplifies scenarios when LTAF tests live in some larger automated tests projects, unit tests for example.
- LTAF v1.0. Was released in November 2009 at ASP.NET QA codeplex page and had pretty good audience. Please check page for LTAF v1.0 for more details or small samples document displaying simplest use cases.
- LTAF v2.0 (this release). Starting this release LTAF becomes fully open source (as opposed to the first version) and everyone can contribute and help this project to evolve. New features in LTAF v2.0:
- Refactoring of the solution structure and change of the naming convention for assemblies and namespaces. Previously LTAF v1.0 was still owned my ASP.NET QA and had Microsoft.Web.Testing in assembly and namespace names. Now, when it is completely open source, we decided that it is a good time to substitute Microsoft.Web.Testing with shorter and more convenient name LTAF.
- New feature BrowserEmulator was added. BrowserEmulator is a lightweight UI-less browser that is suitable for simple scenarios and is very handy for automated test execution when NO UI is a requirement.
- Bug fixes.
- LTAF NuGet package was added to common NuGet feed, check this page for package details.
To get started, download latest suggested release and check out SamplesWebSIte, which is similar to the samples web site of version v1.0 (in meanwhile while documentation for LTAF v2.0 is being developed, please check out samples document for LTAF v1.0
More detailed documentation is still being developed and will be added to codeplex project Documentation tab along the way. However contributors are very welcome to suggest any ideas or samples.
Detailed document for contributor is under development. In meanwhile, you are welcome to pull existing sources and propose your feature or changes. However, before anything may be checked in you change should be discussed, approved and should pass code review by one of the coordinators. Please feel free to start discussion or post your ideas!