Skip to main content

JavaScript - Overview

Recently I have attended a session on JavaScript basics and very eager to know something we don't know. I am here to discuss some points about JavaScript.

-- Basically JavaScript is an Object-Oriented Scripting Language but no relation with Java. Only name have relation.
-- Engineer from Netscape company created Scripting Language "Mocha" for their browser Netscape Navigator. Then renamed as LiveScript.
-- Then Microsoft created their implementation of Scripting Language for their browser and named as JScript for IE.
-- Then ECMA(European Computers Manufacturers Association) took and standardized as ECMA Script. But for marketing purpose they named as JavaScript because Java is familiar in the world.
-- We can also create classes using Prototypes like

  1. function myClass(){
  2.     //some definition
  3. }
  5. myClass.prototype.function = myFunc1() {
  6.     // Some function definition
  7. }
-- Dynamic variable types - No static types of variables. All are variants here. No need to worry about variable types.
-- Anonymous functions ie. Assigning a function definition to a variable without function name.
  1. var myVariable = function() {
  2.    //some definition
  3. }
-- Closures - Nested functions. Inner function will access the outer function's details but Outer function can't access inner function's details.
-- The Scripts are executed by JavaScript engine provided by respective browsers.
    IE - Chakra
    Mozilla - TraceMonkey, JagerMonkey
    Chrome - V8 engine
    Safari - Nitro
-- These Engines are called as Interpreter OR you can take it as JavaScript Virtual Machine.

Hope this will give idea about JavaScript. I will continue this post later....


  1. Thanks for sharing great information in your blog. Got to learn new things from your Blog . It was very nice blog to learn about Selenium


Post a Comment

Popular posts from this blog

QTP - Object Identification - Prerequesties

While starting a new project or proof of concept or after new QTP installation, we would face the issue in identifying objects as QTP built objects like WinList, WebEdit, etc.; instead everything will be identified as WinObject.

Here are some steps to ensure you did the environment setup RIGHT before start automating.
Did you enabled required Add-ins only while launchingDid you selected "Record >> Record and Run Settings" - This should be based on what type of application you are working with
Windows app - Windows >> Record and run test on any windows applications. Web app - Web >> Record and run test on any open browser.
Did you tried to launch UFT/QTP and then AUT.If its web, ensure browser zoom level set to 100%Try disabling the protected mode in IE for web.Launch UFT and AUT using RUN AS ADMINISTRATORAlso see the Object Identification Methods if you are interested.

Change IE Browser ZOOM settings

Lot of UI automation testers could have faced this problem as we could change the zoom settings while operating manually for our convenience and forgot to reset to 100%.
But our QTP and some other related tools would operate the browser perfectly if browser zoom is 100%. So wee need to change the zoom before start to run the scripts. Its better to have a code snippet in our framework to change this zoom setting right?
Here we go...

1. We can simply change the Registry values before Invoking IE
Function ChangeRegistry Dim objShell Set objShell = CreateObject("WScript.Shell")  objShell.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Zoom\ZoomFactor", "100000", "REG_DWORD" Set objShell = Nothing EndFunction This option is very useful. But in real time, lot of customers could have restricted write access to windows registry. So we can try other options.

2. Use IE COM object and Change Settings
Function ChangeIEZoom Dim intZoomLevel, objIE  intZoo…

QTP - Common error messages

Always I am seeing  many of my friends asking for help if any error occurs while running script in QTP without googling for help. How much troubleshooting you guys are doing will directly reflect your knowledge on the tool. I agree, no one knows each and every error occurs in the software. But we can improve our knowledge by googling and doing workarounds...
Whenever the question "How much level you know QTP?" arrows me, always I am comfortable with the answer "below 10%". But after answered, my mind will have an inner thought like, What are the things I have to learn to fulfill the answer I have told because I never used lot of features in QTP.

Here I am listing out some of the errors, situations and what might be the original issue things etc. I hope this will give you some ideas to improve your debug ability and to solve your errors. Kindly correct me If I am wrong in any point.

Type mismatch:
- Mostly doing operations with different data types without doing type co…