TESTEVERYTHING (QTP,JMETER,SELENIUM,WEBDRIVER)

Dim yourstr,r,letter,result yourstr="pro1gr3a6m" Set r=new regexp r.pattern="[a-z 0-9 A-Z]" r.global=true set s=r.execute(yourstr) For each letter in s result= letter.value&result Next print result

Tips to Optimize QTP Scripts to Yield Better Performance We use Automated-testing tools to optimize our manual testing processes. But in order to reap full benefits of any automated testing tool, we must know the complete ins and outs of the tool otherwise it would be a huge waste of money spent on automation. We have to learn the automation tool very thoroughly. We also need to learn the language of the automation tool to do coding more effectively and efficiently. I believe that a software testing tool is as good as the person who is actually using it. I have been getting so many emails from my esteemed readers asking about HP QuickTest Professional tutorials, QTP tips and tricks etc. Some readers even complain that their QTP scripts are too slow to execute. This time I decided to write a post on how to use QTP more effectively which means how to make our QTP scripts perform better. In order words, this post will throw light on some points, which will optimize your QTP scripts...

Synopsis:  Find out ways to pass a value between threads (i.e. capturing a value in one of the thread and passing it to the other thread in the same test plan). Tool Used:      JMeter: Performance testing tool. Solution:        Sharing Variables 1)       Used Sampler : BSF Sampler 1)       Screenshot displaying the use of the BSF Sampler using  ${__setProperty(storeid, ${storeid})}; for capturing the time. The website used is http://www.mail-archive.com/jmeter-user@jakarta.apache.org/info.html for displaying the value captured in one thread to the other thread. Screenshot 1: Displaying the BSF Sampler capturing the time value using ${__setProperty(storetime, ${__time(HMS)})}; Screenshot 2: Displaying the time captured using ${__property(storetime)} in the other thread. Screenshot3: Successful execution of the script ...

Hi All, Some times we have to  check that a object(WebElement) is  exist on page or not. For this we use object exist = False  property but when we run the script it gets failed While object is not showing in the Page. We think that there is  something  wrong. The reason behind why QTP  is giving this because object is present in the page but not visible means it not displaying while it exist in HTML code. So for this we have to be understand the object property( object.currentstyle.display) there will be case some time object inherit the property from its parent or another parent element property to display in page . First we have to identify that object when it not showing/displaying in page.We have to check its display property Display property value we can get through like this  rem disvalue disvalue =Browser(“Google”).Page(“Google”).Image(“Happy Holidays from Google!”).Object.currentStyle.display if disvalue =”block” then print...

Here is the way to disable add-ons window which appears every time when selenium scripts are run on Custom Firefox Profile. Close all instances of Firefox browser and delete the following files from the Custom Profile folder, this should reset Extension Manager and disable add-ons pop-up: extensions.cache extensions.ini extensions.rdf compatibility.ini This Add-ons pop-up will not displayed the next time you run selenium scripts. To find the Firefox profile,  type in cmd run prompt "%APPDATA%\Mozilla\Firefox\Profiles\"  press enter

It is impossible to automate all testing; the first step to successful automation is to determine what test cases should be automated first. The benefit of automated testing is correlated with how many times a given test can be repeated. Tests that are only performed a few times are better left for manual testing. Good test cases for automation are those that are run frequently and require large amounts of data to perform the same action. You can get the most benefit out of your automated testing efforts by automating:       Repetitive tests that run for multiple builds    Tests that are highly subject to human error       Tests that require multiple data sets        Frequently-used functionality that introduces high risk conditions        Tests that run on several different hardware or software platforms and configurations      ...

Common vi Commands Have a look at this list of common vi commands (there are many more, but these will at least allow you to get some basic work done). Then we'll do one more exercise before moving on. Note: As with all of Linux, vi commands are case sensitive. Positioning the Cursor � Move cursor one space right. � Move cursor one space left. � Move cursor up one line. � Move cursor down one line. ctrl-F Move forward one screen. ctrl-B Move backward one screen. $ Move cursor to end of line. ^ Move cursor to beginning of line. :1 Move to first line of file :$ Move to last line of file / Search for a character string. ? Reverse search for a character string. x Delete the character at the cursor position. dd Delete the current line. p Paste data that was cut with x or dd commands. u Undo.