Sunday, May 26, 2013

live cricket streaming

Monday, December 17, 2012

HP QTP Latest Version – Unified Functional Testing (UFT) 11.5


HP would soon be launching the latest version of QuickTest Professional (QTP). This new version of QTP will be called HP Unified Functional Testing (UFT) 11.5. Below is the sneak preview of some of the important new features that will be available in UFT 11.5


 

1) What is UFT 11.5?

The new version of HP QTP is being called HP Unified Functional Testing 11.5 (UFT 11.5). UFT 11.5 is actually a combination of HP QTP (for testing GUI) and HP Service Test (for testing API).
HP UFT new IDE

HP UFT Insight
Image Courtesy: HP Webinar Slides

What is HP UFT 11.5


2) Brand New Modern IDE

This point has been discussed so many times at many forums. QTP’s IDE lacked the punch when compared to many modern IDE’s like Eclipse, Microsoft Visual Studio etc. It lacked many must have features that were there in many IDEs available in the market. With UFT 11.5, HP will be introducing a brand new modern IDE, which will
a) have a new IDE aligned with modern dev IDEs (like Eclipse).
b) have many new features such as script editing, coding, MDI, checkpoints, auto completion etc

3) Image Based Automation – Using HP UFT Insight

With what I have understood, this seems to be a real killer. HP claims that, using HP UFT insight, you can simply recognize controls in the application by their appearance. This feature would enable you to record any object displayed on the screen, even if UFT is not able to recognize the Object’s technology.

4) Integration with Open Source CI Systems

This is another very good feature that has been implemented in UFT 11.5. This was one of the key drawbacks due to which QTP was not considered a good tool for automation in Agile Projects. With this new feature, you would be able to -
a) integrate UFT with popular CI systems like Jenkins.
b) automatically execute smoke and regression test cases repeatedly as part of nightly builds.


5) HP UFT Mobile – Extended Support for Mobile Testing

As part of UFT 11.5, HP will be providing lot of new features in mobile testing, where you will be able to -
a) write agnostic scripts, which once written can be used on multiple devices.
b) test your scripts on simulators as well as real devices.
HP UFT Mobile
Image Courtesy: HP Webinar Slides


Apart from these major features, there are lots of other features such as pdf checkpoints, graphic UI – canvas, workflows support thanks to integration to QC / ALM, support for latest technologies – Qt apps, Flex, more than 20 new versions etc.
All these new features can be explored when HP releases the trial version of UFT 11.5. The trial version should be available by the end of December 2012.
For more information on the above points, refer the HP Webinar Slides.

Saturday, June 23, 2012

Function: HighLightTextPresentOnPage


Function HighLightTextPresentOnPage(byval objpage , byval Textvalue )
On error resume next
REM ——- Create child object description
Set childobj = Description.Create()
childobj("micclass").value="WebElement"
childobj("html tag").value=".*[A-Za-z0-9].*"
childobj("outertext").value =Textvalue
REM  ———-Create ALL child object
set allobj = objpage.ChildObjects(childobj)
 REM here highlight method we will use that is in build in QTP for object
For i=1 to allobj.count-1
    allobj.Item(i).HighLight
 Wait 5
Next
           If allobj.count > 0 then
              HighLightTextPresentOnPage = true
     Wait 5
           Else
              HighLightTextPresentOnPage = false
           End if
             On Error GoTo 0
End Function

 

Friday, September 9, 2011

Wednesday, April 13, 2011

Watch Live Cricket Streaming free online

Cricket Live streaming

Sunday, March 6, 2011

Remove Password Protected Symantec Antivirus

Norton AntiVirus Clients or Symantec AntiVirus Clients (especially Corporate Edition Clients) can be installed as managed client by a Symantec AntiVirus Server. When a Symantec AntiVirus Client is managed, it will prompt for password when uninstalling client via a local computer Control Panel (Add or Remove Programs) applet. If you don’t know or forget the password, then the client is not able to uninstall or remove the software.

In the cases where Symantec AntiVirus server has been taken down and no longer exist, or the client computer has no access to company network, or the default client uninstall password does not work, the following hack will enable you to remove Symantec Antivirus without using a password:

1. Open Registry Editor (regedit).
2. Navigate to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LANDesk\VirusPro tect6\CurrentVersion\Administrator Only\Security\
3. Change the value for useVPuninstallpassword key from 1 to 0.
4. Exit Registry Editor and now you can uninstall Symantec AntiVirus Client.

The trick should work on most version of Symantec AntiVirus client or Norton AntiVirus Client, including version 7, 8, 9 or 10
____________________________________________________________

Remove Symantec Live Update in Windows Xp
Just follow the below steps mention.

1) Click on Start Menu--> Then select Run.

2) In the Run dialog box, type the following text: regedit

3) Click OK.

4) In the Registry Editor, navigate to the following key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

5) Select and delete the LiveUpdate key.


--------------------------------------------------------------------------------

Wednesday, November 17, 2010

Error Guessing

Error Guessing is a test case design technique where the tester has to guess what faults might occur and to design the tests to represent them.

Purpose



The purpose of error guessing is to focus the testing activity on areas that have not been handled by the other more formal techniques, such as equivalence partitioning and boundary value analysis. Error guessing is the process of making an educated guess as to other types of areas to be tested.

For example, educated guesses can be based on items such as metrics from past testing experiences, or the tester's identification of situations in the Functional Design Specification or Detailed Design Specification, that are not addressed clearly.

Examples



Though metrics from past test experiences are the optimum basis for error guessing, these may not be available. Examples of error prone situations include:

initialization of data, (e.g., repeat a process to see if data is properly removed),

wrong kind of data, (e.g., negative numbers, non-numeric versus numeric),

handling of real data, (i.e., test using data created through the system or real records, because programmers tend to create data that reflects what they are expecting),

error management, (e.g., proper prioritization of multiple errors, clear error messages, proper retention of data when an error is received, processing continues after an error if it is supposed to),

calculations, (e.g., hand calculate items for comparison),


restart/recovery, (i.e., use data that will cause a batch program to terminate before completion and determine if the restart/recovery process works properly),


proper handling of concurrent processes, (i.e., for event driven applications, test multiple processes concurrently).


Tuesday, October 19, 2010

QTP Script For Connecting to Database

QTP Script for connecting to MS Access.

Option Explicit
Dim con,rs
Set con=createobject("adodb.connection")
Set rs=createobject("adodb.recordset")
 con.provider="microsoft.jet.oledb.4.0"
 con.open"d:testdata.mdb"
 rs.open"select*from emp",con
Do while not rs.eof
VbWindow("Form1").VbEdit("val1").Set rs.fields("v1")
VbWindow("Form1").VbEdit("val2").Set rs.fields("v2")
VbWindow("Form1").VbButton("ADD").Click
rs.movenext Loop
The database we are using here is MS Access.Before running this script create a table in MS Acess.
 In the above script I used table called "emp" and column names as "v1" and "v2". "d:testdata.mdb" is path of the table which we created. The main use of this script is to use testdata of table(which is in database) in the application. In the above script we are passing values from database to Textboxes in Windows Application.

Similarly script for connecting to other 2 databases are

 QTP Script for connecting to sqlserver.

Option Explicit
 Dim con,rs
Set con=createobject("adodb.connection")
Set rs=createobject("adodb.recordset") con.open"provider=sqloledb.1;server=localhost;uid=sa;pwd=;database=testdata"
rs.open"select*from emp",con
Do while not rs.eof
VbWindow("Form1").VbEdit("val1").Set rs.fields("v1")
VbWindow("Form1").VbEdit("val2").Set rs.fields("v2")
VbWindow("Form1").VbButton("ADD").Click
 rs.movenext
 Loop

Script for connecting to oracle

Option Explicit
Dim con,rs
Set con=createobject("adodb.connection")
Set rs=createobject("adodb.recordset")
con.open"provider=oraoledb.1;server=localhost; uid=scott;pwd=tiger;database=testdata" rs.open"select*from emp",con
Do while not rs.eof
VbWindow("Form1").VbEdit("val1").Set rs.fields("v1")
VbWindow("Form1").VbEdit("val2").Set rs.fields("v2")
VbWindow("Form1").VbButton("ADD").Click
rs.movenext
Loop
This is the way u connect to database in QTP and get the values from database.

Saturday, October 16, 2010

Vbscript Advanced Tutorial

Vbscript Advanced Tutorial#1



Vbscript Advanced Tutorial#2

VB Script Video Tutorial Series

VBScript Tutorial 1-Overview and Output



VBScript Tutorial 2 - Variables and Arrays



VBScript Tutorial 3 - Conditional Statements



VBScript Tutorial 4 - Loops



VBScript Tutorial 5 - Procedures



VBScript tutorial 6- Replace and Round



VBScript tutorial 7- Return and Random



VBScript tutorial 8- Case, Trim , and Reverse




Saturday, October 9, 2010

Characteristics of Good Testers

Is inquisitive

Has functional/business knowledge

Is detail-oriented

Is open-minded

Has a good personality

Has a technical background, but does not want to be a programmer

Has testing experience

Is a team player

Is flexible

Is self-reliant

Is self-starting

Has a positive attitude

Is logical

Handles stress well

Is a quick thinker

Knows specific tools

Has good common sense

Is politically astute

Has a sense of humor

Understands the software development lifecycle

Levels (Stages) of Test Planning


Levels (Stages) of Test Planning
Test planning can and should occur at several levels or stages. The first plan to consider is the Master Test Plan (MTP), which can be a separate document or could be included as part of the project plan. The purpose of the MTP is to orchestrate testing at all levels. The IEEE Std. 829-1998 Standard for Software Test Documentation identifies the following levels of test: Unit, Integration, System, and Acceptance. Other organizations may use more or less than four levels and possibly use different names. Some other levels (or at least other names) that we frequently encounter include beta, alpha, customer acceptance, user acceptance, build, string, and development. In this book, we will use the four levels identified in the IEEE and illustrated in figure 3-1.




Figure 3-1: Levels of Test Planning
Key Point Test planning CAN'T be separated from project planning.
All important test planning issues are also important project planning issues.
The test manager should think of the Master Test Plan as one of his or her major communication channels with all project participants. Test planning is a process that ultimately leads to a document that allows all parties involved in the testing process to proactively decide what the important issues are in testing and how to best deal with these issues. The goal of test planning is not to create a long list of test cases, but rather to deal with the important issues of testing strategy, resource utilization, responsibilities, risks, and priorities.
Key Point Test planning SHOULD be separated from test design.
In test planning, even though the document is important, the process is ultimately more important than the document. Discussing issues of what and how to test early in the project lifecycle can save a lot of time, money, and disagreement later. Case Study 3-1 describes how one company derived a great benefit from their Master Test Plan, even though it was never actually used.
Case Study 3-1: If the Master Test Plan was so great, why didn't they use it?


The "Best" Test Plan We Ever Wrote
I once had a consulting assignment at a major American company where I was supposed to help them create their first ever Master Test Plan. Following up with the client a few months later, the project manager told me that the creation of the Master Test Plan had contributed significantly to the success of the project, but unfortunately they hadn't really followed the plan or kept it up to date. I replied, "Let me get this straight. You didn't use the plan, but you felt that it was a major contributor to your success. Please explain." The project manager told me that when they began to fall behind, they dispensed with much of the project documentation, including the test plan (sound familiar?). But because they created the plan early in the project lifecycle, many testing issues were raised that normally weren't considered until it was too late to take action. The planning process also heightened the awareness of the importance of testing to all of the project participants. Now, I believe that keeping test plans up to date is important, so that's not the purpose of telling you this story. Rather, I'm trying to stress the importance of the testing process, not just the document.
— Rick Craig



Key Point "We should think of planning as a learning process - as mental preparation which improves our understanding of a situation… Planning is thinking before doing."
- Planning, MCDP5 U.S. Marine Corps
Key Point Ike said it best: "The plan is nothing, the planning is everything."
- Dwight D. Eisenhower
In addition to the Master Test Plan, it is often necessary to create detailed or level-specific test plans. On a larger or more complex project, it's often worthwhile to create an Acceptance Test Plan, System Test Plan, Integration Test Plan, Unit Test Plan, and other test plans, depending on the scope of your project. Smaller projects, that is, projects with smaller scope, number of participants, and organizations, may find that they only need one test plan, which will cover all levels of test. Deciding the number and scope of test plans required should be one of the first strategy decisions made in test planning. As the complexity of a testing activity increases, the criticality of having a good Master Test Plan increases exponentially, as illustrated in Figure 3-2.

Figure 3-2: Importance of Test Planning

Saturday, September 25, 2010

QTP Certification - Review your Skills: Q. 21 to 30

Q. 21: Object Spy can be found in __________ menu.

A. Tool

B. Tools

C. Task

D. Tasks
<<<<<< =================== >>>>>>
Q. 22: The ________________ displays the open documents side-by-side.

A. Tile Vertically

B. Tile Horizontally

C. Cascade

D. Tile Cascade
<<<<<< =================== >>>>>>

Q. 23: For opening the Quick Test Professional Help we can use _________

A. F3

B. F5

C. F1

D. F2

<<<<<< =================== >>>>>>

Q. 24: If QTP cannot find any object that matches the description, or if it finds more than one object that matches, QuickTest may use the ___________________ mechanism to identify the object.

A. Ordinal Identifier

B. Index Identifier

C. Smart Identification

D. Assistive Identification


<<<<<< =================== >>>>>>

Q. 25: You can configure the _________ and ___________.properties that QuickTest uses to record descriptions of the objects in your application

A. Mandatory, assistive, and ordinal identifier
B. Mandatory, required, and ordinal identifier
C. Smart, assistive, and ordinal identifier
D. Index, assistive, and ordinal identifier


<<<<<< =================== >>>>>>

Q. 26: The ___________ property set for each test object is created and maintained by QuickTest.

A. Run-Time Object
B. Test Object

C. Smart Identification Object
D. Assistive Object


<<<<<< =================== >>>>>>


Q. 27: You can access and perform ______________ methods using the Object property.


A. Run-Time Object

B. Test Object

C. Smart Identification Object

D. Assistive Object

<<<<<< =================== >>>>>>

Q. 28: You can view or modify the test object property values that are stored with your test in the _______________

A. Information Pane
B. Data Table
C. Information Pane & Data Table Both
D. Object Properties & Object Repository dialog box.


<<<<<< =================== >>>>>>


Q. 29: You can retrieve or modify property values of the test object during the run session by adding _______________ statements in the Keyword View or Expert View.


A. GetROProperty & SetROProperty
B. GetTOProperty & SetTOProperty
C. GetTOProperty & SetROProperty

D. GetROProperty & SetTOProperty

<<<<<< =================== >>>>>>

Q. 30: If the available test object methods or properties for an object do not provide the functionality you need, you can access ______________ of any run-time object using the Object property.

A. The internal methods and properties
B. The mandatory methods and properties
C. The selective methods and properties
D. The assistive methods and properties

Correct Answers to Questions - Q.21 to Q 30 are as under:


QTP Certification - Review your Skills: Q. 11 to 20


Q. 11: Using the Object Spy, you can view
A. The run-time or test object properties and methods of any object in an open application.
B. The run-time or test object properties of any object in an open application.
C. The test object properties and methods of any object in an open application.
D. The run-time object properties and methods of any object in an open application.
<<<<<< =================== >>>>>>
Q. 12: There are ________ object type filters in Object spy dialog box.
A. Two

B. Three

C. Four

D. Five
<<<<<< =================== >>>>>>
Q. 13: In the Object Spy window, in the Properties Tab
A. Copying of Properties and its values is possible with CTRL+C
B. Copying of Properties and its values is possible by right clicking on it and choosing copy.
C. Copying of Properties and its values is possible with both A. and B. methods
D. Copying of Properties and its values is possible is not possible
<<<<<< =================== >>>>>>
Q. 14: In the Object Spy window, in the methods Tab
A. Copying of Methods is possible with CTRL+C
B. Copying of Methods is possible by right clicking on it and choosing copy.
C. Copying of Methods is possible with both A. and B. methods
D. Copying of Methods is possible is not possible
<<<<<< =================== >>>>>>
Q. 15: Object Spy dialog box
A. Can be resized
B. Cannot be resized

<<<<<< =================== >>>>>>

Q. 16: The ___________ are the highest level of the test hierarchy in the Keyword view.
A. Tests
B. Steps

C. Call to Actions

D. Actions
<<<<<< =================== >>>>>>
Q. 17: You can copy and paste or drag and drop actions to move them to a different location within a test
A. True

B. False
<<<<<< =================== >>>>>>
Q. 18: You can print the contents of the Keyword View to your Windows default printer (and even preview the contents prior to printing.
A. True

B. False
<<<<<< =================== >>>>>>
Q. 19: In the Keyword View, you can also view properties for items such as checkpoints.
A. True

B. False
<<<<<< =================== >>>>>>
Q. 20: In the step Browser > Page > Edit > Set "Genius", identify container object(s)
A. Browser

B. Edit

C. Page

D. Both Browser & Page


Correct Answers to - Q.11 to Q 20 are as under:

QTP Certification - Review your Skills: Q. 1 to 10

Objective Type / Multiple Choice Questions on QTP - QuickTest Professional under the Series

(Quickly Review Your QTP Skills before appearing for HP Certification Exam)

Set of 10 Questions

Q. 1: You can manage the test actions and the test or function library steps using the _________ menu commands

A. File

B. Edit

C. Automation

D. Tools

<<<<<< =================== >>>>>>

Q. 2: To expand all the steps in the keyword view which option you would use from the View menu.
A. Expand

B. Expand All

C. Expand Items

D. Expand Rows

<<<<<< =================== >>>>>>

Q. 3: What is the shortcut key to open a Step Generator?

A. F2

B. F5

C. F6

D. F7

<<<<<< =================== >>>>>>

Q. 4: Function Definition Generator in found in which menu option.

A. File

B. Tools

C. Insert

D. View

<<<<<< =================== >>>>>>

Q. 5: The shortcut keys for Record, Stop and Run respectively are

A. F3, F4, F5

B. F4, F3, F5

C. F4, F5, F3

D. F3, F5, F4

<<<<<< =================== >>>>>>

Q. 6: What is the shortcut key for opening an Object Repository?

A. Alt+R

B. Shift+R

C. Ctrl+R

D. Shift+O+R

<<<<<< =================== >>>>>>

Q. 7: Shortcut key to Insert/Remove a breakpoint is

A. F9

B. F8

C. Ctrl+b

D. Shift+b

<<<<<< =================== >>>>>>

Q. 8: The __________ runs only the current line of the script. If the current line calls a method, the method is displayed in the view but is not performed.


A. Step over

B. Step out

C. Step into

D. Step Till


<<<<<< =================== >>>>>>

Q. 9: The ________ runs only the current line of the script. When the current line calls a method, the method is performed in its entirety, but is not displayed in the view.

A. Step Over

B. Step Out

C. Step Into

D. Step Till

<<<<<< =================== >>>>>>

Q. 10: What is the shortcut key to clear all Breakpoints?

A. Ctrl+Shift+F9

B. Shift+Ctrl+F9

C. Alt+Shift+F9

D. Alt+Ctrl+F9

Essential Elements of Testing Web Applications

Today everyone depends upon websites for business, education and trading purpose. Websites are related to the internet. It is believed that no work is possible without internet today. There are so many types of users connected to the websites who need different type of information. So, websites should respond according to the user requirements. At the same time, the correct behaviour of sites has become crucial to the success of businesses and organizations and thus should be tested thoroughly and frequently.

Here we are discussing various methods to test a website. However, testing a website is not an easy job since we have to test not only the client-side but also the server-side. With this approach we can completely test a website with minimum number of errors.


Introduction to Web Testing:
The client end of the system is represented by a browser, which connects to the website server via the Internet.The centerpiece of all web applications is a relational database which stores dynamic contents. A transaction server controls the interactions between the database and other servers (often called "application servers"). The administration function handles data updates and database administration.



According to the above Architecture of Web Applications, It is evident that we need to conduct the following tests to ensure the suitability of web applications.

1) What are the expected loads on the server and what kind of performance is required under such loads. This may include web server response time, database query response times.

2) What kind of browsers will be used?

3) What kinds of connection speeds will they have?

4) Are they intra-organization (thus with likely high connection speeds and similar browsers) or Internet-wide (thus with a wide variety of connection speeds and browser types)?

5) What kind of performance is expected on the client side (e.g., how fast should pages appear, how fast should animations, applets, etc. load and run)?


There are many possible terms for the web application development life cycle including the spiral life cycle or some form of iterative life cycle. A more cynical way to describe the most commonly observed approach is to describe it as the unstructured development similar to the early days of software development before software engineering techniques were introduced. The "maintenance phase" often fills the role of adding missed features and fixing problems.



We need to have ready answers to the following questions:

1) Will down time for server and content maintenance / upgrades be allowed? How much?

2) What kinds of security (firewalls, encryptions, passwords, etc.) will be required and what is it expected to do? How can it be tested?

3) How reliable the Internet connections are? And how does that affect backup system or redundant connection requirements and testing?

4) What processes will be required to manage updates to the website's content, and what are the requirements for maintaining, tracking, and controlling page content, graphics, links, etc.?

5) Will there be any standards or requirements for page appearance and/or graphics throughout a site or parts of a site?

6) How will internal and external links be validated and updated? How often?

7) How many times the user login and do they require testing?

8) How are CGI programs, Applets, Javascripts, ActiveX components, etc. to be maintained, tracked, controlled and tested?

Functional or Black Box Testing of Web Applications

Web Browser-Page Testing:
This type of test covers the objects and code that executes within the browser, but does not execute the server-based components. For example, JavaScript and VB Script code within HTML that does rollovers, and other special effects. This type of test also includes field validations that are done at the HTML level. Additionally, browser-page tests include Java applets that implement screen functionality or graphical output.


For web browser testing we can create test cases using following guidelines:

1) If all mandatory fields on the form are not filled then it will display a message on pressing a submit button.

2) It will not show the complete information about sensitive data like full credit card number, social security number (SSN) etc.

3) Hidden passwords.

4) Login by the user is must for accessing the sensitive information.

5) It should check the limits of all the fields given in the form.


Transaction Testing:
In this testing, test cases are designed to confirm that information entered by the user at the web page level makes it to the database, in the proper way, and that when database calls are made from the web page, the proper data is returned to the user.


Conclusion:
For trouble-free operation of a website we must follow both non-functional and functional testing methods. With these methods one can test the performance, security, reliability, user interfaces etc. which are the critical issues related to any website.