Articles and Reviews on Testing Tools

Mobile applications are key to success for many businesses and individuals. A successful app is always appreciated by users, however a lot of effort is put behind it to make it seamless and bug free.
Testing any type of mobile applications involve same amount of effort irrespective of operating system. Below are some of the tips that I learned hard way while creating my first few mobile device applications. You can use these as a starting point for testing Android, iOS, Windows or any other mobile application.

The following diagram will help you understand precisely how HP ALM functions without any undesired and unnecessary loopholes in the complete work-flow of an application.

In today’s write-up we are going to have idea about HP ALM test management tool, its history, Introduction, Architecture, workflow and modules. We will also understand one of the work flow phases “Release Specification”. HP ALM is a web based tool platform with various key applications and a dashboard focusing on the core life cycles of applications. Let’s understand step by step each function of ALM with more practical approach.
 

What is API testing ?

The API Testing is performed for the application, which has a collection of API that must be tested. API calls verify functionality and expose failure of application.

API testing is strongly connected with Back-end/Database testing, you may have brief knowledge of SQL queries. (That would be an advantage )

This article will present you how to test the API with Postman application.
 

When talking about testing websites and the spacial use case involving "analytics" setups, It turns out that both simple and complicated analytics setups require about six testing sessions. When working with large web sites analytics setup tend to get broken routinely. While custom alerts can help to detect large disasters, automated testing tool is invaluable for tracking these type of failures early.

When Do we need Automatic testing frameworks?

• When there are many repetitive tests (Reusability of Automation Script)
• When there are frequent regression testing iterations ( Frequency of use of test case)
• When you need to simulate large number of users (load testing)
• When you have a large set of test cases. .Time Comparison (automated script run much faster than manual execution.)
• When you can’t rely solely on manual test execution for critical functionality

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.