Group items tagged

Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well. Selenium has the support of some of the largest browser vendors who have taken (or are taking) steps to make Selenium a native part of their browser. It is also the core technology in countless other browser automation tools, APIs and frameworks.

Visual Studio 2012 includes the following command-line tools for testing purposes: VSTest.Console.exe You can use the VSTest.Console.exe program to run automated unit and coded UI tests from a command line. VSTest.Console.exe is optimized for performance and is used in place of MSTest.exe in Visual Studio 2012. MSTest.exe You can use the MSTest.exe program to run automated tests in a test assembly from a command line. MSTest is used for load tests and for compatibility with Visual Studio 2010 test projects. MSTest can also be used to view the test results from these test runs, save the results to disk, and save your results to Team Foundation Server. TCM.exe Tcm.exe is a command-line utility that lets you perform the following tasks: Import automated tests into a test plan Run tests that are part of a test plan from the command line View a list of test items and their corresponding IDs to use when you import tests or run tests You can also use tcm.exe to run test cases with associated automation from the command line using a test environment.

You can use the MSTest.exe program to run automated tests in a test assembly from a command line. You can also view the test results from these test runs, save the results to disk, and save your results to Team Foundation Server.You can also use tcm.exe to run test cases with associated automation from the command line using a test environment.

Requirements Visual Studio Ultimate, Visual Studio Premium, Visual Studio Test Professional

After you have created any of the following types of automated tests by using Visual Studio, you can use Microsoft Test Manager or Visual Studio to run the tests: Unit tests. Coded UI tests. Load tests.

Running automated tests: You can run tests directly from Visual Studio, from Microsoft Test Manager, from Team Foundation Build, or from the command line. You can use mstest.exe to run your automated tests from the command line, or you can use tcm.exe to import your test methods into test cases. You can then run the test cases for specific configurations from the command line and save the results for the appropriate test plan.

With loads of legacy Flash/Flex code where test automation support is limited or in most cases even non-existing there is only so much that can be done in forms of automation.

In short, unless you want to read it from Project Sikuli. Sikuli can match a predefined image to a section of the screen that is VERY similar to predefined image, ‘best fit’. So for example if you take a small screenshot of an object in you Flash implementation and save it as an image Sikuli can then be used to interact with this object, clicking on it, dragging it, checking if it can find it on the page asf..

Why Sikuli? Sikuli automates anything you see on the screen. It uses image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.

Why Sikuli? Sikuli automates anything you see on the screen. It uses image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.

We can collect the data when we run tests through Hudson, but that doesn’t make the output much more readable, doesn’t capture metadata (such as which environment configuration the tests ran against) and doesn’t even give useful historic snapshot data, as the jobs run different suites of tests based on parameters.

Js-test-driver is an open source JavaScript unit tests runner written in Java. The project was started at Google and is under active development. It is available under Apache License 2.0 license

s-test-driver is able to run from command line and reports results to the standard output. As a result, it is possible to fully automate JavaScript tests and run them on a continuous integration server.

s-test-driver is able to run from command line and reports results to the standard output. As a result, it is possible to fully automate JavaScript tests and run them on a continuous integration server.

tcm testcase /import /collection:http://<Team Foundation Server Name>:8080/tfs/<team project collection name> /teamproject:DinnerNow /storage:TestProject1.dll /category:"ShoppingCart&SmokeTest" /syncsuite:3

PhantomJS is a headless WebKit scriptable with a JavaScript API. It has fast and native support for various web standards: DOM handling, CSS selector, JSON, Canvas, and SVG.

Page Automation Access and manipulate webpages with the standard DOM API, or with usual libraries like jQuery. Learn more

Headless Website Testing Run functional tests with frameworks such as Jasmine, QUnit, Mocha, Capybara, WebDriver, and many others. Learn more

Monitoring and Metrics

Automatic Software Patching

Automated Backups

The Apache JMeter™ desktop application is open source software, a 100% pure Java application designed to load test functional behavior and measure performance. It was originally designed for testing Web Applications but has since expanded to other test functions

Access clear summary reports which allow you to drill down to screenshots, stack traces and video

Easily integrated with Continuous Delivery tools like TeamCity and Hudson

Facilitates all team usability and avoids silosBuilt for Agile - make your tests easily re-factored and robust to change

java -Xbootclasspath/a:lib/swinglibrary-0.14.jar:lib/registration-0.1.jar -jar  robotframework-2.5.3.jar  example.html

It is also possible to insert additional jar files to class path using the Xbootclasspath option. In this case, robotframework.jar does not need to be in class path. Here's the above example using Xbootclasspath: