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……

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.

Basics of QTP

What’s the basic concept of QTP?
QTP is based on two concept-* Recording* Playback

Which scripting language used by QTP?
QTP using VB scripting.

How many types of recording facility are available in QTP? QTP provides three types of recording methods-* Context Recording (Normal)* Analog Recording* Low Level Recording

How many types of Parameters are available in QTP?
QTP provides three types of Parameter-* Method Argument* Data Driven* Dynamic

What’s the QTP testing process?
QTP testing process consist of seven steps-* Preparing to recoding* Recording* Enhancing your script* Debugging* Run* Analyze* Report Defects (more…)

How to Start recording using QTP?
Choose Test > Record or click the Record button.When the Record and Run Settings dialog box opens to do this;1. In the Web tab, select Open the following browser when a record or run session begins.2. In the Windows Applications tab, confirm that Record and run on these applications (opened on session start) is selected, and that there are no applications listed.

How to insert a check point to a image to check enable property in QTP?

• As you are saying that the all images are as push button than you can check the property enabled or disabled. If you are not able to find that property than go to object repository for that objecct and click on add remove to add the available properties to that object. Let me know if that works. And if you take it as image than you need to check visible or invisible property tht also might help you are there are no enable or disable properties for the image object.
• The Image Checkpoint does not have any property to verify the enable/disable property.One thing you need to check is:* Find out form the Developer if he is showing different images for activating/deactiving i.e greyed out image. That is the only way a developer can show deactivate/activate if he is using an “image”. Else he might be using a button having a headsup with an image.* If it is a button used to display with the headsup as an image you woudl need to use the object Properties as a checkpoint.
  

How to Save your test using QTP?
Select File > Save or click the Save button. The Save dialog box opens to the Tests folder.Create a folder which you want to save to, select it, and click Open.Type your test name in the File name field.Confirm that Save Active Screen files is selected.Click Save. Your test name is displayed in the title bar of the main QuickTest window.

How to Run a Test using QTP?
1 Start QuickTest and open your test.
If QuickTest is not already open, choose Start > Programs > QuickTest Professional > QuickTest Professional..
If the Welcome window opens, click Open Existing.
If QuickTest opens without displaying the Welcome window, choose File > Open
or
click the Open button. In the Open Test dialog box, locate and select your test, then click Open.
2 Confirm that all images are saved to the test results.QuickTest allows you to determine when to save images to the test results. Choose Tools > Options and select the Run tab. In the Save step screen capture to test results option, select Always.
Click OK to close the Options dialog box.
3 Start running your test.
Click Run or choose Test > Run. The Run dialog box opens.Select New run results folder. Accept the default results folder name.Click OK to close the Run dialog box.

How to open a new test using QTP?
1. If QuickTest is not currently open, choose Start > Programs > QuickTest Professional > QuickTest Professional. If the Welcome window opens, click Blank Test. Otherwise, choose File > New, or click the New button. A blank test opens.
2. . If QuickTest is already open, check which add-ins are loaded by selecting Help > About QuickTest Professional. If the Web Add-in is not loaded, you must exit and restart QuickTest. When the Add-in Manager opens, select the Web Add-in, and clear all other add-ins. Choose File > New, or click the New button. A blank test opens.

How to do Laod testing for web based Application?
1. Recording a scenerio in QTP of my web based application.2. Make 100 copies of that scenerio and run the test (scenerio run for 100 times)3. In that case, do the load of application on server.4. The basic logic of running the copy 100 times is to create same scenerio as if 100 users were working.

What is the extension of script and object repository files?
Object Repository : .tsr , Script : .mts, Excel : Default.xls

How to supress warnings from the “Test results page”?
From the Test results Viewer “Tools > Filters > Warnings”…must be “Unchecked”.

When we try to use test run option “Run from Step”, the browser is not launching automatically why?
This is default behaviour.

How Does Run time data (Parameterization) is handled in QTP?
You can then enter test data into the Data Table, an integrated spreadsheet with the full functionality of Excel, to manipulate data sets and create multiple test iterations, without programming, to expand test case coverage. Data can be typed in or imported from databases, spreadsheets, or text files.

What is keyword view and Expert view in QTP?
Quick Test’s Keyword Driven approach, test automation experts have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View. Advanced testers can view and edit their tests in the Expert View, which reveals the underlying industry-standard VBScript that QuickTest Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View.

How QTP recognizes Objects in AUT?

QuickTest stores the definitions for application objects in a file called the Object Repository. As you record your test, QuickTest will add an entry for each item you interact with. Each Object Repository entry will be identified by a logical name (determined automatically by QuickTest), and will contain a set of properties (type, name, etc) that uniquely identify each object. Each line in the QuickTest script will contain a reference to the object that you interacted with, a call to the appropriate method (set, click, check) and any parameters for that method (such as the value for a call to the set method). The references to objects in the script will all be identified by the logical name, rather than any physical, descriptive properties.

What are the types of Object Repositories in QTP?
QuickTest has two types of object repositories for storing object information: shared object repositories and action object repositories. You can choose which type of object repository you want to use as the default type for new tests, and you can change the default as necessary for each new test. The object repository per-action mode is the default setting. In this mode, QuickTest automatically creates an object repository file for each action in your test so that you can create and run tests without creating, choosing, or modifying object repository files. However, if you do modify values in an action object repository, your changes do not have any effect on other actions. Therefore, if the same test object exists in more than one action and you modify an object’s property values in one action, you may need to make the same change in every action (and any test) containing the object. If I give some thousand tests to execute in 2 days what do u do? Adhoc testing is done. It covers the least basic functionalities to verify that the system is working fine.

How to “Turn Off” QTP results after running a Script?
Goto “Tools > Options > Run Tab” and Deselect “View results when run session ends”. But this suppresses only the result window, but a og will be created and can viewed manually which cannot be restricted from getting created.

Explain about the Test Fusion Report of QTP?
Once a tester has run a test, a TestFusion report displays all aspects of the test run: a high-level results overview, an expandable Tree View of the test specifying exactly where application failures occurred, the test data used, application screen shots for every step that highlight any discrepancies, and detailed explanations of each checkpoint pass and failure. By combining TestFusion reports with QuickTest Professional, you can share reports across an entire QA and development team.

To which environments does QTP supports ?
QuickTest Professional supports functional testing of all enterprise environments, including Windows, Web, ..NET, Java/J2EE, SAP, Siebel, Oracle, PeopleSoft, Visual Basic, ActiveX, mainframe terminal emulators, and Web services.

What’s QuickTest Window?
Before you begin creating tests, you should familiarize yourself with the main QuickTest window.The QuickTest window contains the following key elements:

• Title bar—Displays the name of the currently open test.
• Menu bar—Displays menus of QuickTest commands.
• File toolbar—Contains buttons to assist you in managing your test.
• Testing toolbar—Contains buttons to assist you in the testing process.
• Debug toolbar—Contains buttons to assist you in debugging tests.
• Test pane—Contains the Keyword View and Expert View tabs.
• Active Screen—Provides a snapshot of your application as it appeared when you performed a certain step during the recording session.
• Data Table—Assists you to parameterize your test.
• Debug Viewer pane—Assists you in debugging your test. The Debug Viewer pane contains the Watch Expressions, Variables, and Command tabs. (The Debug Viewer pane is not displayed when you open QuickTest for the first time. You can display the Debug Viewer by choosing View <>
• Status bar—Displays the status of the QuickTest application.

How does QTP identifies the object in the application?QTP identifies the object in the application by Logical Name and Class.
For example :The Edit box is identified by

Logical Name : txtSearch

Class: WebEdit

If an application name is changes frequently i.e while recording it has name “Window1” and then while running its “Windows2” in this case how does QTP handles?
QTP handles those situations using “Regular Expressions".

What is QTP?

QTP is Mercury Interactive Functional Testing Tool. QTP stands for Quality Test Professional. Mercury QuickTest Professional: provides the industry’s best solution for functional test and regression test automation – addressing every major software application and environment. This next-generation automated testing solution deploys the concept of Keyword-driven testing to radically simplify test creation and maintenance.

Unique to QuickTest Professional’s Keyword-driven approach, test automation experts have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View.

QuickTest is a graphical interface record-playback automation tool. It is able to work with any web, java or windows client application. Quick Test enables you to test standard web objects and ActiveX controls. In addition to these environments, QuickTest Professional also enables you to test Java applets and applications and multimedia objects on Applications as well as standard Windows applications, Visual Basic 6 applications and .NET framework application.
You can also acquire additional Quick Test add-ins for a number of special environments (such as Java, Oracle, SAP Solutions, .NET Windows and Web Forms, Siebel, PeopleSoft, Web services, and terminal emulator applications).

Effort Estimation

Estimates is considered to be difficult/challenging as most of the time estimate is requested so early in the project you might not even know how much information to provide a close to accurate estimate. In-order to provide a decent estimate below mentioned information is considered.

Factors for Estimation

Market opportunity

• Who the competition is?
• What is the opportunity now and in the future?

Contractual terms

• Are there penalty clauses?
• Is it phase wise delivery?
• Volatility of requirements
• How standard is the requirement?
• What could be the change in requirements over time?

Past Experience

• Have we had a better or bitter experience?
• Have we delivered something similar in the past?

Skill Set

• Talent pool of engineers and the expectations of the project
• In house training capability
• Ability to learn quickly
• Ability to ramp up
• Can we ramp up our team in case we win the project?
• Option and flexibility to outsource?

Technology

• Complexity
• Environment –Onsite/Offsite
• Virtual Testing

Estimation Models

What is it?

• Estimation model is the combination of the technique and the factors
• A predefined framework or template
• Adaptable with modifications

Build or use Models?

• Using existing models is a safe bet
• Derive and build your own models

Principle of Estimation for testing projects shall be:

• Based on
• Software requirements
• Previous projects
• Metrics
• Estimation shall
• Never forget the past
• Be recorded
• Be supported by tools
• Be always verified
• Consider automation needs
• Consider people skills
• Other Inputs to consider
• # of test cases/scenarios,
• # test cases per scenario,
• # of builds (for regression)

We also have an old thumb rule for estimation i.e. to complete testing we will take about 30% of Development time. This will not hold good all the time as some time coding for some functionality can be done much faster than the time it takes for testing the functionality.

If at al possible, keep a history of your estimates versus actual. Time and experience are some of the best educators. If you keep track you can gain some useful history.

Software Testing Methods

Software Testing Methods can be broadly classified as Black Box Testing, White Box Testing & Gray Box Testing.

Black Box Testing: In this type of testing , the tester views the program as a black - box, tester doesn't see the code of the program: Equivalence partitioning, Boundary - value analysis, Error guessing are the few which user will consider when testing.

White Box Testing: In this type of testing , the tester examine the internal structure of the program: Statement coverage, Decision coverage, condition coverage, Decision/Condition coverage, Multiple - condition coverage. This to do more with code verification. Usually the development team does this type of testing as many a times QA will not get accessto the code written by the developer.

Gray Box Testing: In this type of testing Black box testing can be combined with knowledge of database validation, such as SQL for database query and adding/loading data sets to confirm functions, as well as query the database to confirm expected result.

Software Testing Documents

Test Plan: The purpose of Test Plan document is to describe the overall test approach for the . The test approach will consist of the scope of the testing that is required for this Project, the activities that need to be completed, the resources required (people, software, hardware), test methodology, general release criteria, and any risks or dependencies for this project.
It should be noted, that test planning is an essential step in the overall software development framework. It sets expectations for the amount of testing (functional, system, and performance) that should occur for a project.

Test Effort Estimation: This document will give the details on how much time will be required for completion of the given Project / Module based on the priority of testcase (Low, Medium, High or Complex). For doing any effort estimation following few things are considered: Requirement Analysis, Testcase Design, Review, Automation/Performance Test, Manual Test Execution, Trainings if any & Project Management/Configuration Management.

Test Strategy: The purpose of a test strategy is to clarify the major tasks and challenges of the test project. Test strategy will consist of the following:
- Understand the decision algorithm and generate a parallel decision analyzer using Perl or Excel that will function as a reference oracle for high volume testing of the app.
- Create a means to generate and apply large numbers of decision scenarios to the product. This will be done either through the use of a GUI test automation system, if practical, or through a special test facility built into the product (if development is able to provide that), or through the direct generation of Decide Right scenario files that would be loaded into the product during test.
- Review the documentation, and the design of the user interface and functionality for its sensitivity to user error that could result in a reasonable misunderstanding of decision parameters, analysis, or suggestions.
- Test with decision scenarios that are near the limit of complexity allowed by the product. (We will investigate creating these scenarios automatically.)
- Compare complex scenarios (Automatically, if practical). - Test the product for the risk of silent failures or corruptions in the decision analysis.
- Using requirements documentation, user documentation, or by exploring the product, we will create an outline of product elements and use that to guide user-level capability and reliability testing of the product.

The principal issues in executing the test strategy are as follows:
- The difficulty of understanding and simulating the decision algorithm.
- The risk of coincidental failure of both the simulation and the product.
- The difficulty of automating decision tests.

Test Case: This document will contain the steps to be followed to achieve its objective. In a testcase document we will give the testcase Name, the steps to be followed, Test data, Expected and Actual results, Pass/Fail and remarks. We also specify the testcase version number and the author.

Software Testing

Software testing is any activity aimed at evaluating an attribute or capability of a program or system and determining that it meets its required results. Although crucial to software quality and widely deployed by programmers and testers, software testing still remains an art, due to limited understanding of the principles of software. The difficulty in software testing stems from the complexity of software: we can not completely test a program with moderate complexity. Testing is more than just debugging. The purpose of testing can be quality assurance, verification and validation, or reliability estimation. Testing can be used as a generic metric as well. Correctness testing and reliability testing are two major areas of testing. Software testing is a trade-off between budget, time and quality.