Monday, January 9, 2012

Monday, January 2, 2012


Happy New Year 2012 With AutoIt Tool
AutoIt v3 is a freeware BASIC-like scripting language designed for automating the Windows GUI and general scripting. It uses a combination of simulated keystrokes, mouse movement and window/control manipulation in order to automate tasks in a way not possible or reliable with other languages (e.g. VBScript and SendKeys). AutoIt is also very small, self-contained and will run on all versions of Windows out-of-the-box with no annoying “runtimes” required!
AutoIt was initially designed for PC “roll out” situations to reliably automate and configure thousands of PCs. Over time it has become a powerful language that supports complex expressions, user functions, loops and everything else that veteran scripters would expect.
Features:
  • Easy to learn BASIC-like syntax
  • Simulate keystrokes and mouse movements
  • Manipulate windows and processes
  • Interact with all standard windows controls
  • Scripts can be compiled into standalone executables
  • Create Graphical User Interfaces (GUIs)
  • COM support
  • Regular expressions
  • Directly call external DLL and Windows API functions
  • Scriptable RunAs functions
  • Detailed helpfile and large community-based support forums
  • Compatible with Windows 2000 / XP / 2003 / Vista / 2008 / Windows 7 / 2008 R2
  • Unicode and x64 support
  • Digitally signed for peace of mind
  • Works with Windows Vista’s User Account Control (UAC)
AutoIt has been designed to be as small as possible and stand-alone with no external .dll files or registry entries required making it safe to use on Servers. Scripts can be compiled into stand-alone executables withAut2Exe.
Also supplied is a combined COM and DLL version of AutoIt called AutoItX that allows you to add the unique features of AutoIt to your own favourite scripting or programming languages!
Best of all, AutoIt continues to be FREE – but if you want to support the time, money and effort spent on the project and web hosting then you may donate using the link to your left in the menu.
Take me to the downloads page!
download autoit AutoIt

Features

Basic-like Syntax and Rich Function Set
AutoIt has a BASIC-like syntax which means that most people who have ever written a script or used a high-level language should be able to pick it up easily.
Although it started life as a simple automation tool, AutoIt now has functions and features that allow it to be used as a general purpose scripting language (with awesome automation as well of course!). Language features include:
  • The usual high-level elements for functions, loops and expression parsing
  • A staggering amount of string handling functions and a Perl compatible regular expression engine (using the PCRE library).
  • COM support
  • Call Win32 and third-party DLL APIs
Built-in Editor with Syntax Highlighting
AutoIt comes with a customised “lite” version of SciTe that makes editing scripts easy. Users can alsodownload a complete version of SciTe that includes additional tools to make things even easier.
Standalone and Small
AutoIt is a very small and standalone application with no reliance on massive runtimes like .NET or VB. All you need to run AutoIt scripts are the main AutoIt executable (AutoIt3.exe) and the script. Scripts can also be encoded into standalone executables with the built-in script compiler Aut2Exe.
International and 64-bit Support
AutoIt is fully Unicode aware and also includes x64 versions of all the main components! How many other free scripting languages can you say that about?
Key and Mouse Simulation
Much time has been spent optimizing the keystroke and mouse simulation functions to be as accurate as possible on all versions of Windows. All the mouse and keyboard routines are highly configurable both in terms of simulation “speed” and functionality.
Window Management
You can expect to move, hide, show, resize, activate, close and pretty much do what you want with windows. Windows can be referenced by title, text on the window, size, position, class and even internal Win32 API handles.
Controls
Directly get information on and interact with edit boxes, check boxes, list boxes, combos, buttons, status bars without the risk of keystrokes getting lost.  Even work with controls in windows that aren’t active!
Graphical User Interfaces (GUIs)
AutoIt v3 will also allow you to create some complex GUIs – just like those below!

Sunday, January 1, 2012

Happy New Year 2012 !!!


Wish You A...Great, Prosperous, Blissful, Healthy, Bright, Delightful, Mind Blowing, Energetic, Terrific & Extremely !!!
...HAPPY NEW YEAR 2012...

new year scraps, comments, cards, images for Orkut, Myspace, Facebook, friendster


Thanks In Advance ...

Wednesday, December 14, 2011

Paths and URL, Testing Tool for desktop application

Q. Difference between Absolute URL and Relative URL ?
Ans. 

* Absolute URL : It is base URL and this represents domain address, called Base URL also.
* Relative URL : (Absolute URL + Page path)

Q. Describe some desktop application testing tools ?
Ans.

There are few testing tools for desktop application,
1. AutoIt
2. AutoHotkey
3. TestSmith
4. QAliber
5. pywingauto

Thanks

Difference between Freeware, Shareware and Open Source tools

Freeware vs Shareware vs Open Source


What are the differences between three models of "free" software, and why does it matter?

With all the excitement, many people are actually confusing open source software with two other models of "free" software--with potentially serious consequences. Here, we'll try to clear it up.

Freeware

The word "freeware" has been so overused, its meaning is no longer clear. Today it is often synonymous with "shareware," but for our purposes, I will define "freeware" as "software which can be downloaded, used, and copied without restrictions." (See this definition.)

Legally, the difference between freeware and open source is that you do not have access to the source code. Organizationally, this makes a big difference: There is no community and no development infrastructure around "freeware" as there is around open source software. Thus, while you can use freeware "as is," there is no real way to improve upon it or obtain support for it.

Thus, freeware is "free" as in those "Free Treadmill" classified advertisements.

Shareware

Shareware is a different concept. You can download and try shareware for free, but if you use it, you are supposed to pay for it. It is developed and released by someone who keeps full control of the intellectual property. The user does not have access to the source code and cannot modify it. There is also no collaboration or community around shareware.

In the end, the only difference between shareware and commercial software is that you can download and try shareware for free. Like commercial software, you are utlimately dependent on the developer of shareware for enhancements and support.

Thus, shareware is "free" as in "Free Sample" at restaurants or grocery stores.

Open Source

Open source means that the source code is available to all potential users, and they are free to use, modify, and re-distribute the source code. (For more details, see the Open Source Definition.) Legally, the "free" of open source refers exclusively to the source code, and it is possible to have support, services, documentation, and even binary versions which are not monetarily free. (Although some licenses, notably the GPL, requires that the source code always be freely available in such cases.)

In practice, open source usually means that the application is free to users as well as developers. Furthermore, most open source software have communities that support each other and collaborate on development. Therefore, unlike freeware, there are future enhancements, and, unlike shareware, users are not dependent on a single organization.

Open source advocates like to say that open source software is "free" as in "free speech," which is true. Since the user has the source code, it's also usually "free" as in "free lunch," even if sometimes you'd have to tip the waiter to get good service or pay for the wine.

In the Real World

The differences between the three models can be clearly seen in the kind of software that is available as freeware, shareware, or open source:
  • Freeware is usually a very small program, released by a student or enthusiast.
  • Shareware is usually a mid-sized utility or application, written by a professional developer or small software company. The developer or publisher does not have the resources to market it, so they release it as shareware with a "try-before-you-buy" business model.
  • Open source spans the gamut, but the largest "free" software out there are all open source--Linux, FreeBSD, PostgreSQL, Apache. Before the advent of VCs in the "free software industry," collaborative development around a shared code base was the only way a large free application could be built.
Does It Matter?

At first sight, these differences may seem like legal subtleties. In reality, though, misunderstandings about the true nature of open source can be a serious hurdle to the adoption and development of open source software.

For example, corporate users often confuse "open source" with "freeware." Thus, when we talk to them about "open source," they immediately think of the little utilities that they can download for free. Nice to have, of course, but without support or enhancements, they are dead ends for enterprise users.

(In addition, users confusing "open source" with "freeware" probably contributes to the concerns about the security of open source software. "Freeware" and "shareware" often come bundled with adware or spyware, which is actually not possible with "open source" software: see Is Open Source Secure?)

On the other hand, investors often confuse "open source" with "shareware." Thus, they are investing in companies which engage in the "free sample" business model. Many of these companies try to enforce some form of de facto if not de jure protection of their source code. Their investors may be able to reap the rewards of cheaper distribution, but, in the end, they are still investing in a traditional software vendor, with all the same risks and rewards as before.

Thus, for enterprise users to adopt open source software, they must understand the advantages of open source software over freeware. Only then will they understand that open source software does not share the same security and support problems as freeware.

Similarly, for investors to become really comfortable funding "open source business models," they will have to appreciate the potential of open collaboration in producing better software--and how it improves their risk/return tradeoffs.

Thanks in Advance ...

Wednesday, December 7, 2011

Excel Sheet Automation Fundamental


 #cs
 Project: Existing Project Name
 Criterion: AutoIt Scripting
 Purpose: To automate "Scenario Name" script test case
 Start Date: 12:10:2011
 Modify Date: 12:10:2011
 Author: Prashant Chauhan
 #ce

 #include <WindowsConstants.au3>
 #include <GuiConstantsEx.au3>
 #include <GuiTab.au3>
 #include <Misc.au3>

 ; There is some code for making excel sheet

 #include <Excel.au3>
 #include <File.au3>
 #include <array.au3>
 #include <Date.au3>

 $STime =  _DateTimeFormat( _NowCalc(),1)

  global $sFilePath = @WorkingDir & "\." & ".\result\Result.xls"
  _ExcelBookOpen($sFilePath)
  $oExcel = _ExcelBookAttach($sFilePath)

  $pass_count=0
  $fail_count=0
  $start=TimerInit()
  $logwrite = FileOpen(@WorkingDir & "\." & ".\result\Result.log", 1)
  FileWriteLine($logwrite,"")
  FileWriteLine($logwrite,"===== TC_createProjectFolder =====")
  FileWriteLine($logwrite,"")
 
  ;Run ("C:\ Path \*.exe")
  DirRemove("C:\ *.* ",1)

 WinSetState("Title","",@SW_MAXIMIZE)

  If WinExists("[TITLE:*; CLASS:*; INSTANCE:1]", "") Then
   FileWriteLine($logwrite,"Fail : The folder is not added to the project with the given name")
   _ExcelWriteCell($oExcel, "Fail : The folder is not added to the project with the given name", 5, 9)
   $oExcel.Activesheet.Range("I5").Font.ColorIndex = 3


;Red color=3, Green color=10, "I5" means- I for column and 5 for row


   $fail_count=$fail_count+1
  Else
   FileWriteLine($logwrite,"Pass : The folder is added to the project with the given name")
   _ExcelWriteCell($oExcel, "Pass : The folder is added to the project with the given name", 5, 9)
   $pass_count=$pass_count+1
  EndIf

 Sleep(2000)
 WinClose("[TITLE:*; CLASS:*; INSTANCE:1]", "")
 Sleep(1000)

 WinWaitActive("Modified Files")
 
  If WinExists("Modified Files") Then
   Send("{TAB}")
   Sleep(1000)
   Send("{ENTER}")
  EndIf
 
   $dif = TimerDiff($start)
   $Time = Round($dif/1000,2)
 
 FileWriteLine($logwrite, "Pass: "&$pass_count&"    Fail: "&$fail_count&"      Time: "&$Time&" Sec" )
 FileWriteLine($logwrite,"")
 FileClose($logwrite)

 _ExcelWriteCell($oExcel, $Time, 5, 12)
 ;_ExcelWriteCell($oExcel, '3', 5, 1)
 ;_ExcelWriteCell($oExcel, "TC_createProjectFolder", 5, 2)
 _ExcelWriteCell($oExcel, $STime, 5, 14)
 ;_ExcelBookClose($oExcel, 1, 0)

Friday, November 25, 2011

== Software Testing Concepts ==

Following should be the pre-requisite to start automation:

1. Build should be stable.
2. Functionalities should be getting repeated.
3. Test cases, which can be automated, should be filtered.
4. Generally after third or fourth release of the application.



Entry & Exit criteria is part of test plan document:

Entry Criteria: Use to determine that test plan is ready to execute 

1. Setup test environment that is required for particular test plan.
2. S/W or application has been installed successfully.
3. All required / specified per-requisite are there.

Exit Criteria: Use to determine that it is the time to stop testing like


1. All major functionalists have been cover as specify in test plan.
2. All test cases are completely executed or not.
3. S/W or application is bug free (up to 80%) and no higher priority 
or higher severity bug in application. 
4. All the documents should be reviewed, finalized or signed off.



Integration testing test cases:- 


Integration testing is done to ensure that the modules are integrated properly and to check the communication between modules 

:-- So to write the test cases 
:-- Simply enter the values in the Mandatory fields and Click the Submit/Login buttons.

here we don't fill the values in each and every text box.. we simply enter values in all of the required fields and will click on the button to check the modules are corrected or not.