FluentAutomation.PhantomJS
Metadata
| Authors | Brandon Stirnaman |
|---|---|
| Copyrights | Copyright © Brandon Stirnaman 2012 |
| Description | Fluent Automation is a simplified DSL for web application automation testing. |
| Owners | Brandon Stirnaman |
| RequireLicenseAcceptance | False |
| Dependencies | FluentAutomation.Core:2.0.0.2|Fleck:0.9.5.10|Newtonsoft.Json:4.5.1 |
| Title | Fluent Automation API for PhantomJS |
| PackageSize | 5977854 |
| PackageHashAlgorithm | SHA512 |
| PackageHash | bi/8wn049/cuRcKN+lqPM4xZyFAgCoh9bc6kf5Xyv7TLlTqabdtC/qoUmGmEroHUQK5MpzBWmiCa7sBOcEE31g== |
| DownloadCount | 000000 |
| CreatedDate | 2012-11-01T01:18:15 |
| Language | en-US |
| ProjectUrl | http://fluent.stirno.com/ |
| ReleaseNotes | New docs at http://fluent.stirno.com/ |
| Tags | PhantomJS Phantom WatiN Selenium Fluent Automation API |
Access
You can access data for this project using the tools and addresses described below.
NuGet (nuget.exe)
- Installing the package (HTTP Basic authentication):
-
nuget install FluentAutomation.PhantomJS -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
nuget install FluentAutomation.PhantomJS -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
NuGet (Package Manager Console)
- Installing the package (search all configured feeds):
-
Install-Package FluentAutomation.PhantomJS
- Installing the package (HTTP Basic authentication):
-
Install-Package FluentAutomation.PhantomJS -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
Install-Package FluentAutomation.PhantomJS -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
- Uinstalling the package:
-
Uninstall-Package FluentAutomation.PhantomJS
OpenWrap
- Installing the package:
-
o add-wrap FluentAutomation.PhantomJS
- Uninstalling the package:
-
o remove-wrap FluentAutomation.PhantomJS
Versions
A version is snapshot of a project's source code. It does not need to follow the Major.Minor.Revision.Build numbering pattern. It can be an arbitrary string of text that identifies a release or a build, in particular including meaningful words like beta, RC or RTM.