Saturday, January 29, 2011

12 Tips for Writing an Effective Resume

1. Make sure to use the right keywords
Most companies (even smaller ones) are already using digital databases to search for candidates. This means that the HR department will run search queries based on specific keywords. Guess what, if your resume doesn’t have the keywords related to the job you are applying for, you will be out even before the game starts.

know more..

2. Use Design That Grabs Attention
Employers make snap judgments when glancing at your resume. If they see unrelated job titles or skills the likelihood is very high that they will make an immediate assumption that you are not qualified for the job you want. Adding to this problem is the fact that employers don't have the time to read through each of your job descriptions to determine if you have the skills they need. You Must Do That For Them! The design of your resume must highlight the most important information about your work experience, skills and education. At first glance this information forms the image that employers have of your skills and abilities.
know more..

3. Don't skip the small stuff.

Make sure your résumé includes your name, mailing address, phone numbers, and e-mail address -- all possible ways you can be contacted.

know more..

4. Edit and proofread carefully

The importance of painstakingly proofing your résumé for typos, misspellings, and grammatical errors cannot be stressed enough. Enlist several other pairs of eyes to go over it as well, preferably belonging to friends who are professional writers or editors. Having to review so many résumés can make many employers look for reasons to eliminate applicants; that first typo usually does the trick. Even small mistakes can lead a potential employer to believe that a candidate might not make a very careful or conscientious employee.

know more..

5. Be truthful and accurate

Make sure you have not included any misleading or false information on your résumé. Chances are your "inaccuracies" will eventually be discovered, and you'll lose all credibility with your prospective employer.

know more..

7. Emphasize achievements

Employers are less interested in titles and duties and more interested in previous accomplishments. The fact that you implemented cost-cutting measures that reduced your department's expenses by 15 percent is far more meaningful than simply stating you oversaw a budget. Quantify your achievements in terms of percentages, dollar amounts, or time frames to make your accomplishments more concrete.

know more..

8. Put education in the right place
If you are a recent graduate who does not yet have much work experience, make sure to put the emphasis on your education. In addition to listing the university you attended, include information on degrees earned, majors and minors, grade point average, date of program completion, and any scholarships or honors received. Once you've got several years of work experience under your belt, this education information can move to the end of the résumé.

know more..

9. Use bullet points
No employer will have the time (or patience) to read long paragraphs of text. Make sure, therefore, to use bullet points and short sentences to describe your experiences, educational background and professional objectives.

know more..

10. You don’t need to list all your work experiences
If you have job experiences that you are not proud of, or that are not relevant to the current opportunity, you should just omit them. Mentioning that you used to sell hamburgers when you were 17 is probably not going to help you land that executive position.

know more..

11. Sell Your Fish
Remember that you are trying to sell yourself. As long as you don’t go over the edge, all the marketing efforts that you can put in your resume (in its content, design, delivery method and so on) will give you an advantage over the other candidates.

know more..

12. Don’t include irrelevant information
Irrelevant information such as political affiliation, religion and sexual preference, Blood group, Height, Weight will not help you. In fact it might even hurt your chances of landing an interview. Just skip it.

know more..

Tuesday, January 18, 2011

QTP Interview Questions

Tell me briefly about QTP?
If you are going for a position related to QTP, you could expect this as the first question in the interview. The first step on the part of an interviewer is to make you comfortable with a basic question. 

know more..

Hence try to remember maximum portion from the following content that should be presented to the interviewer if situation arises.


QTP is a graphical interface record-playback automation tool. It is able to work with any web, Java or windows client application. QTP enables you to test standard web objects and ActiveX controls. In addition to these environments, QTP also enables you to test Java applets and applications and multimedia objects on Applications as well as standard Windows applications, Visual Basic applications and .NET framework applications...

QTP is Mercury Interactive Functional Testing Tool.
Mercury QTP 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 QTP’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.

QTP enables you to test standard Windows applications, Web objects, ActiveX controls, and Visual Basic applications. You can also acquire additional QTP 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).
What’s the basic concept of QTP?
QTP is based on two concepts like: a) Recording b) Playback
Which scripting language used by QTP?
QTP uses VB scripting.
How many types of recording facility are available in QTP?
QTP provides three types of recording methods like:
a) Context Recording (Normal)
b) Analog Recording
c) Low Level Recording
How many types of Parameters are available in QTP?
QTP provides three types of Parameters like:
a) Method Argument
b) Data Driven
c) Dynamic
What’s the testing process in QTP?
QTP testing process consist of seven steps like: 1) Preparing to recording
2) Recording
3) Enhancing your script
4) Debugging
5) Run
6) Analyze
7) Report Defects etc.
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 checkpoints to an image to check enable property in QTP?
1: If all images are like 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 object and click on add remove to add the available properties to that object. And if you take it as image than you need to check visible or invisible property, 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.


Important aspects that needs to be checked are:

a)
Find out form the Developer if he is showing different images for activating/deactivating i.e. grayed 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.

b)
If it is a button used to display with the headsup as an image you would 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 QTP window.
How to Run a Test using QTP?
Step-1: Start QTP and open your test.
If QTP is not already open, choose Start > Programs > QuickTest Professional > QuickTest Professional.
# If the Welcome window opens, click Open Existing.
# If QTP 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.

Step-2:
Confirm that all images are saved to the test results.
QTP 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.

Step-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 QTP 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 QTP 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 QTP. 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 load testing for web based Application?
1) Recording a scenario in QTP of web based application.
2) Make 100 copies of that scenario and run the test (scenario 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 scenario 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 suppress 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 behavior.
What's the role of Checkpoints in QTP?
A checkpoint verifies that expected information is displayed in your application while the test is running. Checkpoint is basically a point in the test, which validates for truthfulness of a specific thing in the AUT. There are different types of checkpoints depending on the type of data that needs to be tested in the AUT. It can be text, image/bitmap, attributes, XML etc....
What types of checkpoints are offered by QTP?
There are 10 types of checkpoints you can insert in QTP: 1) Standard Checkpoint checks the property value of an object in your application or Web page. The standard checkpoint checks a variety of objects such as buttons, radio buttons, combo boxes, lists, etc.

2)
Image Checkpoint checks the value of an image in your application or Web page. For example, you can check that a selected image’s source file is correct.

3)
Bitmap Checkpoint checks an area of your Web page or application as a bitmap.

4)
Table Checkpoint checks information within a table. For example, suppose your application or Web site contains a table listing all available flights from one place to another. You can add a table checkpoint to check that the time of the first flight in the table is correct.

5)
Text Checkpoint checks that a text string is displayed in the appropriate place in your application or on a Web page.

6)
Text Area Checkpoint checks that a text string is displayed within a defined area in a Windows application, according to specified criteria.

7)
Accessibility Checkpoint identifies areas of your Web site that may not conform to the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines.

8)
Page Checkpoint checks the characteristics of a Web page. For example, you can check how long a Web page takes to load or whether a Web page contains broken links.

9)
Database Checkpoint checks the contents of a database accessed by your application.

10)
XML Checkpoint checks the data content of XML documents in XML files or XML documents in Web pages and frames.
How to add a standard checkpoint in your test?
1) Start QTP 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 QTP 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.
How run time data (Parameterization) is handled in QTP?
You can 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?
By QTP’s Keyword Driven approach, the 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 QTP automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View.
How QTP recognizes Objects in AUT?
QTP stores the definitions for application objects in a file called the Object Repository.

As you record your test, QTP will add an entry for each item you interact with.


Each Object Repository entry will be identified by a logical name (determined automatically by QTP), and will contain a set of properties (type, name, etc) that uniquely identify each object. Each line in the QTP 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?
QTP has two types of object repositories for storing object information:
1)
Shared object repositories and
2)
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, QTP 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 modify values in an action object repository, your changes do not have any effect on other actions. Hence, if the same test object exists in more than one action and if 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 you do?
Adhoc testing is done. It covers the least basic functionality to verify that the system is working fine.
know more..
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 log will be created and can be viewed manually which cannot be restricted from getting created.
Explain the Test Fusion Report of QTP?
Once a tester has run a test, a TestFusion report displays all aspects of the test run.
know more..

This is a high-level results overview, an expandable Tree View of the test specifying the following:

Exactly where application failures occurred,
Test data used
Application screen shots for every step that highlight any discrepancies
Detailed explanations of each checkpoint pass and failure.
By combining TestFusion reports with QTP, you can share reports across an entire QA and development team.
QTP supports which environments?
QTP 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.
know more..

What are the elements of QTP Window?
Before beginning creation of the tests,, it is essential to familiarize with the main QTP window.

The QTP window contains the following key elements:

1)
Title bar: Displays the name of the currently open test.

2)
Menu bar: Displays menus of QTP commands.

3)
File toolbar: Contains buttons to assist you in managing your test.

4)
Testing toolbar: Contains buttons to assist you in the testing process.

5)
Debug toolbar: Contains buttons to assist you in debugging tests.

6)
Test pane: Contains the Keyword View and Expert View tabs.

7)
Active Screen: Provides a snapshot of your application as it appeared when you performed a certain step during the recording session.

8)
Data Table: Assists you in parameterizing your test.

9)
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 QTP for the first time.
You can display the Debug Viewer by choosing View < Debug Viewer.)

10)
Status bar: Displays the status of the QTP application.
know more..
How does QTP identifies the object in the application?
QTP identifies the object in the application by LogicalName and Class.
For example:
The Edit box is identified by Logical Name : PSOPTIONS_BSE_TIME20 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.
Briefly explain the utility of Table and Database Checkpoints?
By adding table checkpoints to your tests or components, you can check:
a)
That a specified value is displayed in a cell in a table on your application.
b)
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, QTP 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 QTP, 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
How do you check 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. QTP 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, QTP 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, QTP 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).


The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.
Briefly explain the utility of 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.

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.


QTP 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.

know more..
What are the Features & Benefits of QTP?
1) Key word driven testing

2)
Suitable for both client server and web based application

3)
VB script as the script language

4)
Better error-handling mechanism

5)
Excellent data driven testing features

6)
Operates stand-alone, or integrated into HP Business Process Testing and HP Quality Center.

It introduces next-generation zero-configuration Keyword Driven testing technology in QTP allowing for fast test creation, easier maintenance, and more powerful data-driving capability.

It identifies objects with Unique Smart Object Recognition, even if they change from build to build, enabling reliable unattended script execution.

It collapses test documentation and test creation to a single step with Auto-documentation technology.

It enables thorough validation of applications through a full complement of checkpoints.
know more..
How to handle the exceptions using recovery scenario manager in QTP?
You can instruct QTP to recover unexpected events or errors that occurred in your testing environment during test run. Recovery scenario manager provides a wizard that guides you through the defining recovery scenario.

Recovery scenario has three steps

1) Triggered Events
2) Recovery steps
3) Post Recovery Test-Run
What information does the columns in the Keyword View provide for each step?
As you recorded your test, QTP generated steps in the Keyword View representing each operation you performed in the Web browser.
know more..

The columns in the Keyword View show different information for each step, as follows:

1) Item:
Displays the item for the step (test object, utility object, function call, or statement) in a hierarchical icon-based tree.

2) Operation:
The operation to be performed on the item, for example, Click or Select.

3) Value:
The argument values for the selected operation, for example, the mouse button to use when clicking the image.

4) Assignment:
The assignment of a value to or from a variable so you can use the value later in the test.

5) Comment:
Any textual information you want to add regarding the step, for example, Return to page used in first step of the test.

6) Documentation:
Auto-documentation of what the step does, in an easy-to-understand sentence, for example, Click the "findFlights" image.
Why do we use Regular Expressions?
We create a text checkpoint for searching a specific text string. We can use regular expressions to increase the flexibility and adaptability of your tests. Regular expressions enable QTP to identify objects and text strings with varying values.
You can use regular expressions when defining the properties of an object, the methods of an argument, when parameterizing a step, and when creating checkpoints with varying values.
Explain QTP Testing process ?
The QTP testing process consists of 6 main phases:
1) Create your test plan:
Prior to automating there should be a detailed description of the test including the exact steps to follow, data to be input, and all items to be verified by the test. The verification information should include both data validations and existence or state verifications of objects in the application.

2) Recording a session on your application:
As you navigate through your application, QTP graphically displays each step you perform in the form of a collapsible icon-based test tree. A step is any user action that causes or makes a change in your site, such as clicking a link or image, or entering data in a form.

3) Enhancing your test:

Inserting checkpoints into your test lets you search for a specific value of a page, object or text string, which helps you identify whether or not your application is functioning correctly.
Checkpoints can be added to a test as you record it or after the fact via the Active Screen. It is much easier and faster to add the checkpoints during the recording process.

Broadening the scope of your test by replacing fixed values with parameters lets you check how your application performs the same operations with multiple sets of data.

Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.

4) Debugging your test:
If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.

5) Running your test on a new version of your application:
You run a test to check the behavior of your application. While running, QTP connects to your application and performs each step in your test.

6) Analyzing the test results:
You examine the test results to pinpoint defects in your application.

7) Reporting defects:
As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.
know more..
What is parameterizing of Tests?
When you test your application, you may want to check how it performs the same operations with multiple sets of data.

For example, you want to check how your application responds to ten separate sets of data. You could record ten separate tests, each with its own set of data.


Alternatively, you can create a parameterized test that runs ten times: each time the test runs, it uses a different set of data.
How to analyze the test results using QTP?
When QTP finishes running the test, the Test Results window opens. Initially, the Test Results window contains two panes for displaying the key elements of your test run. # The left pane displays the results tree, an icon-based view of the steps that were performed while the test was running. The results tree is organized according to the Web pages visited during the test run and can be expanded (+) to view each step. The steps performed during the test run are represented by icons in the tree. You can instruct QTP to run a test or action more than once using different sets of data in each run. Each test run is called iteration, and each iteration is numbered. (The test you ran had only one iteration.) # The right pane displays the test results details. The iteration summary table indicates which iterations passed and which failed. The status summary table indicates the number of checkpoints or reports that passed, failed, and raised warnings during the test. View the test results for a specific step. In the results tree, expand (+) Test Recording Summary > Recording Iteration 1 (Row 1) > Action1 Summary > your application > your test name.
know more..

Monday, January 17, 2011

Manual Testing Interview Question

What is the difference between QA and Testing?
QA stands for "Quality Assurance", and focuses on "Prevention" of defects in the product being developed. It is associated with the "Process" and activities related to the Process Improvement. Quality Assurance measures the quality of the processes employed to create a quality product. Whereas "Testing" refers to "Quality Control", and focuses on Detection of Defect and removal thereafter. Or Quality Control measures the quality of a product.
know more..

What is the difference between Software Testing & Debugging?
Testing is the process of locating or identifying the errors or bugs in a software system. Whereas Debugging is the process of Fixing the identified Bugs. It involves a process of analyzing and rectifying the syntax errors, logic errors and all other types of errors identified during the process of testing.
What is the difference between a Bug and a Defect?
"Bug" is a problem or an error in the software code, which is found in the application during Testing. Bug is responsible for failure of the application to comply with the desired specifications. Whereas "Defect" is problem reported by the customer during usage of the software application.
What is the difference between a Bug and an Enhancement?
"Bug" is a problem or an error in the software code, which is found in the application during Testing. Bug is responsible for failure of the application to comply with the desired specifications. Whereas "Enhancement" is the additional feature or functionality found and added to the application as desired by the end user / real word customer or tester during the testing process.
know more..
What is the difference between Requirements & Specifications?
"Requirements" are statements given by the customer as to what needs to be achieved by the software system. Later on these requirements are converted into specifications which are nothing but feasible or implementable requirements. Whereas "Specifications" are feasible requirements derived from various statements given by the customer. These are the starting point for the product development team.
What is the sequence of succession in STLC - Software Testing Life Cycle?
1) Test Planning
2)
Test Analysis
3)
Test Design
4)
Construction and verification
5)
Testing Cycles
6)
Final Testing and Implementation and Post Implementation.
What is the difference between Verification and Validation?
"Verification" involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications to confirm whether items, processes, services, or documents conform to specified requirements or not. This can be done with the help of checklists, issues lists, walkthroughs, and inspection meetings. The purpose of verification is to determine whether the products of a given phase of the software development cycle fulfill the requirements established during the previous phase or not. Whereas "Validation" is the determination of the correctness of the final program or software product produced from a development project with respect to the user needs and requirements. This involves actual testing of the product and takes place after verifications are completed. "Software Verification" raises the question, "Are we building the Product Right?"; that is, does the software conform to its specification. "Software Validation" raises the question, "Are we building the Right Product?"; that is, is the software doing what the user really requires.
What is the difference between a Test Plan and a Use Case?
"Test Plan" is a document describing an introduction to the client company, intended scope, overview of the application, test strategy, schedule of testing activities, roles and responsibilities, deliverables and milestones. It describes test items, features to be tested, testing tasks, details of the personnel performing each task and any risks requiring contingency planning. Whereas a "Use Case" describes the process as to how an end user uses a specific functionality in the application. It is a summary of user actions and system response to the user actions. It contains the flows like typical flow, alternate flow and exceptional flow. It also contains pre condition and post condition.
What is the difference between Bug Priority & Bug Severity?
"Bug Priority" is the need on how urgently bug is needed to be fixed. It describes the importance of the bug. Bug priority may change according to the schedule of testing. Whereas "Bug Severity" is the quantum of danger as to how badly the bug can harm the system. It describes as to how bad the bug is. Severity is a feature of constant nature associated with the bug.
What is difference between Waterfall Model and V Model?
"Waterfall Model" Is a sequential software development model (a process for the creation of software) in which development is seen as flowing steadily downwards (like a waterfall) through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance. To follow the waterfall model, we proceed from one phase to the next in a purely sequential manner. In traditional waterfall model, testing comes at the fag end of the development process. Whereas "V Model" or "Life Cycle Testing" involves carrying out verification of consistency, completeness and correctness of software at every stage of the development life cycle. It aims at catching the defects as early as possible and thus reduces the cost of fixing them. It involves continuously testing the system during all stages of the development process rather than just limiting testing to the last stage.
What are Baseline Documents?
Baseline documents are the documents, which have been approved by the customer and will not have any more changes. Baseline Documents cover all the details of the project and have undergone "walkthrough" process. Once a document is Base-lined it cannot be changed unless there is a change request duly approved by the customer. Service Level Agreement (SLA) & Business Requirement Documents (BRD) are the examples of Baseline Documents.
What is Defect Density?
"Defect Density" Is a software metric defined as: Total number of defects per LOC (lines of code). Alternatively It can be: Total number of defects per Size of the Project. Here the measure of "Size of the Project" can be number of Function Points, Number of Feature Points, number of Use Cases or KLOC (Kilo Lines of Code) etc
What is Negative Testing?
"Negative Testing" involves testing the application for failure like conditions. It involves testing the tool with improper inputs. For example entering the special characters in place of a phone number.
What is Incremental Integration Testing?
"Incremental Integration Testing" Involves continuous testing of an application while new functionality is simultaneously added. It requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed. This testing is done either by programmers or by testers.
What is the difference between Unit Testing, Component Testing and Integration Testing?
"Unit Testing" involves testing of individual programs, modules, or components to demonstrate that the program executes as per the specification and it validates the design and technical quality of the application. In Unit Testing, the Called Components (or Communicating Components) are replaced with Stubs, Simulators, or Trusted Components. Testing Stubs or Drivers are used to simulate the behavior of interfacing modules. "Component Testing" is like "Unit Testing" with the difference that all Stubs and Simulators are replaced with the real objects. Here a Unit is a component, and integration of one or more such components is also a Component. Whereas "Integration Testing" is the test process which begins after two or more programs components have been successfully unit tested. It is conducted by the development team to validate the interaction or communication/flow of information between the individual components that will be integrated. 

HR Interview Questions

Can you please tell me about yourself?
The most often asked question in interviews. Although this question is quite broad, keep your answer focused and relevant to the job you're applying for.

You need to have a short statement prepared in your mind. Be careful that it does not sound rehearsed. Limit it to work-related items unless asked otherwise. Mention the top three or four aspects of your experience, skills, interests, and personality that make you a qualified candidate for the job.


Talk about things you have done and jobs you have held that relate to the position you are interviewing for. Start with the item farthest back and work up to the present.
What are your long- and short-term career goals?
The interviewer is trying to get a feel for why you want this job and how long you’re going to stick with it. The ideal answer will assure the employer that you’re worth his investment - that is, training you, introducing you to clients, entrusting you with responsibility. Your answer should assure him that you’d be around for awhile - and maybe even a long time.
Do you consider this a lateral or vertical career move?
This question is designed to find out how challenged you’ll be on the job -be careful, it’s a double-edged sword. If you aren’t challenged, you’ll get bored and move on. If you’re too challenged, you might not make it past the first week. Try to come in somewhere in the middle - maybe say something to the effect of, "It’s a comfortable stretch." Another tip: Your answer will also give the employer a sense of whether you’re hoping for a just a little or a big increase in salary.
Why do you want to leave your current position?
The interviewer is concerned about any problems that might pop up on your next job - especially since that might be with him. Be sure to use good judgment here. Don’t bad-mouth your current boss and don’t bring up anything negative. A safe approach is to say something like: "It’s time to move on in my career" or "I'm looking for a greater challenge."
Why did you leave your last job?
The interviewer wants to know if there are any underlying problems like: lack of commitment, difficult personality, poor performance, or anything that might lead to termination. Employers don’t want to take on someone who has a record of walking out on jobs or getting fired. Stay positive regardless of the circumstances. Never refer to a major problem with management and never speak ill of supervisors, co-workers or the organization. If you do, you will be the one looking bad. Keep smiling and talk about leaving for a positive reason such as an opportunity, a chance to do something special or other forward-looking reasons. No matter why you left your last job, couch your response in positive terms, without lying.
Please explain why you have a gap in your employment history?
The employer is looking for any problems in your personal life that might become his headache if he hires you. Explain your gaps honestly, leaning on activities that support your job objective, if that’s possible. If you don’t have anything to say that’s relevant, then talk about activities that show your strength of character and helped you know what you really want to do next: the job you're interviewing for.
What experience do you have in this field?
Speak about specifics that relate to the position you are applying for. If you do not have specific experience, get as close as you can.
Do you consider yourself successful?
You should always answer yes and briefly explain why. A good explanation is that you have set goals, and you have met some and are on track to achieve the others.
What do co-workers say about you?
Be prepared with a quote or two from co-workers. Either a specific statement or a paraphrase will work. Jill Clark, a co-worker at Smith Company, always said I was the hardest workers she had ever known. It is as powerful as Jill having said it at the interview herself.
What do you know about this organization?
This question is one reason to do some research on the organization before the interview. Find out where they have been and where they are going. What are the current issues and who are the major players?
Do you know anyone who works for us?
Be aware of the policy on relatives working for the organization. This can affect your answer even though they asked about friends not relatives. Be careful to mention a friend only if they are well thought of.
What kind of salary do you need?
A loaded question. A nasty little game that you will probably lose if you answer first. So, do not answer it. Instead, say something like, That's a tough question. Can you tell me the range for this position? In most cases, the interviewer, taken off guard, will tell you. If not, say that it can depend on the details of the job. Then give a wide range.
Are you a team player?
You are, of course, a team player. Be sure to have examples ready. Specifics that show you often perform for the good of the team rather than for yourself are good evidence of your team attitude. Do not brag, just say it in a matter-of-fact tone. This is a key point.
How long would you expect to work for us if hired?
What college experience are you especially proud of?
If you haven't been in the workforce long, this question is your opportunity to give balance to the fact that you don't have much paid experience. Spotlight your academic and extracurricular achievements, especially the ones that are relevant to your job objective.
Have you ever been asked to leave a position?
If you have not, say no. If you have, be honest, brief and avoid saying negative things about the people or organization involved.
Explain how you would be an asset to this organization
You should be anxious for this question. It gives you a chance to highlight your best points as they relate to the position being discussed. Give a little advance thought to this relationship.
Why should we hire you?
Point out how your assets meet what the organization needs. Do not mention any other
Tell me about a suggestion you have made
Have a good one ready. Be sure and use a suggestion that was accepted and was then considered successful. One related to the type of work applied for is a real plus.
What irritates you about co-workers?
This is a trap question. Think real hard but fail to come up with anything that irritates you. A short statement that you seem to get along with folks is great.
What strengths would you bring to this job that other candidates might not?
The employer’s giving you the floor to sell yourself for the job. Prepare well for this answer and deliver it with confidence. There are many good answers to this question, just stay positive. A few good examples: Your ability to prioritize, Your problem-solving skills, Your ability to work under pressure, Your ability to focus on projects, Your professional expertise, Your leadership skills, Your positive attitude. Make your presentation using brief achievement stories whenever possible.
How do you introduce a new software QA process?
It depends on the size of the organization and the risks involved. For large organizations with high-risk projects, a serious management buy-in is required and a formalized QA process is necessary. For medium size organizations with lower risk projects, management and organizational buy-in and a slower, step-by-step process is required. Generally speaking, QA processes should be balanced with productivity, in order to keep any bureaucracy from getting out of hand. For smaller groups or projects, an ad-hoc process is more appropriate. A lot depends on team leads and managers, feedback to developers and good communication is essential among customers, managers, developers, test engineers and testers. Regardless the size of the company, the greatest value for effort is in managing requirement processes, where the goal is requirements that are clear, complete and testable.
What are the common problems coming across Software Development Process?
Common problems in software development process are: 1) Poor Projection of Requirements - Generally the users are not very clear in regards to their exact needs. Most of the specifications given to Software Development Outsourcing vendors are rough and very sketchy. Problems arise if the requirements are unclear, incomplete, too general, and not testable etc. 2) Miscommunication - Becomes the main cause of problem when the developers remain ignorant of the exact needs or expectations of the customer. 3) Unrealistic Schedules - Cause problems if too much work is crammed in too little time. 4) Inadequate Testing - Problems arise when the application has not been adequately tested before giving it to the customer & the customer complains after using it or when there is a systems crash.


know more..