Saturday, July 25, 2009

BELUR TRIP



This trip was planned mainly by Appa and Amma(MIL & FIL) . They wanted to do Panchamrutha abhisheka for Lord Channakeshava. Appa and amma went to Belur on 18th itself and we all had to leave blr on 19th early morning. As Planned bellige bellige 4:30 yeddu ready aagi we picked up Sumukh (my nephew) and ended up starting from blr at 6AM…every one knows bcoz of whom :-)

Like my wife said my family went to belur in a highly fashioned Chuffer driven Ikon i.e ME..This was also my first long drive…….I never thought this would be so fascinating…..no breakfast and no coffee and nothing till we reach Belur……on the way few stops for peeing n nothing else J. We took NICE road and reached tumkur road in just abt 10 min’s as I crusied at 130 kmph and unfortunately the same old traffic jam in Tumkur Road. It took close to 1 hr to cover 2 kms and that too I had to drive on wrong lane taking lot of risk…I had to thank Big brother (Bus) who was driving in front of me and shielding me.
With lots of curse from the rest of the crowd coming form the other side. I reached Kunigal cross.
Kunigal Road was one more mess……it’s a very small word for the risk what I had to take while driving on that road……first the road is so narrow and the road being completely chipped with chisel J I felt I was driving on Lays…guess u know wat lies ahead of me. I anticipated kunigal to better than wat it was having heard of UB Kudre Laya (Breading and Training Ground for horses) and not to forget Kunigal Kere (lake) which is more or less heard from every kannadiga as a Janapada geethe….gothilla andre keli----moodal kunnigal kere, noodokondhu eyebogha, moodi barthane chandirama….rest please refer to Google search Thank You :-).

After this great experience the drive till Hassan was better with landscape being good and a pleasant weather adding much life to our drive and of course Rafi and Mukesh singing for us all the way one could not have asked for more. Till Hassan I was the most content son on earth with my parents enjoying the driving my nephew to asking me to speed on and my Son on Roop’s lap, Road being good weather giving the charm I was heart content.

Then we entered the City of Gowda’s…..what u guys are guessing is right ….Yours truly HASSAN. The roads are as bad as the owners of the city. I had a different expectation of Hassan all together only to be rain washed with in few seconds after entering the city. Yenappa yellige bandvi and yake bandhvi anisthu that too on the outskirts of the city. Just imagin the plight of people who travel daily. Hope their baks are better.

However this was short lived as we hit the Belur Road. This was the best stretch I drove other than our own NICE road. The entire strectch of Belur road of 20 odd kilometers had a beautiful canopy like the one we used to see on Nanda Road (Jayanagar). We reached Belur at about 9:45 AM. To cover 240 kms, I took close to 4 hrs. Not so bad for the first long drive. By gods grace every one were ok with out any back problem. We had a quick referesh at IB Belur. My Son enjoyed the lavish space at IB. We had Idli and coffee and had to march for the temple where we had given for Abhisheka.

It’s a delight to see Belur in rain. The true value for the Archtectural Marval is so very visible during rains. One u enter the Prangana of the temple the feeling what you get is out of the world. Every one should experience this at least once in their life time. With light drizzle and cool breeze blowing its simply marvalus to be there in such a place of my heritage. I don’t have words to describe how I felt when I was standing and looking around the temple. I will get back to this later.

We had given for Panchamrutha Abhisheka….hope u know wat is Panchamrutha…just kidding…..The idol of lord Channakeshva is 12 feet tall and to see the abhisheka standing at a distance of 10 feet is just amazing. It was a pleasure to watch the abhisheka. After Panchamrutha abhisheka since this is the idol of Mohini Avathara of Lord Vishnu the god will be decorated with Arishina (Turmaric powder). It’s a heavenly treat to be part of such a great holy occurrence. In kannada I can say Thiddi theedidha devru sadha kannige kattidha hage iruthe. Adhu yentha adhbutha …..Sorry I cant explain in English…..forgive me please…..
Check the pic to know how beautiful lord looks when he is decorated with Arishina.


Now comes the next wonder of the world…..Far more than the seven wonders…..Only one in a 100 million may get the opportunity like what Shreyas got….he was taken inside the Garbha gudi and he was made to touch the feet of lord Channakeshava. Very very lucky indeed. Next we went to Goddess Ranganayaki Temple. We gave goddess, sobalakki and offered our prayers. There too Shreyas got the special blessings from the godess by touching her feet. And you know what he asked…..Namma ammanige, namma appange erothara volle buddi kodappa…….I am sure my wife cant debate this :-).

Shreyas enjoyed the most once we started circling the temple. He did Ane banthondh aane by sitting on different elephant idols……and any god he sees he just could not stop doing namaskara……..Both his grand parents had the time of their life playing with him there……the prangana was so slippery still he wanted to walk in the rain and he did it…..he njoyed every bit it…….


U know what Shreyas checked his feet size with that of Kehava devru paada……I am not lieing…check the pic if u don’t trust me…….

I had my best buddy sumukh….he just could not stop asking questions on each and every step…..he was over moon on seeing the proceedings upclose and being part of it. He wants to make a design of Mantapa for his house like the one in the picture…….First step is already taken…pic is there check it out.....


He njoyed the most when Shreays and his one and only ever green Athe was wid him…..any questions athe was there to answer……


So lot of study was done on belur wid his athe….and few heart breaks while seeing the tarnished idols…. Will tell more when I write about Halebedu…..
We collected prasada and went to IB and had our lunch there…..Puliyogre, Belladha anna and Mosranna. Relaxed for a while and set for Halebeedu.

So from here on we had two cars…one for Appa and Amma, and other we all…..Shivu was driving the other car and I was driving my car. Appa came wid me and Roopa and Sumukha went with Amma. We can reach Halebedu either by a good road or by a bypass which is a bad road…..Shivu being expert driver who knows the place and being from chenraya patna…knowing that we have few patients on board took us in that bad road….thanks a ton for his forethought.

Halebedu was considered just for Shreyas and Sumuk. We wanted to show shreyas the Amba mami(Big Bull) & Sumukh the history of Hoysalas. This was the first time for sumuk and me. By the time we reached halebeedu shreyas was fast asleep after playing so much in Belur. Once we entered the halebeedu temple we could only see the destruction caused by Allaudin Khilji. Its really sad when u see Belur’s Beauty and come to Halebeedu to see the destruction. I felt it as Halu beedu instead of hale beedu. Its not just that the destruction of the temple but also our heritage. Not only is the destruction worrisome but also we can see the negligence of it.

My wife had warned Sumukh and me in advance about how it feels in halebeedu after visiting Belur. This came true when we saw it. The ones who destroyed the temple are barbarians……The way they have destroyed the temple is unimaginable….Its really hard to explain the destruction of such magnitude. You should have seen sumukhs reaction on seeing halebeedu. While feeling sad about this the only gud wat we saw was Shreays getting up and njoing the Amba Maami. As soon as he got up there was no stop on he doing namaskara to amba maami and showing that to his Thatha’s and aggi’s.

Then came the time to depart such a historical place. We started our return journey around 4:00PM. Sumukha went with Aggi and thatha in other car. Every one tired and slowly started dorwsing off one after the other….it was Kishor, Mukesh, Rafi and myself….even my slept off for some time…..(5 mins) J. Even I started feeling sleepy and then the hunt began for coffee….unfortunately I could not find even a single hotel or Dabha serving coffee…..Eventually I had to have T and survive……Between we shopped Cucumber near Hassas as its famus there…..and trust me u don’t find cucumber like that in Bangalore……

The worst phase of the trip started once I crossed Kunigal…..Its a stretch of around 25 kms and I had to drive in Dark…90% of the vehicles were using high beam and I could hardly see anything in the front…..In one place I could not notice a curve until it was too close and had to take sharp turn……. it was so hard that my dad started doing Japa so that we could reach home safe. Finally we reached Tumkur road and felt safe :-) …..In next few minutes we reached NICE road and by 8:30PM we reached home safe :-)
As this is my first non technical blog I find it really hard to write a blog like this.
Hope you guys enjoyed reading this blog……

Tuesday, July 21, 2009

QTP - Check Points

What’s Checkpoints for QTP?
A checkpoint verifies that expected information is displayed in your application while the test is running.
QuickTest Professional offers the following types of checkpoints:
Checkpoint Type Description Example of Use
Standard Checkpoint Checks values of an object’s properties. Check that a radio button is selected.
Image Checkpoint Checks the property values of an image. Check that the image source file is correct.
Table Checkpoint Checks information in a table. Check that the value in a table cell is correct.

How to add a standard checkpoint in your test ?
1. Start QuickTest and open your test.In the Open Test dialog box, locate and select your test, then click Open.
2. Save the test as Checkpoint. Select File > Save As. Save the test as Checkpoint.
3. Confirm that the Active Screen option is enabled.
If you do not see the Active Screen at the bottom of the QuickTest window, click the Active Screen button, or choose View > Active Screen.
4. Locate the page where you want to add a standard checkpoint. 5 Create a standard checkpoint.
In the Active Screen, right-click element in your application and choose Insert Standard Checkpoint.
6 Save the test.

How to add a page checkpoint to your test?
The page checkpoint checks that the number of links and images in the page when you run your test is the same as when you recorded your test.
1 Locate the page where you want to add a page checkpoint.
2 Create a page checkpoint.
Right-click anywhere in the Active Screen, and choose Insert Standard Checkpoint. The Object Selection – Checkpoint Properties dialog box opens. Note that this dialog box may include different elements, depending on where you click in the Active Screen.
3 Save the test.

Table and DB Checkpoints:
By adding table checkpoints to your tests or components, you can check that a specified value is displayed in a cell in a table on your application. By adding database checkpoints to your tests or components, you can check the contents of databases accessed by your application. The results displayed for table and database checkpoints are similar. When you run your test or component, QuickTest compares the expected results of the checkpoint to the actual results of the run session. If the results do not match, the checkpoint fails. You can check that a specified value is displayed in a cell in a table by adding a table checkpoint to your test or component. For ActiveX tables, you can also check the properties of the table object. To add a table checkpoint, you use the Checkpoint Properties dialog box. Table checkpoints are supported for Web and ActiveX applications, as well as for a variety of external add-in environments. You can use database checkpoints in your test or component to check databases accessed by your Web site or application and to detect defects. You define a query on your database, and then you create a database checkpoint that checks the results of the query. Database checkpoints are supported for all environments supported by QuickTest, by default, as well as for a variety of external add-in environments.There are two ways to define a database query:(a) Use Microsoft Query. You can install Microsoft Query from the custom installation of Microsoft Office.(b) Manually define an SQL statement.The Checkpoint timeout option is available only when creating a table checkpoint. It is not available when creating a database checkpoint

Checking Bitmaps:
You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area within an object. QuickTest captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk space.When you run the test or component, QuickTest compares the object or selected area of the object currently displayed on the Web page or application with the bitmap stored when the test or component was recorded. If there are differences, QuickTest captures a bitmap of the actual object and displays it with the expected bitmap in the details portion of the Test Results window. By comparing the two bitmaps (expected and actual), you can identify the nature of the discrepancy. For more information on test results of a checkpoint, see Viewing Checkpoint Results.For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, you can check that the map zooms in correctly.You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins are loaded). Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.


Text/Text Area Checkpoint :

In the Text/Text Area Checkpoint Properties dialog box, you can specify the text to be checked as well as which text is displayed before and after the checked text. These configuration options are particularly helpful when the text string you want to check appears several times or when it could change in a predictable way during run sessions.
Note: In Windows-based environments, if there is more than one line of text selected, the Checkpoint Summary pane displays [complex value] instead of the selected text string. You can then click Configure to view and manipulate the actual selected text for the checkpoint.QuickTest automatically displays the Checked Text in red and the text before and after the Checked Text in blue. For text area checkpoints, only the text string captured from the defined area is displayed (Text Before and Text After are not displayed). To designate parts of the captured string as Checked Text and other parts as Text Before and Text After, click the Configure button. The Configure Text Selection dialog box opens

Checking XML :

XML (Extensible Markup Language) is a meta-markup language for text documents that is endorsed as a standard by the W3C. XML makes the complex data structures portable between different computer environments/operating systems and programming languages, facilitating the sharing of data.XML files contain text with simple tags that describe the data within an XML document. These tags describe the data content, but not the presentation of the data. Applications that display an XML document or file use either Cascading Style Sheets (CSS) or XSL Formatting Objects (XSL-FO) to present the data.You can verify the data content of XML files by inserting XML checkpoints. A few common uses of XML checkpoints are described below:An XML file can be a static data file that is accessed in order to retrieve commonly used data for which a quick response time is needed—for example, country names, zip codes, or area codes. Although this data can change over time, it is normally quite static. You can use an XML file checkpoint to validate that the data has not changed from one application release to another.An XML file can consist of elements with attributes and values (character data). There is a parent and child relationship between the elements, and elements can have attributes associated with them. If any part of this structure (including data) changes, your application’s ability to process the XML file may be affected. Using an XML checkpoint, you can check the content of an element to make sure that its tags, attributes, and values have not changed.XML files are often an intermediary that retrieves dynamically changing data from one system. The data is then accessed by another system using Document Type Definitions (DTD), enabling the accessing system to read and display the information in the file. You can use an XML checkpoint and parameterize the captured data values in order to check an XML document or file whose data changes in a predictable way.XML documents and files often need a well-defined structure in order to be portable across platforms and development systems. One way to accomplish this is by developing an XML schema, which describes the structure of the XML elements and data types. You can use schema validation to check that each item of content in an XML file adheres to the schema description of the element in which the content is to be placed.