Thiyagarajan Veluchamy's Blog

First Name, Last Name Validation

Thiyagarajan Veluchamy — Thu, 22 Oct 2009 03:39:58 +0000

It should be

- first and last character must be alphabet

- accepts single character input

- it wont allow any special character and white space at start and end

Posted in Uncategorized Tagged: name validation

E-mail address validation

Thiyagarajan Veluchamy — Thu, 16 Jul 2009 06:42:35 +0000

We will discus how to validate email field,
given below,
E-Mail Address = “A@b.c”;                — Valid
E-Mail Address = “A@b.cnet”;         — Invalid
E-Mail Address = “A@b.c_”;             — Invalid
E-Mail Address = “A@bcnn”;            — Invalid
E-Mail Address = “Ab.cnn”;             — Invalid
E-Mail Address = “A@bc”;            — Invalid
E-Mail Address = “A@bat@.cnn”;   – Invalid
E-Mail Address = “A@bat/.com”;   – Invalid

conditions are,

Must not be too short and too long
Only one @ in email address
Only one period ‘.’ or two periods in email
No more than 3 characters after the final period (reverse find is 0 based not 1 based) com/ org/net/mil/gov/co.in/co.uk and etc
Should not have an underscrode after @
Allowed characters 0-9 A-Z _ . before @

Example E-Mail is thiyagarajannv@yahoo.com

I have devided Email ID in 4 parts in above email id,

In first part we have to check invalid condition input spaces, Left blank, use special character, symbols etc before email in @.
In Second part we have to check invalid condition input other specail character [!#$%^&*()_-:;”‘?/|\) at the place of @. left thisfield as blank. input spaces.etc
In third part we have to check invalid invalid domain.
In fourth part we have to check only valid suffix(.com,.co.in,.edu,.info,.org,.in etc)

very time EmailID should be in well manner.

like thiyagarajannv@yahoo.com and etc.

Posted in Manual Testing Tagged: E-mail address validation

File Handling Using QTP

Thiyagarajan Veluchamy — Wed, 15 Jul 2009 11:15:27 +0000

QTP File Handling

Many times we have may need to interact with text files using QTP. Interaction can be (but not limited to) in the form of reading input from a file or writing output to a file.

We can use FSO (FileSystemObject) object to do this.

What is FSO?
FSO stands for File System Object. This is used to support text file creation and manipulation through the TextStream object and is contained in the Scripting type library (Scrrun.dll).
The FSO Object Model has a rich set of properties, methods and events to process folders and files.

How to create a file?
We first create a FSO object using CreateObject.

Secondly we create a text file using CreateTextFile.
For Example: Suppose you want to create a file called “test.txt” located in C:\

Dim fso, file, file_actual_location
file_ actual_location = “C:\file_ actual _location”
Set fso = CreateObject(“Scripting.FileSystemObject”)
Set file = fso.CreateTextFile(file_ actual _location, True)

How to open a file?

Set file= fso.OpenTextFile(“C:\file_ actual_location”, ForWriting, True)
//2nd argument can be ForReading, ForWriting, ForAppending
//3rd argument is “True” if new file has to be created if the specified file doesn’t exist else false, blank signify false.

How to read content from a file?
Use ReadLine() method
For example:

Set file= fso.OpenTextFile(“C:\file_ actual_location”, ForReading, True) //2nd argument should always be “ForReading” in order to read contents from a file
Do while file.AtEndofStream <> True
data = file.ReadLine()
msgbox data
Loop

How to write content to a file?
You can use Write() or WriteLine() Methods to write text into a file. The difference between the Write() and WriteLine() Method is that the latter automatically inserts a new line character while the former doesn’t insert a new line character.
For example:

Set file= fso.OpenTextFile(“C:\file_ actual_location”, ForWriting, True) //2nd argument should always be “ForWriting” in order to write contents to a file
file.Write(“This is test is”)
file.Write(“file created.”)
//Output will be:
This is test is file created.
while
file.WriteLine(“This is test is “)
file.Write(“file created.”)
//Output will be:
This is test is
file created.

How to delete file?
Use DeleteFile() method to delete a file from a particular location
Foe Example:

file_location = “C:\file_actual_location”
Set fso = CreateObject(“Scripting.FileSystemObject”)
fso.DeleteFile(file_ actual_location)

Posted in Automation Testing, QTP Tagged: File Handling Using QTP, fso

QTP Advantages and Disadvatages

Thiyagarajan Veluchamy — Fri, 26 Jun 2009 12:42:18 +0000

Will be getting the initial focus on development of all new features and supported technologies.

Ease of use.
Simple interface.
Good error handling mechanism
Presents the test case as a business workflow to the tester (simpler to understand).
Excellent DDT (Data Driven Testing features)
Uses a real programming language (Microsoft’s VBScript) with numerous resources available.
Quick Test Professional is significantly easier for a non-technical person to adapt to and create working test cases, compared to WinRunner.
Data table integration better and easier to use than WinRunner.
Test Run Iterations/Data driving a test is easier and better implement with QuickTest.
Parametrization easier than WinRunner.
Can enhance existing QuickTest VB scripts without the Application Under Test? being available; by using the ActiveScreen.
Can create and implement the Microsoft Object Model (Outlook objects, ADO objects, FileSystem objects, supports DOM, WSH, etc.).
Better object identification mechanism.
Numerous existing functions available for implementation both from within QuickTest Pro and VBScript.
QTP supports .NET development environment (currently WinRunner 7.5 does not).
XML support (currently WinRunner 7.5 does not).
The Test Report is more robust in QuickTest compared to WinRunner.
Integrates with TestDirector and WinRunner (can kick off WinRunner scripts from QuickTest).
Must know VBScript in order to program at all.
Must be able to program in VBScript in order to implement the real advance testing tasks and to handle very dynamic situations.
Need training to implement properly.
The Object Repository (OR) and testing environment? (paths, folders, function libraries, OR) can be difficult to understand and implement initially.
we can’t done merzeing easly, when compare to winrunner
we can’t able to check if the Window of Background colour is dynamically changes.

Posted in QTP Tagged: QTP Advantages and Disadvatages

Priority Testing

Thiyagarajan Veluchamy — Wed, 20 May 2009 08:32:37 +0000

Generally Priority is Business for the projects. And this will be set by the team lead or the project lead, based on the severity and the time constraint that the module has the priority will be set.

Must fix the bug as soon as possible. Because bug is blocking further progress in this area.
Should fix the all issues, before release the product or project.
fix the issues within time period.

Posted in Uncategorized

Available Browsers for Linux, Windows, Mac for Testing

Thiyagarajan Veluchamy — Tue, 07 Apr 2009 11:11:11 +0000

A Web browser is a software application, user to display and interact with text, images, music, videos, games & etc typically located on a Web page at a Web site on the World Wide Web or a local area network. A web browser is importing for web application testing … The great number of browsers in the internet,

Web browsers listing for Windows

Logo	Browser Name & Developed by
	Internet Explorer Microsoft Corporation Download version 7 & 8
	Mozilla Firefox Mozilla Corporation Download latest version
	Chrome Google Download Chrome
	Safari Apple Inc. Download version 4 Beta
	Opera Opera Software ASA Download version 9.64
	Netscape Navigator AOL Download version 9
	SeaMonkey Mozilla Foundation Download version 1.1.15
	K-Meleon kmeleonbrowser.org Download version 1.5.2
	Amaya W3C Download version 11.1
	Maxthon Browser Maxthon Download version 2.5.1
	Flock Flock, Inc. Download version 2
	Slim Browser FlashPeak Download version 4.11
	KidRocket KidRocket.org Download version 1.5
	PhaseOut PhaseOut Download latest version
	Crazy Crazy Browser Download version 3
	Smart Bro Mind Vision Software Download latest version
	ShenzBrowser Shenz International Download version 1.1
	JonDoFox JonDoNYM Download version 2.1.3
	Avant Browser Avant Force Download version 11.7
	xB Browser XeroBank Download version 2.9.1.2
	Sleipnir Fenrir Inc. Download version 2.8.3
	space time space time Download version 1
	Browse3D Browse3D Corporation Download version 3.5
	3B Room 3B Download version 3.11
	Bitty Browser Turnstyle Download version
	Grail CNRI Download version 0.6
	Lynx Thomas Dickey Download version 2.8.6
	Happy Browser Igoodsoft Software Download version 1.03

Posted in Uncategorized Tagged: browsers, linux browsers, mac browsers, windows browsers

How To Access Blocked Web Sites

Thiyagarajan Veluchamy — Mon, 02 Mar 2009 10:54:03 +0000

i given blow more proxy sites:

http://www.hidemyass.com
http://www.anonymizer.com
http://www.wujie.net
http://www.ultrareach.net
http://surfshield.net
http://www.guardster.com/subscription/proxy_free.php
http://anonymouse.ws/anonwww.html
http://www.browser-x.com
http://www.spysurfing.com
http://www.xerohour.org/hideme
http://www.proxyz.be
http://www.sc0rian.com/prox
https://www.proxify.us
http://kproxy.com/index.jsp
http://www.brawl-hall.com/pages/proxy.php
http://www.proxify.net
http://proxy.computersteroids.com/index0.php
http://www.unipeak.com
http://flyproxy.com
http://alienproxy.com
http://proxify.com/
http://www.unfilter.net
http://www.proxymouse.com
http://www.surfonym.com/cgi-bin/nph-proxy
http://www.superproxy.be/browse.pl
http://www.websiteguru.com/mrnewguy
http://www.letsproxy.com
http://www.fsurf.com
http://indianproxy.com
http://www.letmeby.com
http://Boredatschool.net
http://www.ibypass.org
http://www.ipzap.com/
https://proxify.biz
http://kproxy.com/index.jsp
http://www.attackcensorship.com/attack-censorship.html
http://mrnewguy.com
http://www.evilsprouts.co.uk/defilter
http://www.proxify.info
http://www.torify.com
http://www.switchproxy.com
http://www.proxifree.com
http://www.secure-tunnel.com/
http://www.proxify.cn
http://www.arnit.net/utilities/webproxy/new
http://www.proxify.co.uk
http://www.betaproxy.com
http://www.proxify.org
http://www.proxychoice.com
http://www.proxysnail.com
http://www.anonypost.com
http://www.thestrongestlinks.com
http://www.hujiko.com
http://www.anonproxy.info
http://www.peoplesproxy.com
http://www.freeproxy.us
http://www.proxyweb.net
http://www.nopath.com
http://urlencoded.com
http://www.pole.ws
http://www.browseany.com
http://www.spiderproxy.com
http://www.clickcop.com
http://www.sneakysurf.com
http://www.mywebtunnel.com
http://www.thewebtunnel.com
http://www.3proxy.com
http://www.yourfreeproxy.com
http://www.proxy7.com
http://www.fireprox.com
http://www.stupidcensorship.com
http://www.letsproxy.com
http://www.sneak2.com
http://www.cecid.com
http://www.freeproxy.ca
http://www.ibypass.org
http://www.goproxing.com
http://www.projectbypass.com/
http://www.ipsecret.com
http://www.nomorelimits.net
http://www.proxify.de
http://www.bywhat.com
http://www.snoopblocker.com
http://www.anonymizer.ru
http://www.proxyking.net/
http://www.perlproxy.com
http://www.proxylord.com
http://tntproxy.com
http://satanproxy.com
http://zombieinvasion.info
http://demonproxy.com
http://www.myfreeproxy.com
http://www.gezcem.com/nph-proxy.pl.old
http://mpleger.de
http://www.the-cloak.com/login.html

Posted in Uncategorized Tagged: proxy servers

Top 25 common programming bugs

Thiyagarajan Veluchamy — Tue, 17 Feb 2009 06:17:37 +0000

Insecure Interaction between Components

Improper Input Validation
Improper Encoding or Escaping of Output
Failure to Preserve SQL Query Structure (‘SQL Injection’)
Failure to Preserve Web Page Structure (‘Cross-site Scripting’)
Failure to Preserve OS Command Structure (‘OS Command Injection’)
Clear text Transmission of Sensitive Information
Cross-Site Request Forgery (CSRF) 8. Race Condition
Error Message Information Leak

Risky Resource Management

Failure to Constrain Operations within the Bounds of a Memory Buffer
External Control of Critical State Data
External Control of File Name or Path
Un trusted Search Path
Failure to Control Generation of Code (‘Code Injection’)
Download of Code Without Integrity Check
Improper Resource Shutdown or Release
Improper Initialization
Incorrect Calculation

Porous Defenses

Improper Access Control (Authorization)
Use of a Broken or Risky Cryptographic Algorithm
Hard-Coded Password
Insecure Permission Assignment for Critical Resource
Use of Insufficiently Random Values
Execution with Unnecessary Privileges
Client-Side Enforcement of Server-Side Security

Posted in Uncategorized Tagged: 25 common programming bugs, common programming bugs, Top 25 common programming bugs

Testing Challenges

Thiyagarajan Veluchamy — Sat, 03 Jan 2009 04:38:32 +0000

It is human (people) nature to respond to any challenges thrown upon them. But what do human mean by a challenge?

Well one of the definition of challenge is ‘a demanding or stimulating situation‘. A challenge could be ‘a call to engage yourself in a contest‘. As a tester we face different challenges in our profession. These situations can be handled in a better way if we have the skills to analyze the problem and off-course by understanding how our fellow testers are tackling a particular problem in their unique context.

As a tester, we have some challenges which are very unique to our profession and some challenges are more generic in nature. A challenge has classified into two broad categories:

Analytical Challenges – These challenges are not unique to our profession and most of the professions require some degree of analytical skills. Analytic can be defined as “Having the ability to analyze” or “Ability to divide into elements and principle“, given the nature of testing it is very important for testers to have good analytical skills. Like any other skill, analytical skill can also be improved by practice. This skill can be improved by practicing different Puzzles, taking challenges or reading different books to improve your aptitude. Best mechanism of improving this skill is to exercise your brain.

Professional Challenges: Every profession has its own challenges. This section explains the different challenges faced in this field and how you can overcome them. These may be the interaction with the developer, attitude of Management towards testing, identification of tools, their usage and training, interaction with the customers, acceptability and entry-exit criteria for the tests and many more.

Posted in Manual Testing Tagged: Testing Challenges

Web Test Plan Development

Thiyagarajan Veluchamy — Mon, 14 Jul 2008 09:06:24 +0000

Web Test Plan Development

The objective of a test plan is to provide a roadmap so that the Web site can be evaluated through requirements or design statements. A test plan is a document that describes objectives and the scope of a Web site project. When you prepare a test plan, you should think through the process of the Web site test. The plan should be written so that it can successfully give the reader a complete picture of the Web site project and should be thorough enough to be useful. Following are some of the items that might be included in a test plan. Keep in mind thatthe items may vary depending on the Web site project.

The Web Testing Process

Internet
Web Browser
Web Server

PROJECT

Title of the project:
Date:
Prepared by:

PURPOSE OF DOCUMENT

Objective of testing: Why are you testing the application? Who, what, when, where, why, and how should be some of the questions you ask in this section of the test plan.
Overview of the application: What is the purpose of the application? What are the specifications of the project?

TEST TEAM

Responsible parties: Who is responsible and in charge of the testing?
List of test team: What are the names and titles of the people on the test team?

RISK ASSUMPTIONS

Anticipated risks: What types of risks are involved that could cause the test to fail?
Similar risks from previous releases: Have there been documented risks from previous tests that may be helpful in setting up the current test?

SCOPE OF TESTING

Possible limitations of testing: Are there any factors that may inhibit the test, such as resources and budget?

Impossible testing: What are the considerations involved that could prevent the tests that are planned?
Anticipated output: What are the anticipated outcomes of the test and have they been documented for comparison?
Anticipated input: What are the anticipated outcomes that need to be compared to the test documentation?

TEST ENVIRONMENT: Hardware:

What are the operating systems that will be used?
What is the compatibility of all the hardware being used?

Software:

What data configurations are needed to run the software?
Have all the considerations of the required interfaces to other systems been used?
Are the software and hardware compatible?

TEST DATA

Database setup requirements: Does test data need to be generated or will a specific data from production be captured and used for testing?
Setup requirements: Who will be responsible for setting up the environment and maintaining it throughout the testing process?

TEST TOOLS

Automated:Will automated tools be used?
Manual:Will manual testing be done?

DOCUMENTATION

Test cases: Are there test cases already prepared or will they need to be prepared?
Test scripts: Are there test scripts already prepared or will they need to be prepared?

PROBLEM TRACKING

Tools: What type of tools will be selected?
Processes: Who will be involved in the problem tracking process?

REPORTING REQUIREMENTS

Testing deliverables: What are the deliverables for the test?
Retests: How will the retesting reporting be documented?

PERSONNEL RESOURCES

Training:Will training be provided?
Implementation: How will training be implemented?

ADDITIONAL DOCUMENTATION

Appendix:Will samples be included?
Reference materials:Will there be a glossary, acronyms, and/or data dictionary?

Once you have written your test plan, you should address some of the following issues and questions:

Verify plan. Make sure the plan is workable, the dates are realistic, and that the plan is published. How will the test plan be implemented and what are the deliverables provided to verify the test?
Validate changes. Changes should be recorded by a problem tracking system and assigned to a developer to make revisions, retest, and sign off on changes that have been made.
Acceptance testing. Acceptance testing allows the end users to verify that the system works according to their expectation and the documentation. Certification of the Web site should be recorded and signed off by the end users, testers, and management.

Test reports. Reports should be generated and the data should be checked and validated by the test team and users.