Learn n Share

Selenium - For Web Browser automation

2013-10-02T14:59:00.002-07:00

Refer below blog for learning Selenium Step by Step.

Operational Acceptance Testing

2013-09-23T15:46:00.003-07:00

There are several types of Operational Test Activities that may be considered for a testing purpose, but the most important ones are as i have discussed below. These are discussed and defined from my own experience of work:

a) Application fail-over Test

· Objective:

a. To ensure whether resilience node is capable to handle the load when one of the two nodes goes down and it shares the load successfully when it is back.

b) Database Failure Test

· Objective:

a. To ensure whether the proper DB Alerts are received when a Database is down.

b. Time taken for restoration of service will be monitored during this test

c) Cable Pull Test (Network Blip Test)

· Objective:

a. The objective of this test is to do Network Blip testing and Application servers’ recover-ability.

d) UNIX Failure Test

· Objective:

a. The objective of this test is to verify the behavior of UNIX Application servers if they crash (abrupt shutdown).

e) Creation & Dropping of Partition Test

· Objective:

a. To ensure there is no performance impact while creating and dropping partitions on the database

f) Connection Keep Alive Test

· Objective:

a. The objective of this test is to verify the behavior of application connections when left idle for long

g) Back-end Failure Test

· Objective:

a. The objective of this test is to verify the behavior of applications when Back-end systems go unavailable & return back online.

b. All back-end systems involved will be made unavailable one by one.

h) Back-end Fail-over Test

· Objective:

a. The objective of this test is to ensure that back-end is capable to handle the request on Secondary Web Service when Primary Web Service is down.

b. All back-end systems involved will be tested for this one by one.

Downloading & Installation Apache Jmeter for Windows

2013-09-23T15:44:00.002-07:00

Downloading and Installing Jmeter is very simple and can be accomplished by simply following simple steps. However before that, please make sure your system is capable of hosting Apache Jmeter Software.

System requirements:

JVM 1.4 or higher
Jmeter v2.2 and later do not support Java 1.3.

Downloading Jmeter:

1. Navigate to http://jmeter.apache.org/download_jmeter.cgi

2. Click on apache-jmeter-2.8.zip (or the latest version available) under BINARIES sub-heading, which will start downloading of the zip file.

3. Unzip the file in area of your choice (I used C:\apache-jmeter-2.8).

4. Navigate to C:\apache-jmeter-2.8\apache-jmeter-2.8\bin

5. Double click on jmeter (Windows Batch File) or run Jmeter.bat from command prompt

Here you go!! Jmeter is ready to be used

Non Functional Testing - Overview

2013-09-23T15:42:00.002-07:00

Definition:

It is testing of "how" the system works. Non functional testing may be performed at all test levels. The term non-functional testing describes the tests required to measure characteristics of systems and software that can be quantified on a varying scale, such as response times for performance testing.

Classification:

I classify Non Functional Test activities into two parts:

1. Performance testing

Performance test activities include set of testing done on the application under test under various levels of load injection. Objective of these test activities is to access various performance parameters and applications’ behavior under various level of load injection.

Below mentioned Test Activities are done as part of Performance Testing.

a. Compatibility Testing

b. Break-point Testing

c. Soak Test

d. Single Node Test

e. Integration Test

2. Operational Acceptance Testing

Operational test activities are set of activities which are generally done after Test Team is confident on the Performance aspects of the application. These activities aim to simulate various scenarios which may arise during Operational Activities on the applications.

Below mentioned Test Activities are done as part of Operational Acceptance Testing.

a. Application Fail-over Test

b. Database Failure Test

c. Cable Pull Test (Network Blip Test)

d. Unix Failure Test

e. Creation & Dropping of Partition Test

f. Connection keep-alive Test

g. Back-end Failure Test

h. Back-end Fail-over Test

Recover Lost Photographs

2013-09-23T15:36:00.004-07:00

I just came back from a 10 day holiday to the best destination in the world, Switzerland & Paris; and as a keen lover, I took loads of pictures of my lovely wife and this part of world. However, things do take bad turn and as soon as I connected my SD card to my laptop to copy the memories, I found some junk files in the card and almost instantly my 1200 approx images were reduced to 500. I was in real shock, and frustrated by thinking of the fact , What Next?
Read More

Change password of user on a Remote desktop Machine

2013-09-23T15:34:00.004-07:00

Today , I met with a situation where the password on one of the remote systems i work on was going to expire and needs to be reset. Initially I thought CTRL + ALT + DEL would do the trick , but the action happened for my local machine. Then i found that the trick is :

CTRL + DEL +END

Hope This Helps...

Software Testing Basics

2012-08-26T10:25:00.003-07:00

Difference between Test Strategy & Test Plan

It is very common opinion that Test Strategy & Test Plan are same. However it is very important to understand that these are separate documents and are important in their own aspect. Lets understand what is the difference between these two documents.

Test Strategy

A Test Strategy document is a high level document and generally prepared by project manager. This document defines Software Testing Approach to achieve testing objectives. The Test Strategy is normally derived from the Business Requirement Specification document.

The Test Strategy document is a static document meaning which does not need constant updating. This documents sets the principles for testing processes and activities and other documents such as the Test Plan draws its contents from those standards set in the Test Strategy Document.

For small projects, sometimes the Test Strategy is included in the Test Plan, however this approach is not good for larger projects, for which there should always be a different Test Strategy Document and a separate Test Plan.

Components of the Test Strategy document

· Scope and Objectives

· Business issues

· Roles and responsibilities

· Communication and status reporting

· Test deliver-ability

· Industry standards to follow

· Test automation and tools

· Testing measurements and metrics

· Risks and mitigation

· Defect reporting and tracking

· Change and configuration management

· Training plan

Test Plan

The Test Plan document, is derived from various project documents such as Software Requirement Specification (SRS), Use Case Documents, etc.

The Test Plan document is usually prepared by the Test Lead or Test Manager and the focus of the document is to describe what to test, how to test, when to test and who will do what test.

· Introduction

· Test items

· Features to be tested

· Features not to be tested

· Test techniques

· Testing tasks

· Exit criteria

· Pass or fail criteria

· Test environment

· Test deliverable

· Responsibilities

· Time Plan