Beginning with Selenium 3.0 Automation – Part IV (Scripting with Selenium 3.0)

Beginning with Selenium 3.0 Automation – Part IV (Scripting with Selenium 3.0)


Hey Folks, you are all set to begin with the Selenium scripting.

Continue reading


Beginning with Selenium 3.0 Automation – Part III (Setup your project and Configure build path)

Beginning with Selenium 3.0 Automation – Part III (Setup your project and Configure build path)


With your basic idea about Selenium, it is time to begin with the actual Selenium coding.

Continue reading

Creating an Effective Test Case Format

Creating an effective test case format

Time and again, the testing folks have to go about creating a test case set for the project at hand. As we are all aware that the test cases can be generalized with some basic fields.


The mandatory fields are

–          Test Case Title (It is best indicated to have a title which clearly indicates the functionality of the product under test).

–          Test Case Version (when you have multiple enhancements/ changes in the product and thereby the test case too).

Continue reading

Using HP – Quality Center for Effective Testing

 Using Quality Center for effective testing.


What is Testing?

In the software development life cycle, we find that testing is an important and integral part. Most people are of the view that testing phase can only be initiated for testing once the code is ready. They are wrong!!!


Testing will in fact be initiated from the requirements gathering phase until the stage when the product goes live. i.e. into production.


Phases in Software Development
Phases in Software Development

Let’s see the set of documents that aid testing during the various phases of software development.



With the onus on testing to deliver quality products, it became necessary to have a set of documents that are manageable and make sense to the development community. In comes various tools that will aid the testing and development community to track these documents. These tools manage all the testing activities and provide different kinds of reports.


Continue reading

Writing Test Cases for Security Test (Role Based).

Writing Test Cases for Security Test (Role Based).

What is a test case?

In software engineering, a product/ application is to be tested by exercising all possible combinations of features and inputs. In order to define a test case, we can say “It is a set of conditions or combination of variables under which a tester/ engineer will identify whether the application under test is working correctly or not”.

A single test case will not however verify that the application is working as desired. It will take numerous test cases for execution before we say that the application features are working correctly.

The typical set of test cases that are commonly used to test a particular application are

Continue reading

Hardfacts about Agile Process Implementation

Hardfacts about Agile implementation

Agile, the name conjures up images of the experience I had since the last one and half years. I have been in this traditional school of thought for Software Development for nearly 18 years. That is an awfully long time. I have time and again been exposed to the same traditional methods of development and testing. With the advent of the Agile product development process that was undertaken in our organization, it was kinda difficult to adjust to this new pace of activity.

You know what I mean!!! It has been like walking on the edge, knowing very clearly that one fall will expose a far greater risk which we may not be able to overcome. However the experience has been exhilarating and thrilling to the core. Innovation and creativity has become a part of life as a software engineer now. For most of the developers it was a change from the usual chore of creating huge rolls of documents to prove what they had developed.

Continue reading

Web Applications – Scalability

Scalability for Web applications

What is scalability?

In simple terms, the server should be able to meet the increased demand for HITS per SECOND/ Transactions per Second over a period of time in increasing user ratio, without failure.

If the Hits per second decreases at some point of time, then it is indicative of decreased performance. Typically a decrease in scalability can be traced to database indexing problem, a full data cache or a saturated network connection.

Therefore it becomes necessary to test the disk usage, memory, or network components while stress testing.

Continue reading