The real answer to this is - it depends! on the context, on the need, on necessity, on motivation, on relevance, and even on geography...Is it absolutely necessary - definitely not! Should you go for it - may be. Why? - read the first line.OK, now the real reasons.What a formal Certification (like ISTQB) does is a lay a foundation about the basic process of Software Testing, that anyone who works in this field is expected to know - you cannot build an Empire state building with only 6 inches of slab as foundation.But I feel that the course-ware (syllabus) is mostly irrelevant in today's real world scenario, though some of it can be pretty useful even in the advanced stages of your careers. It is like the basics of engineering that we all studied but rarely used, but it was still important at that point of our lives.So, the point is if you are just starting your career in testing - most of the young people in India and some Asian countries fall in this category - it might be worthwhile to go for it. Because most testers start their careers in testing without any formal training in the different aspects of testing, and they keep struggling until they develop that knowledge and understanding. So all this certification can do is speed-up that learning a bit, by pointing you in the right direction.But for people who have credible experience it may not be worth spending a weekend that you could have spent on taking your wife shopping! For people in mature markets like US and EU, this certification has already lost all relevance; and for those who want to 'statistically' refuse, here is a good article that can help you do just that - http://chrismcmahonsblog.blogspot.in/2010/10/ignoring-certification-with-numbers.htmlA weekend is all it takes to clear these certifications - but its no cake-walk either as the failure rate is quite high, though the material is quite abundantly (and freely) available online.One exam tip for those who want to take the plunge - don't sweat too much over the 'Standards' even if you get the itch to do so, because not much gets asked about those anyways!
Often we are faced with an issue when QTP cannot identify the objects in a web page.So, listed below are some of the things we should try (in no particular order). This is not an exhaustive list (yet), but this could give some pointers or options that you may not have tried.Bear in mind that Uninstall & Re-install should always be the last option - no matter how tempting it is ;-)• Check the compatibility of QTP with OS and IE.
• IE Browser > Tools > Internet Options > Disable the "Enable Tabbed Browsing" checkbox.
This worked for me on Windows 7 with IE 8 and QTP 11 - Jun2012
• IE Browser > Tools > Internet Options > Disable the "Enable Protected Mode" checkbox. If Protected Mode is required to be set as ON, then a QTP Patch QTPWEB_00073 is needed.• Sometimes QTP identifies objects on the main browser page but not on the child page. This may happen when web pages have Web 2.0 elements embedded in them. These Web 2.0 apps are not based on new technology but instead on a set of cumulative toolkits or frameworks, like AJAX, Dojo, Yahoo User Interface (YUI) and GWT. In such cases, we have to enable/install Web 2.0 toolkit add-ins in QTP. Refer the following links in such a case:• UAC (User Account Control) has to be disabled on Vista and for Windows7 has to be set to "Never Notify"
• If QTP's BHOManager Addon is disabled in IE, even this can cause issues, and has to be Enabled.
To enable it go to IE > Tools > Addons > BHOManager Class - Enable
• IE Browser > Tools > Internet Options > Advanced > Browsing > Enable Third Party Browser Extensions
• For FireFox, ensure that QTP Plugin is available in the Extensions section of the Addons in Fox
• Ensure that the Browser is running in 32-bit mode, even if the machine is 64-bit because QTP is a 32-bit app. To ensure this during run-time, pass the complete path for the browser (the one with (x86)) via SystemUtil.Run
We often work with a lot of COM objects, and it may cause errors if we define them incorrectly, so, here is a list of commonly used COM objects.
Set oQTPApp = CreateObject ("QuickTest.Application")Set oWSHNetwork = CreateObject ("WScript.Network")Set oWSHShell = CreateObject ("WScript.Shell")Set oShell = CreateObject ("Shell.Application")Set oFSO = CreateObject ("Scripting.FileSystemObject")Set oWMI = GetObject ("WinMgmts:")Set oWMIService = GetObject ("WinMgmts:{ImpersonationLevel=Impersonate}!\\.\Root\Cimv2") ' ''The "." can be replaced by compturename
Set oADOConn = CreateObject ("ADODB.Connection")Set oADORecSet = CreateObject ("ADODB.Recordset")Set oDeviceReplay = CreateObject ("Mercury.DeviceReplay")Set oIE = CreateObject ("InternetExplorer.Application")Set oDic = CreateObject ("Scripting.Dictionary")Set oWinHTTP = CreateObject ("WinHTTP.WinHTTPRequest.5.1")Set oXmlDoc = CreateObject ("Microsoft.XmlDom")Set oXml2Doc = CreateObject ("MSXml2.DOMDocument.5.0")Set oSoapClient = CreateObject ("MSSoap.SoapClient")Set oCal = CreateObject ("MSCAL.Calendar")Set oQuattro = CreateObject ("QuattroPro.PerfectScript")Set oWPerfect = CreateObject ("WordPerfect.PerfectScript")Set oRandom = CreateObject ("System.Random")Set oArrList = CreateObject ("System.Collections.ArrayList")Set oSortList = CreateObject ("System.Collections.SortedList")Set oiTunes = CreateObject ("iTunes.Application")Set oWMPlayer = CreateObject ("WMPlayer.OCX")Set oWM7Player = CreateObject ("WMPlayer.OCX.7")Set oRealPlayer = CreateObject ("rmocx.RealPlayer G2 Control.1")Set oFSDialog = CreateObject ("SAFRCFileDlg.FileSave")Set oFODialog = CreateObject ("SAFRCFileDlg.FileOpen")Set oDialog = CreateObject ("UserAccounts.CommonDialog")Set oWOL = CreateObject ("UltraWOL.ctlUltraWOL")Set oSearcher = CreateObject ("Microsoft.Update.Searcher")Set oEmail = CreateObject ("CDO.Message")Set oInet = CreateObject ("InetCtls.Inet.1")Set oExcel = CreateObject ("Excel.Application")Set oOutlook = CreateObject ("Outlook.Application")Set oPpt = CreateObject ("PowerPoint.Application")Set oWord = CreateObject ("Word.Application")Set oHTML = CreateObject ("HTMLFile")
