Articles and Reviews on Testing Tools

Acceptance Test-Driven Development (ATDD) is a development methodology based on communication between the business customers, the developers, and the testers. ATDD encompasses many of the same practices as Specification by Example,Behavior Driven Development (BDD),Example-Driven Development (EDD),and Story Test-Driven Development (SDD).
All these processes aid developers and testers in understanding the customer’s needs prior to implementation and allow customers to be able to converse in their own domain language.

The agile testing quadrant separates the whole process in four Quadrants and helps to understand how agile testing is performed.

We did a small fight of features between Selenium, most wanted web testing tool and Ranorex well known web/mobile/desktop testing tool.

This small fight include only 17 comparison issues, my guess that there is much more, so please comment for more issues to add to this table.

you can also view here comparison between web testing tools.

DID YOU KNOW

ODT - Observation Driven Testing, A testing technique for identifying code behavior that is unexpected. An automated tool can test the code by executing it in many ways based on the contents of the code units, and their relationships, and then provide its observations about code behavior to the developer for review.

How to Read a pdf using the selnium webdriver? here is one solution, implemented with selenium on visual studio,

extract PDF using selenium.This sample will helps you out

On traditional projects, testing is usually treated as a quality gate, and the QA/Test group often serves as the quality gatekeeper. It's considered the responsibility of testing to prevent bad software from going out to the field. The result of this approach is long, drawn out bug scrub meetings in which we argue about the priority of the bugs found in test and whether or not they are sufficiently important and/or severe to delay a release.
On Agile teams, we build the product well from the beginning, using testing to provide feedback on an ongoing basis about how well the emerging product is meeting the business needs.

Selenium is a browser automation tool, commonly used for writing end-to-end tests of web applications. A browser automation tool does exactly what you would expect: automate the control of a browser so that repetitive tasks can be automated. It sounds like a simple problem to solve, but as we will see, a lot has to happen behind the scenes to make it work.

Before describing the architecture of Selenium it helps to understand how the various related pieces of the project fit together. At a very high level, Selenium is a suite of three tools. The first of these tools, Selenium IDE, is an extension for Firefox that allows users to record and playback tests. The record/playback paradigm can be limiting and isn't suitable for many users, so the second tool in the suite, Selenium WebDriver, provides APIs in a variety of languages to allow for more control and the application of standard software development practices. The final tool, Selenium Grid, makes it possible to use the Selenium APIs to control browser instances distributed over a grid of machines, allowing more tests to run in parallel. Within the project, they are referred to as "IDE", "WebDriver" and "Grid". This chapter explores the architecture of Selenium WebDriver.

Start or Stop Appium Server Programmatically using Java.
Appium is a very promising tool when it comes to mobile automation. I have given it a try for about 6 months when I was working on a mobile testing framework for my company. 
Appium comes in many client bindings (Java, C#, Python and Ruby) which offer a lot of features, but they lack the ability to start the server in an automated way which means that it has to be done manually.

Apache JMeter is a great open source tool designed for load testing and performance measurement of web applications and web services. For those of you wishing to bring together the strengths of JMeter and JSystem, here is a short tutorial describing the methods that me and my team members have devised for integrating JMeter scripts with JSystem

Consider the following scenario:
You're writing an automation script that's supposed to perform a login to a website (using a username and password), and then you're transferred to the next web page which has a link for downloading a PDF document (call it: my_report.pdf). To download the file, your script would need to be able to perform the following steps:

1. Enter a username and password into the relevant input fields and click the "Submit" button.
2. On the next page, click the "Download Report" link to begin downloading the my_report.pdf file.
3. Select a location on your local hard drive for saving the PDF document, and finally download the file to that location for some further processing.

eggPlant brings a plethora of cross platform, technology agnostic user based test automation capabilities to an organization through image recognition technology, with complete control of entire user interface.
It can automate anything that a manual test engineer needs to test.
eggPlant essentially started as a functional testing tool which later developed into an automation solution that could automate any system, rather than the application.
It later permeated into performance and load testing, network testing, device and lab management testing, mobile and integration testing space.
The tool further focuses to provide solutions for test analytics, test creation and test environment management.

Read on how to setup Selenium with SoapUI installation in a way that it will empower SoapUI, to be operation even for testing flows that need interaction with the UI.