Sunteți pe pagina 1din 28

1. Software Testing is more Oriented to Detecting the defects or often equated to finding bugs.

Testing is a process of executing a software system to determine whether it matches its


specification and executes in its intended environment under controlled conditiions. The
controlled conditions should include both normal and abnormal conditions. Testing should
intentionally attempt to make things go wrong to determine if things happen when they
shouldn't or things don't happen when they should.  
2. SQA: - Software QA involves the entire software development PROCESS - monitoring and
improving the process, making sure that any agreed-upon standards and procedures are
followed, and ensuring that problems are found and dealt with. It is oriented to 'prevention'.
3.   Stop Testing: - Testing is potentially endless. We can not test till all the defects are unearthed
and removed -- it is simply impossible. At some point, we have to stop testing and ship the
software. The question is when.   Realistically, testing is a trade-off between budget, time and
quality. It is driven by profit models. The pessimistic, and unfortunately most often used
approach is to stop testing whenever some, or any of the allocated resources -- time, budget, or
test cases -- are exhausted. The optimistic stopping rule is to stop testing when either reliability
meets the requirement, or the benefit from continuing testing cannot justify the testing cost.
[Yang95] This will usually require the use of reliability models to evaluate and predict reliability
of the software under test. Each evaluation requires repeated running of the following cycle:
failure data gathering -- modeling -- prediction. This method does not fit well for ultra-
dependable systems, however, because the real field failure data will take too long to
accumulate.  
4. For Verification & Validation (V&V) Just as topic Verification and Validation indicated, another
important purpose of testing is verification and validation (V&V). Testing can serve as metrics. It
is heavily used as a tool in the V&V process. Testers can make claims based on interpretations of
the testing results, which either the product works under certain situations, or it does not work.
We can also compare the quality among different products under the same specification, based
on results from the same test.  
5. 2. What is the purpose of software testing? The purpose of software testing is a. To
demonstrate that the product performs each function intended; b. To demonstrate that the
internal operation of the product performs according to specification and all internal
components have been adequately exercised; c. To increase our confidence in the proper
functioning of the software. d. To show the product is free from defect. e. All of the above.   3.
6. Types of Levels: - COMPATIBILITY TESTING. Testing to ensure compatibility of an application or
Web site with different browsers, OSs, and hardware platforms. Compatibility testing can be
performed manually or can be driven by an automated functional or regression test suite.  
7. CONFORMANCE TESTING. Verifying implementation conformance to industry standards.
Producing tests for the behavior of an implementation to be sure it provides the portability,
interoperability, and/or compatibility a standard defines.  
8. FUNCTIONAL TESTING. Validating an application or Web site conforms to its specifications and
correctly performs all its required functions. This entails a series of tests which perform a
feature by feature validation of behavior, using a wide range of normal and erroneous input
data. This can involve testing of the product's user interface, APIs, database management,
security, installation, networking, etcF testing can be performed on an automated or manual
basis using black box or white box methodologies.
9.   LOAD TESTING. Load testing is a generic term covering Performance Testing and Stress Testing.
10. PERFORMANCE TESTING. Performance testing can be applied to understand your application or
WWW site's scalability, or to benchmark the performance in an environment of third party
products such as servers and middleware for potential purchase. This sort of testing is
particularly useful to identify performance bottlenecks in high use applications. Performance
testing generally involves an automated test suite as this allows easy simulation of a variety of
normal, peak, and exceptional load conditions.  
11. REGRESSION TESTING. Similar in scope to a functional test, a regression test allows a consistent,
repeatable validation of each new release of a product or Web site. Such testing ensures
reported product defects have been corrected for each new release and that no new quality
problems were introduced in the maintenance process. Though regression testing can be
performed manually an automated test suite is often used to reduce the time and resources
needed to perform the required testing.  
12. SMOKE TESTING. A quick-and-dirty test that the major functions of a piece of software work
without bothering with finer details. Originated in the hardware testing practice of turning on a
new piece of hardware for the first time and considering it a success if it does not catch on fire.  
13. STRESS TESTING. Testing conducted to evaluate a system or component at or beyond the limits
of its specified requirements to determine the load under which it fails and how. A graceful
degradation under load leading to non-catastrophic failure is the desired result. Often Stress
Testing is performed using the same process as Performance Testing but employing a very high
level of simulated load.  
14. UNIT TESTING. Functional and reliability testing in an Engineering environment. Producing tests
for the behavior of components of a product to ensure their correct behavior prior to system
integration.
15.   Black Box Testing Black box testing methods focus on the functional requirements of the
software. Tests sets are derived that fully exercise all functional requirements. This strategy
tends to be applied during the latter part of the lifecycle. Tests are designed to answer questions
such as:   1) How is functional validity tested? 2) What classes of input make good test cases? 3)
Is the system particularly sensitive to certain input values? 4) How are the boundaries of data
classes isolated? 5) What data rates or volumes can the system tolerate? 6) What effect will
specific combinations of data have on system operation?  
16. Equivalence Partitioning: - This method divides the input of a program into classes of data. Test
case design is based on defining an equivalent class for a particular input. An equivalence class
represents a set of valid and invalid input values. Guidelines for equivalence partitioning -   1) If
an input condition specifies a range, one valid and two invalid equivalence classes are defined.
2) If an input condition requires a specific value, one valid and two invalid equivalence classes
are defined. 3) If an input condition specifies a member of a set, one valid and one invalid
equivalence class are defined. 4) If an input condition is boolean, one valid and one invalid class
are defined.
17.   Boundary Value Analysis: - Boundary value analysis is complementary to equivalence
partitioning. Rather than selecting arbitrary input values to partition the equivalence class, the
test case designer chooses values at the extremes of the class. Furthermore, boundary value
analysis also encourages test case designers to look at output conditions and design test cases
for the extreme conditions in output. Guidelines for boundary value analysis -   1) If an input
condition specifies a range bounded by values a and b, test cases should be designed with values
a and b, and values just above and just below and b. 2) If an input condition specifies a number
of values, test cases should be developed that exercise the minimum and maximum numbers.
Values above and below the minimum and maximum are also tested. 3) Apply the above
guidelines to output conditions. For example, if the requirement specifies the production of an
table as output then you want to choose input conditions that produce the largest and smallest
possible table. 4) For internal data structures be certain to design test cases to exercise the data
structure at its boundary. For example, if the software includes the maintenance of a personnel
list, then you should ensure the software is tested with conditions where the list size is 0, 1 and
maximum (if constrained).  
18. Cause-Effect Graphs A weakness of the two methods is that do not consider potential
combinations of input/output conditions. Cause-effect graphs connect input classes (causes) to
output classes (effects) yielding a directed graph. Guidelines for cause-effect graphs -   1) Causes
and effects are listed for a modules and an identifier is assigned to each. 2) A cause-effect graph
is developed (special symbols are required). 3) The graph is converted to a decision table. 4)
Decision table rules are converted to test cases.   We can not test quality directly, but we can
test related factors to make quality visible. Quality has three sets of factors -- functionality,
engineering, and adaptability. These three sets of factors can be thought of as dimensions in the
software quality space. Each dimension may be broken down into its component factors and
considerations at successively lower levels of detail.
19.   Performance testing Not all software systems have specifications on performance explicitly.
But every system will have implicit performance requirements. The software should not take
infinite time or infinite resource to execute. "Performance bugs" sometimes are used to refer to
those design problems in software that cause the system performance to degrade.  
20. Reliability testing Software reliability refers to the probability of failure-free operation of a
system. It is related to many aspects of software, including the testing process. Directly
estimating software reliability by quantifying its related factors can be difficult. Testing is an
effective sampling method to measure software reliability. Guided by the operational profile,
software testing (usually black-box testing) can be used to obtain failure data, and an estimation
model can be further used to analyze the data to estimate the present reliability and predict
future reliability. Therefore, based on the estimation, the developers can decide whether to
release the software, and the users can decide whether to adopt and use the software. Risk of
using software can also be assessed based on reliability information. [Hamlet94] advocates that
the primary goal of testing should be to measure the dependability of tested software.  
21. Security testing Software quality, reliability and security are tightly coupled. Flaws in software
can be exploited by intruders to open security holes. With the development of the Internet,
software security problems are becoming even more severe. Many critical software applications
and services have integrated security measures against malicious attacks. The purpose of
security testing of these systems include identifying and removing software flaws that may
potentially lead to security violations, and validating the effectiveness of security measures.
Simulated security attacks can be performed to find vulnerabilities.   TESTING means "quality
control"        * QUALITY CONTROL measures the quality of a product        * QUALITY ASSURANCE
measures the quality of processes used to create a quality product. Beta testing is typically
conducted by end users of a software product who are not paid a salary for their efforts.  
22. Acceptance Testing Testing the system with the intent of confirming readiness of the product
and customer acceptance.  
23. Ad Hoc Testing Testing without a formal test plan or outside of a test plan. With some projects
this type of testing is carried out as an adjunct to formal testing. If carried out by a skilled tester,
it can often find problems that are not caught in regular testing. Sometimes, if testing occurs
very late in the development cycle, this will be the only kind of testing that can be performed.
Sometimes ad hoc testing is referred to as exploratory testing.  
24. Alpha Testing Testing after code is mostly complete or contains most of the functionality and
prior to users being involved. Sometimes a select group of users are involved. More often this
testing will be performed in-house or by an outside testing firm in close cooperation with the
software engineering department.  
25. Automated Testing Software testing that utilizes a variety of tools to automate the testing
process and when the importance of having a person manually testing is diminished. Automated
testing still requires a skilled quality assurance professional with knowledge of the automation
tool and the software being tested to set up the tests.  
26. Beta Testing Testing after the product is code complete. Betas are often widely distributed or
even distributed to the public at large in hopes that they will buy the final product when it is
released.  
27. Black Box Testing Testing software without any knowledge of the inner workings, structure or
language of the module being tested. Black box tests, as most other kinds of tests, must be
written from a definitive source document, such as a specification or requirements document..  
28. Compatibility Testing Testing used to determine whether other system software components
such as browsers, utilities, and competing software will conflict with the software being tested.  
C
29. onfiguration Testing Testing to determine how well the product works with a broad range of
hardware/peripheral equipment configurations as well as on different operating systems and
software.
30.   Functional Testing Testing two or more modules together with the intent of finding defects,
demonstrating that defects are not present, verifying that the module performs its intended
functions as stated in the specification and establishing confidence that a program does what it
is supposed to do.   I
31. ndependent Verification and Validation (IV&V) The process of exercising software with the
intent of ensuring that the software system meets its requirements and user expectations and
doesn't fail in an unacceptable manner. The individual or group doing this work is not part of the
group or organization that developed the software. A term often applied to government work or
where the government regulates the products, as in medical devices.  
32. Installation Testing Testing with the intent of determining if the product will install on a variety
of platforms and how easily it installs.  
33. Integration Testing Testing two or more modules or functions together with the intent of
finding interface defects between the modules or functions. Testing completed at as a part of
unit or functional testing, and sometimes, becomes its own standalone test phase. On a larger
level, integration testing can involve a putting together of groups of modules and functions with
the goal of completing and verifying that the system meets the system requirements. (see
system testing)  
34. Load Testing Testing with the intent of determining how well the product handles competition
for system resources. The competition may come in the form of network traffic, CPU utilization
or memory allocation.  
35. Performance Testing Testing with the intent of determining how quickly a product handles a
variety of events. Automated test tools geared specifically to test and fine-tune performance are
used most often for this type of testing.  
36. Pilot Testing Testing that involves the users just before actual release to ensure that users
become familiar with the release contents and ultimately accept it. Often is considered a Move-
to-Production activity for ERP releases or a beta test for commercial products. Typically involves
many users, is conducted over a short period of time and is tightly controlled. (see beta testing)  
37. Regression Testing Testing with the intent of determining if bug fixes have been successful and
have not created any new problems. Also, this type of testing is done to ensure that no
degradation of baseline functionality has occurred.  
38. Security Testing Testing of database and network software in order to keep company data and
resources secure from mistaken/accidental users, hackers, and other malevolent attackers.  
39. Software Testing The process of exercising software with the intent of ensuring that the
software system meets its requirements and user expectations and doesn't fail in an
unacceptable manner. The organization and management of individuals or groups doing this
work is not relevant. This term is often applied to commercial products such as internet
applications. (contrast with independent verification and validation)  
40. Stress Testing Testing with the intent of determining how well a product performs when a load
is placed on the system resources that nears and then exceeds capacity.
41.   System Integration Testing Testing a specific hardware/software installation. This is typically
performed on a COTS (commerical off the shelf) system or any other system comprised of
disparent parts where custom configurations and/or unique installations are the norm.
42.   White Box Testing Testing in which the software tester has knowledge of the inner workings,
structure and language of the software, or at least its purpose.  
43. Difference Between Verification & Validation: - - Verification is about answering the question
"Does the system function properly?" or "Have we built the system right?" - Validation is about
answering the question "Is the product what the customer wanted?" or "Have we built the right
system?"   This definition indicates that Validation could be the same thing as Acceptance Test
(or at least very similar).   I have often described Verification and Validation processes in the
same way, ie:   1. Plan the test (output Test Plan) 2. Specify the test (output Test Specification) 3.
Perform the test (output Test Log and/or Test Report
44.   Verification & Validation Verification typically involves reviews and meetings to evaluate
documents, plans, code, requirements, and specifications. This can be done with checklists,
issues lists, walkthroughs, and inspection meetings. Validation typically involves actual testing
and takes place after verifications are completed. The term 'IV & V' refers to Independent
Verification and Validation

45. COMMON INTERVIEW


Tell me about yourself.
The most often asked question in interviews. 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 instructed otherwise. 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.

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 tract to achieve the others.

Why did you leave your last job?


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.
  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.  
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?  
What have you done to improve your knowledge in the last year?
Try to include improvement activities that relate to the job. A wide variety of activities can be
mentioned as positive self-improvement. Have some good ones handy to mention.  
Are you applying for other jobs?
Be honest but do not spend a lot of time in this area. Keep the focus on this job and what you can
do for this organization. Anything else is a distraction.  
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 worker she
had ever known." It is as powerful as Jill having said it at the interview herself.  
Why do you want to work for this organization?
This may take some thought and certainly should be based on the research you have done on the
organization, Sincerity is extremely important here, and will easily be sensed. Relate it to your
long-term career goals.  
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
will 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?
Specifics here are not good. Something like this should work: "I'd like it to be a long time." Or
"As long as we both feel I'm doing a good job."  
Have you ever had to fire anyone? How did you feel about that?
This is serious. Do not make light of it or in any way seem like you like to fire people. At the
same time, you will do it when it is the right thing to do. When it comes to the organization
versus the individual who has created a harmful situation, you will protect the organization.
Remember firing is not the same as layoff or reduction in force.  
What is your philosophy towards work?
The interviewer is not looking for a long or flowery dissertation here. Do you have strong
feelings that the job gets done? Yes. That's the type of answer that works best here. Short and
positive, showing a benefit to the organization.
If you had enough money to retire right now, would you?
Answer yes if you would, But since you need to work, this is the type of work you prefer. Do not
say yes if you do not mean it.
  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 your?
Point out how your assets meet what the organization needs. Do not mention any other
candidates to make a comparison.   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
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 are your greatest weaknesses?
Assure the interviewer that you can think of nothing that would stand in the way of your
performing in this position with excellence. Then, quickly review you strongest qualifications.
Example: "Nobody's perfect, but based on what you've told me about this position, I believe I' d
make an outstanding match. I know that when I hire people, I look for two things most of all. Do
they have the qualifications to do the job well, and the motivation to do it well? Everything in
my background shows I have both the qualifications and a strong desire to achieve excellence in
whatever I take on. So I can say in all honesty that I see nothing that would cause you even a
small concern about my ability or my strong desire to perform this job with excellence."  
Alternate strategy (if you don't yet know enough about the position to talk about such a perfect
fit): Instead of confessing a weakness, describe what you like most and like least, making sure
that what you like most matches up with the most important qualification for success in the
position, and what you like least is not essential.   Example: Let's say you're applying for a
teaching position. "If given a choice, I like to spend as much time as possible in front of my
prospects selling, as opposed to shuffling paperwork back at the office. Of course, I long ago
learned the importance of filing paperwork properly, and I do it conscientiously. But what I
really love to do is sell (if your interviewer were a sales manager, this should be music to his
ears.)  
What is your greatest strength?
Numerous answers are good, just stay positive. A few good examples: your ability to prioritize.
You know that your key strategy is to first uncover your interviewer's greatest wants and needs
before you answer questions.

Prior to any interview, you should have a list mentally prepared of your greatest strengths. You
should also have, a specific example or two, which illustrates each strength, an example chosen
from your most recent and most impressive achievements.

As a general guideline, the 10 most desirable traits that all employers love to see in their
employees are:
· 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. · Tell
me about your dream job. · Definiteness of purpose...clear goals. · Enthusiasm...high level of
motivation. · Likeability...positive attitude...sense of humor.   Stay away from a specific job. You
cannot win. If you say the job you are contending for is it, you strain credibility. If you say
another job is it, you plant the suspicion that you will be dissatisfied with this position if hired.
The best bet is to stay generic and say something like: "A job where I love the work, like the
people, can contribute, and can't wait to get to work."  
Why do you think you would do well at this job?
Give several reasons and include skills, experience, and interest.
  What are you looking for in a job?
Stay away from a specific job. You cannot win. If you say the job you are contending for is it,
you strain credibility. If you say another job is it, you plant the suspicion that you will be
dissatisfied with this position if hired. The best bet is to stay generic and say something like: "A
job where I love the work, like the people, can contribute, and can't wait to get to work."  
What kind of person would you refuse to work with?
Do not be trivial, It would take disloyalty to the organization, violence or lawbreaking to get you
to object. Minor objections will label you as a whiner.  
What is more important to you: the money or the work?
Money is always important, but the work is the most important. There is not better answer.  
What would your previous supervisor say your strongest point is?
· Loyalty
· Energy
· Positive attitude
· Leadership
· Team Player
· Expertise
· Initiative
· Patience
· Hard Work
· Creativity
· Problem solver
· Tell me about a problem you had with a supervisor.
Biggest trap of all. This is a test to see if you will speak ill of your boss. If you fall for it and tell
about a problem with a former boss, you may well blow the interview right there. Stay positive
and develop a poor memory about any trouble with a superior.
  What has disappointed you about a job?
Don't get trivial or negative. Safe areas are few but can include.
 Not enough of a challenge.
 You were laid off in a reduction.
 Company did not win a contract, which would have given you more responsibility.
  Tell me about your ability to work under pressure.
You may say that you thrive under certain types of pressure. Give an example that relates to the
type of position applied for.
  Do your skills match this job or another job more closely?
Probably this one. Do not give fuel to the suspicion that you may want another job more than
this one.
  What motivates you to do your best on the job?
This is a personal trait that only you can say, but good examples are:
 Challenge
 Achievement

1.  Recognition

2.   How would you know you were successful on this job?

3. Several ways are good measures: Ø You Set high standards for yourself and meet
them. Ø Your outcomes are a success. Ø Your boss tells you that you are successful.
4.   Would you be willing to relocate if required?

5. You should be clear on this with your family prior to the interview if you think
there is a chance it may come up. Do not say yes just to get the job if the real answer is
no. This can create a lot of problems later on in your career. Be honest at this point and
save yourself future grief.

6.   Describe your management style. Try to avoid labels. Some of the more
common labels, like "progressive", "Salesman" or "Consensus", can have several
meanings or descriptions depending on which management expert you listen to. The
"situational" style is safe, because it says you will manage according to the situation,
instead of "one size fits all."  

7. Do you have any blind spots? Trick question, if you know about blind spots,
they are no longer blind spots. Do not reveal any personal areas of concern here. Let them
do their own discovery on your bad points. Do not hand it to them.  

8. How do you propose to compensate for your lack of experience? First, if you
have experience that the interviewer does not know about, bring that up. Then, point out
(if true) that you are a hard working quick learner.

9.   What qualities do you look for in a boss? Be generic and positive, safe
qualities are knowledgeable, a sense of humor, fair, loyal to subordinates, and holder of
high standards. All bosses think they have these traits.  

10. Describe a bad decision you made. The major pitfall that interviewee's often
exhibit with this question is that they make the "bad decision" something they did when
they were ten years old. The idea here is not to avoid the question. Pick something from
the relevant past. We all make mistakes and a hallmark of honesty is admitting that and a
hallmark of self-awareness is being able to recognize when we made those mistakes.
Do not put your mistake so far back in the past that you are obviously picking something
that is "harmless" but if you feel the need to do this, you might say something like, "Well,
I have more current answers but I have one from my past that really stuck with me." If
you go that route, then explain why that decision "stuck with you" and, more importantly,
how it is has guided your actions in other areas so as to not make that kind of bad
decision again. The real point here, for the candidate, is to turn this into a "lesson
learned" answer. State your bad decision, make it clear why you perceive this was a bad
decision, and then talk about what you learned from that.  
11. Describe your work ethic. Emphasize benefits to the organization. Things like,
"determination to get the job done" and "work hard but enjoy your work" are good.  

12. Do you have any questions for me? Always have some questions prepared.
Questions involving areas where you will be an asset to the organization are good. "How
soon will I be able to be productive?" and "What type of projects will I be able to assist
on?" are examples.

13. Can u explain the structure of bug life cycle?


14. Can you explain V model in manual testing?
15. Can you explain me the levels in V model manual?
16. Can you explain water fall model in manual testing?
17. Difference between bug,error,and defect?
18. Explain about MicroSoft Six Rules Standardfor User Interface testing?
19. Explain about use case document ?
20. Explain me the phases of STLC and explain each one briefly?
21. Give exact and appropriate definition of testing.
22. How many modes of recording are there ?
23. How to add objects to the Object Rpository?
24. How to arrive Testcase? and how to write Testcase in Email id? when we go for
winrunner and why we go for
25. How to carry out manual testing for a background process which does't have any user
interface ?
26. How to do regression testing, and can give one or two examples on that in the same
application?
27. How to test the Microsoft Word 2003. What all the major areas to be tested, please
explain.
28. How to write a testcase and bugreport?plz expln with an example.
29. How will you review the test case and how many types are there ?
30. Share a particular project where you have been able to learn enough skills to help with
testing? (more for the
31. The role of both QA & QC?
32. What are GET TO , SETTO,and GET RO properties in QTP.
33. What are the difference between per text mode and shared mode in qtp ?
34. What are the objectives of Lowlevel recording? What is Elapsed Time? When we use
Update mode? Is Quick Test
35. What are the objectives of Utility objects?
36. What are the objectives of debugging?
37. What are the processes followed in your company for automation?
38. What do you mean by Pilot Testing?
39. What is AUT?
40. What is BUG Life cycle?
41. What is Black Box Testing?
42. What is FSO can you explain?
43. What is Review?
44. What is SRS and BRS document?Can you explain them briefly.
45. What is SRS and BRS in manual testing.
46. What is STLC how many phases are there can you explain them .
47. What is Sanity Test,Adhoc Testing & Smoke Testing? When will use the Above Tests?
48. What is V model can u explain ?
49. What is V model in manual testing ?
50. What is a frame work at what situations we will use?
51. What is a test plan who will prepare that one?
52. What is alpha tesging and beta testing ?
53. What is application entry and exit criteria?
54. What is compatibility testing?
55. What is debugging?
56. What is determination?
57. What is exact difference between Debugging & Testing?
58. What is fish model can you explain?
59. What is frame work in qtp.
60. What is functional testing,system testing,datadriven testing?
61. What is integration testing?
62. What is mean by gui testing ? What is mean by client/Server? What is meat by web based
application ?
63. What is objective of actions in qtp ?
64. What is performance testing?
65. What is port testing?
66. What is prototype model in manual testing?
67. What is regualr expression and when we will use regularexpression in qtp?
68. What is reusable action in qtp?
69. What is stand alone mode running in load runner?
70. What is stress testing?
71. What is stub and driver in manual testing?
72. What is system testing?
73. What is test bed?
74. What is test development?
75. What is test metrics ?
76. What is test strategy who will prepare that one. And what will be there in test strategy.
77. What is the Testcase Life Cycle.
78. What is the definition for test life cycle?
79. What is the difference between constant and parameter in qtp?
80. What is the difference between properties and methods in qtp?
81. What is the difference between smoke testing and sanitary testing ?
82. What is the difference between test scenarios and test strategy?
83. What is the difference between usability testing and GUI?
84. What is the model of spiral binding in manual testing? Can you explain spiral binding?
85. What is unit testing in manual?
86. What is unit testing?
87. What is virtual memory?
88. What is virtual object and at what we will use virtual object in qtp?
89. What is virtual object and when will we use?
90. What is visual source safe?
91. What part of the testing phase is the most important part for testing in the cycle?
92. What type of testing questions will be asked for 2+ yrs exp people in interview?
93. When we do update mode in qtp?
94. Where do check points store in qtp ?
95. Who are prepared use case?
96. Why do need synchronization in qtp?
97. Why do u use object spy in qtp?
98. can u explain spiral binding model in manual testing developers looking to do= testing)
99. how i can do gui testing,what is its important contant,plz tell me all property of Gui
testing
100. how to wrtie test case with a minimum of 13 columns.......
101. supports Java Script? What is extention for test script in Quick Test?
102. what is the Testcase Life Cycle ?
103. what is the differene between scenario and testcase ?
104. whta is open beta testing? ans it done at which end? what is the difference b/w
open beta testing and beta testing?
105. why do u save .vbs in library files in qtp winrunner

Software Testing Interview Questions And Answers

Black Box Testing Software Testing Books Software Testing Document Software Testing Notes

   Important 40 Testing Interview Questions


Last Updated on Sunday, 9 March 2008 07:10 Written by EditorMonday, 22 October 2007 05:29

What’s Ad Hoc Testing ?

A testing where the tester tries to break the software by randomly trying functionality of
software.

What’s the Accessibility Testing ?

Testing that determines if software will be usable by people with disabilities.

What’s the Alpha Testing ?

The Alpha Testing is conducted at the developer sites and in a controlled environment by the end
user of the software

What’s the Beta Testing ?

Testing the application after the installation at the client place.


What is Component Testing ?

Testing of individual software components (Unit Testing).

What’s Compatibility Testing ?

In Compatibility testing we can test that software is compatible with other elements of system.

What is Concurrency Testing ?

Multi-user testing geared towards determining the effects of accessing the same application code,
module or database records. Identifies and measures the level of locking, deadlocking and use of
single-threaded code and locking semaphores.

What is Conformance Testing ?

The process of testing that an implementation conforms to the specification on which it is based.
Usually applied to testing conformance to a formal standard.

What is Context Driven Testing ?

The context-driven school of software testing is flavor of Agile Testing that advocates
continuous and creative evaluation of testing opportunities in light of the potential information
revealed and the value of that information to the organization right now.

What is Data Driven Testing ?

Testing in which the action of a test case is parameterized by externally defined data values,
maintained as a file or spreadsheet. A common technique in Automated Testing.

What is Conversion Testing ?

Testing of programs or procedures used to convert data from existing systems for use in
replacement systems.

What is Dependency Testing ?

Examines an application’s requirements for pre-existing software, initial states and configuration
in order to maintain proper functionality.

What is Depth Testing ?

A test that exercises a feature of a product in full detail.

What is Dynamic Testing ?


Testing software through executing it. See also Static Testing.

What is Endurance Testing ?

Checks for memory leaks or other problems that may occur with prolonged execution.

What is End-to-End testing ?

Testing a complete application environment in a situation that mimics real-world use, such as
interacting with a database, using network communications, or interacting with other hardware,
applications, or systems if appropriate.

What is Exhaustive Testing ?

Testing which covers all combinations of input values and preconditions for an element of the
software under test.

What is Gorilla Testing ?

Testing one particular module, functionality heavily.

What is Installation Testing ?

Confirms that the application under test recovers from expected or unexpected events without
loss of data or functionality. Events can include shortage of disk space, unexpected loss of
communication, or power out conditions.

What is Localization Testing ?

This term refers to making software specifically designed for a specific locality.

What is Loop Testing ?

A white box testing technique that exercises program loops.

What is Mutation Testing ?

Mutation testing is a method for determining if a set of test data or test cases is useful, by
deliberately introducing various code changes (‘bugs’) and retesting with the original test
data/cases to determine if the ‘bugs’ are detected. Proper implementation requires large
computational resources

What is Monkey Testing ?

Testing a system or an Application on the fly, i.e just few tests here and there to ensure the
system or an application does not crash out.
What is Positive Testing ?

Testing aimed at showing software works. Also known as “test to pass”. See also Negative
Testing.

What is Negative Testing ?

Testing aimed at showing software does not work. Also known as “test to fail”. See also Positive
Testing.

What is Path Testing ?

Testing in which all paths in the program source code are tested at least once.

What is Performance Testing ?

Testing conducted to evaluate the compliance of a system or component with specified


performance requirements. Often this is performed using an automated test tool to simulate large
number of users. Also know as “Load Testing”.

What is Ramp Testing ?

Continuously raising an input signal until the system breaks down.

What is Recovery Testing ?

Confirms that the program recovers from expected or unexpected events without loss of data or
functionality. Events can include shortage of disk space, unexpected loss of communication, or
power out conditions.

What is the Re-testing testing ?

Retesting- Again testing the functionality of the application.

What is the Regression testing ?

Regression- Check that change in code have not effected the working functionality

What is Sanity Testing ?

Brief test of major functional elements of a piece of software to determine if its basically
operational.

What is Scalability Testing ?


Performance testing focused on ensuring the application under test gracefully handles increases
in work load.

What is Security Testing ?

Testing which confirms that the program can restrict access to authorized personnel and that the
authorized personnel can access the functions available to their security level.

What is Stress Testing ?

Stress testing is a form of testing that is used to determine the stability of a given system or
entity. It involves testing beyond normal operational capacity, often to a breaking point, in order
to observe the results.

What is Smoke Testing ?

A quick-and-dirty test that the major functions of a piece of software work. Originated in the
hardware testing practice of turning on a new piece of hardware for the first time and considering
it a success if it does not catch on fire.

What is Soak Testing ?

Running a system at high load for a prolonged period of time. For example, running several
times more transactions in an entire day (or night) than would be expected in a busy day, to
identify and performance problems that appear after a large number of transactions have been
executed.

What’s the Usability testing ?

Usability testing is for user friendliness.

What’s the User acceptance testing ?

User acceptance testing is determining if software is satisfactory to an end-user or customer.

What’s the Volume Testing ?

We can perform the Volume testing, where the system is subjected to large volume of data.

Preparing For Software Testing Interview – Simple Tips To


Follow Prior And at The Time of Interview
October 25th, 2009 — Career in software Testing, Testing Interview questions

This is a guest article by “N. Sandhya Rani”.


As Software testers, we keep performing testing activities in various phases of a project. When it
comes to testing our own skills, we may not end up choosing an appropriate approach. I am
talking about how the interview rounds go and how to face them. The whole article is a very
general discussion about the challenges that a tester has to face in an interview.

Let’s start with preparing a CV for software testing job profile.

How to prepare a good CV?


By the term ‘Good’ I mean a CV that describes best about your skills, your expertise, your
strengths etc. It’s better not to use a same CV for different types of job profiles. Making slight
changes will help to get a call. For e.g. you can highlight the skill set that you posses for the
required job like any automation tool or experience in other related automation tools. You can
also add about the basic knowledge of any technologies that you posses. This may be an added
advantage.

Preparation before the job interview:

Before attending the interview, check the job profile in detail. Understand if the requirement is
purely in manual testing, Automation testing or on both. Check if your job profile experience
match with what is expected.
The interviewer will mostly stick to questions around the given job profile and what you have
mentioned in your CV.  Make sure you can answer questions confidently which are based on
your CV. It depends on how the discussion goes between the candidate and the interviewer,
which leads to discussion in other areas.

Appear confidently at the time of interview:

In most cases, the interview starts with a brief up about the candidate. One can answer to this
question by following a sequence like starting with your Name, what qualifications do you
posses, how you started your career as a software tester etc. Some interviewers do not like to
hear about personal details like family. So do not proceed with these details unless the
interviewer asks for it.

While answering any question tell what you know. Do not try to explain about ideal cases.
Interviewers are interested in practical approach, rather than ideal cases. Tell the interviewer how
you will go about solving the problems or about your way of tackling things. Do not talk
anything negative about any person especially about developers/programmers. If you do so, then
it shows that you are not mature enough. Now a days in most of the interviews, scenarios are
cited rather than direct question and answer. If the scenario is new to you, take few seconds to
think on it and then answer. Do not hurry up things.

The way you present in interviews is very important. Right attitude is very important too. Many
managers can judge it easily, if you have really worked on projects or it’s just a fake experience.
The confidence level with which you answer makes a strong impression. For any question if you
are not sure about the correct answer, just make an attempt. Do not just give up. You can also
talk about things that you explored in free time or with your interest. This shows that you take
initiative and are a continuous learner as well.

As many of us must have experienced that the interviewers keep asking about the processes that
you have followed or are familiar with. One does not need to worry if they have never followed
any processes. Following the processes is up to the company and a tester cannot do much
regarding that. But of course one can follow some processes for his/her own task (I mean the
modules that you own or are in charge of etc). This will not only help to manage things but also
inspires other to follow some processes. Any process, which has proven some good results, can
be followed. So, instead of blaming others for not following any processes, one can take an
initiative to do it. Do not forget that Initiative is one of the qualities that a tester should possess.

One more important point: It’s not necessary that the person who is taking your interview is a
person from QA background. A person from developing background can also take software
testing job interviews. What I mean to say is the person need not have actually worked on the
QA processes. In such case it becomes very important to answer the questions very carefully. It
may sound illogical when a person from non-QA background interviews a tester but remember it
will be a very good experience as you will get to know how testing is perceived by others.

Over to You:
What’s your experience about software testing interviews? If you want to share some do’s and
don’ts please make comments below so that other testers can get benefit from your experience.
And finally ‘all the best’ for your testing career!

108 Comments

ISTQB software testing certification sample question paper


with answers – Part II
July 15th, 2009 — QA certifications, Questions & answers, Testing Interview questions

In continuation with our Previous article on “ISTQB software testing certification sample
papers and tips to solve the questions quickly“, we are posting next set of ISTQB exam
sample questions and answers with detailed evaluation for each option.

This is a guest article by “N. Sandhya Rani”.

ISTQB ‘Foundation level’ sample questions with answers and detailed evaluation of each
option:

1. Methodologies adopted while performing Maintenance Testing:-


a) Breadth Test and Depth Test
b) Retesting
c) Confirmation Testing
d) Sanity Testing
Evaluating the options:
Continue reading →

186 Comments

ISTQB question pattern and tips to solve


July 8th, 2009 — QA certifications, Questions & answers, Testing Interview questions

Please welcome ‘Sandhya’ on softwaretestinghelp.com writer’s board. Sandhya is having


extensive experience in software testing field and helping many software testers in clearing the
testing certification exams like ISTQB.

Sandhya will be giving you ISTQB paper pattern and tips on how to solve the questions
quickly. To start with, here are 10 sample ISTQB ‘Foundation level’ questions with detailed
explanation for answers.

ISTQB question pattern and tips to solve:


ISTQB questions are formatted in such a way that the answers look very much similar. People
often choose the one, which they are more familiar with. We should carefully read the question
twice or thrice or may be more than that, till we are clear about what is being asked in the
question.

Now look at the options carefully. The options are chosen to confuse the candidates. To choose
the correct answer, we should start eliminating one by one. Go through each option and check
whether it is appropriate or not. If you end up selecting more than one option, repeat the above
logic for the answers that you selected. This will definitely work.

Before you start with the question papers, please read the material thoroughly. Practice as many
papers as possible. This will help a lot because, when we actually solve the papers, we apply the
logic that we know.

ISTQB ‘Foundation level’ sample questions with answers:

1. Designing the test environment set-up and identifying any required infrastructure and
tools are a part of which phase

a) Test Implementation and execution


b) Test Analysis and Design
c) Evaluating the Exit Criteria and reporting
d) Test Closure Activities

Evaluating the options:


a) Option a: as the name suggests these activities are part of the actual implementation cycle. So
do not fall under set-up
b) Option b: Analysis and design activities come before implementation. The test environment
set-up, identifying any required infrastructure and tools are part of this activity.
c) Option c: These are post implementation activities
d) Option d: These are related to closing activities. This is the last activity.

So, the answer is ‘B’

2. Test Implementation and execution has which of the following major tasks?

i. Developing and prioritizing test cases, creating test data, writing test procedures and optionally
preparing the test harnesses and writing automated test scripts.
ii. Creating the test suite from the test cases for efficient test execution.
iii. Verifying that the test environment has been set up correctly.
iv. Determining the exit criteria.

a) i,ii,iii are true and iv is false


b) i,,iv are true and ii is false
c) i,ii are true and iii,iv are false
d) ii,iii,iv are true and i is false

Evaluating the options:


Let’s follow a different approach in this case. As can be seen from the above options,
determining the exit criteria is definitely not a part of test implementation and execution. So
choose the options where (iv) is false. This filters out ‘b’ and ‘d’.

We need to select only from ‘a’ and ‘c’. We only need to analyze option (iii) as (i) and (ii) are
marked as true in both the cases. Verification of the test environment is part of the
implementation activity. Hence option (iii) is true. This leaves the only option as ‘a’.

So, the answer is ‘A’

3. A Test Plan Outline contains which of the following:-

i. Test Items
ii. Test Scripts
iii. Test Deliverables
iv. Responsibilities

a) I,ii,iii are true and iv is false


b) i,iii,iv are true and ii is false
c) ii,iii are true and i and iv are false
d) i,ii are false and iii , iv are true

Evaluating the options:


Let’s use the approach given in question no. 2. Test scripts are not part of the test plan (this must
be clear). So choose the options where (ii) is false. So we end up selecting ‘b’ and ‘d’. Now
evaluate the option (i), as option (iii) and (iv) are already given as true in both the cases. Test
items are part of the test plan. Test items are the modules or features which will be tested and
these will be part of the test plan.

So, the answer is ‘B’

4. One of the fields on a form contains a text box which accepts numeric values in the range
of 18 to 25. Identify the invalid Equivalence class
a) 17
b) 19
c) 24
d) 21

Evaluating the options:


In this case, first we should identify valid and invalid equivalence classes.

Invalid Class | Valid Class | Invalid Class


Below 18 | 18 to 25 | 26 and above

Option ‘a’ falls under invalid class. Options ‘b’, ‘c’ and ‘d’ fall under valid class.

So, the answer is ‘A’

5. In an Examination a candidate has to score minimum of 24 marks in order to clear the


exam. The maximum that he can score is 40 marks. Identify the Valid Equivalence values if
the student clears the exam.

a) 22,23,26
b) 21,39,40
c) 29,30,31
d) 0,15,22

Evaluating the options:


Let’s use the approach given in question 4. Identify valid and invalid equivalence classes.

Invalid Class | Valid Class | Invalid Class


Below 24 | 24 to 40 | 41 and above

The question is to identify valid equivalence values. So all the values must be from ‘Valid class’
only.

a) Option a: all the values are not from valid class


b) Option b: all the values are not from valid class
c) Option c: all the values are from valid class
d) Option d: all the values are not from valid class

So, the answer is ‘C’


6. Which of the following statements regarding static testing is false:

a) static testing requires the running of tests through the code


b) static testing includes desk checking
c) static testing includes techniques such as reviews and inspections
d) static testing can give measurements such as cyclomatic complexity

Evaluating the options:


a) Option a: is wrong. Static testing has nothing to do with code
b) Option b: correct, static testing does include desk checking
c) Option c: correct, it includes reviews and inspections
d) Option d: correct, it can give measurements such as cyclomatic complexity

So, the answer is ‘A’

7. Verification involves which of the following:-


i. Helps to check the Quality of the built product
ii. Helps to check that we have built the right product.
iii. Helps in developing the product
iv. Monitoring tool wastage and obsoleteness.

a) Options i,ii,iii,iv are true.


b) i is true and ii,iii,iv are false
c) i,ii,iii are true and iv is false
d) ii is true and i,iii,iv are false.

Evaluating the options:


a) Option a: The quality of the product can be checked only after building it.
Verification is a cycle before completing the product.
b) Option b: Verification checks that we have built the right product.
c) Option c: it does not help in developing the product
d) Option d: it does not involve monitory activities.

So, the answer is ‘B’

8. Component Testing is also called as :-


i. Unit Testing
ii. Program Testing
iii. Module Testing
iv. System Component Testing .

a) i,ii,iii are true and iv is false


b) i,ii,iii,iv are false
c) i,ii,iv are true and iii is false
d) all of above is true
Evaluating the options:
a) Option a: correct, component testing is also called as unit testing
b) Option b: not sure (but as all the options indicate this as true, we can conclude that Program
testing is also called as unit testing)
c) Option c: correct, component testing is also called as module testing
d) Option d: wrong. System component testing comes under system testing.

So, the answer is ‘A’

9. Link Testing is also called as :


a) Component Integration testing
b) Component System Testing
c) Component Sub System Testing
d) Maintenance testing

Evaluating the options:


As the name suggests, this testing is performed by linking (say modules). Now if
we look at the options, only option ‘a’ is performed by linking or integrating
modules/components.

So, the answer is ‘A’

10.

What is the expected result for each of the following test cases?
A.TC1: Anand is a 32 year old married, residing in Kolkatta.
B.TC3: Attapattu is a 65 year old married person, residing in Colombo.
a) A – Issue membership, 10% discount, B–Issue membership, offer no discount. B
b) A – Don’t Issue membership, B – Don’t offer discount. C
c) A – Issue membership, no discount, B – Don’t Issue membership.
d) A – Issue membership, no discount, B- Issue membership with 10% discount.

Evaluating the options:


Explanation:
For TC1: follow the path in green color
(The person is Indian resident, so select only ‘True’ options.
The person is aged between 18-55, so select only ‘True’
The person is a married, so again select only ‘True’
For this person, the actions under ‘Rule 4′ will be applied. That is, issue membership and no
discount)

For TC3: follow the path in blue color


(The person is not Indian resident, so select only ‘False’ (under Rule 1)
The person is not aged between 18-55. No need to select any path, as it is written “Don’t care”.
The person is married. No need to select any path, as it is written “Don’t care”.
For this person, the actions under ‘Rule1′ will be applied, That is, Don’t issue membership and
no discount.)

So, the answer is ‘C’

Note: The answers are based on writers own experience and judgment and may not be 100%
correct. If you feel any correction is required please discuss in comments below.

Please feel free to ask any question related to ISTQB exam and testing certifications in
comment section below.

139 Comments

What is Boundary value analysis and Equivalence


partitioning?
October 22nd, 2008 — Questions & answers, Testing Concepts, Testing Interview questions

Boundary value analysis and Equivalence partitioning, explained with simple example:

Boundary value analysis and equivalence partitioning both are test case design strategies in black
box testing.
Equivalence Partitioning:

In this method the input domain data is divided into different equivalence data classes. This
method is typically used to reduce the total number of test cases to a finite set of testable test
cases, still covering maximum requirements.

Continue reading →

119 Comments

How to hire the right candidates for software testing


positions?
September 21st, 2008 — Career in software Testing, Questions & answers, Testing Interview
questions

Do companies really judge candidate’s testing ability in interviews? Do they ask the questions
that really judge the candidate’s skill? What questions should be asked to judge the candidate for
software testing field? What is the key process to hire good candidates for software testing
positions?

Ok, I am asking to many questions without giving answer to any of it. Well, each question
mentioned above will require a separate post to address the problem fairly. Here we will address
in short about – How to hire the right candidates for software testing positions?

Companies or interviewers, who are not serious about hiring right candidates, often end with
hiring poor performers.

What I mean by “Not serious” here?


- They don’t know why and for what post they are hiring a candidate.
- They either fake or fail to post the exact job opening details.
- Or they don’t want to hire skilled performers at all. Hmm, jealousy might be the key here!

Whichever is the reason, there is definitely loss of organization. Loss in terms of both revenue
and growth.

If you need answer to these questions, here is an informative video from Pradeep Soundararajan
– Consulting tester of Satisfice Inc in India. He explained what is the current situation of
software testing interview process in India and how interviewers are wrong in selecting questions
to be asked to candidates. A nice start to spread the awareness and importance of software testing
interviews.

Current Software Testing Interview situation:

Click on the bottom right button to see the video in full screen.
You can watch his more video’s on software testing here.

Do not forget to comment your experience on software testing interviews, either as an


interviewer or as a candidate.

Related article: Choosing software testing as your career.

51 Comments

Smoke testing and sanity testing – Quick and simple


differences
May 31st, 2008 — Basics of Software testing, Questions & answers, Testing Concepts, Testing
Interview questions

Despite of hundreds of web articles on Smoke and sanity testing, many people still have
confusion between these terms and keep on asking to me. Here is a simple and understandable
difference that can clear your confusion between smoke testing and sanity testing.

Here are the differences you can see:

SMOKE TESTING:

 Smoke testing originated in the hardware testing practice of turning on a new piece of
hardware for the first time and considering it a success if it does not catch fire and smoke.
In software industry, smoke testing is a shallow and wide approach whereby all areas of
the application without getting into too deep, is tested.
 A smoke test is scripted, either using a written set of tests or an automated test
 A Smoke test is designed to touch every part of the application in a cursory way. It’s
shallow and wide.
 Smoke testing is conducted to ensure whether the most crucial functions of a program are
working, but not bothering with finer details. (Such as build verification).
 Smoke testing is normal health check up to a build of an application before taking it to
testing in depth.

SANITY TESTING:

 A sanity test is a narrow regression test that focuses on one or a few areas of
functionality. Sanity testing is usually narrow and deep.
 A sanity test is usually unscripted.
 A Sanity test is used to determine a small section of the application is still working after a
minor change.
 Sanity testing is a cursory testing, it is performed whenever a cursory testing is sufficient
to prove the application is functioning according to specifications. This level of testing is
a subset of regression testing.
 Sanity testing is to verify whether requirements are met or not, checking all features
breadth-first.

Hope these points will help you to clearly understand the Smoke and sanity tests and will help to
remove any confusion.

Thanks to VijayD for answering this question in simple way for our readers.

If you have more points on smoke and sanity testing to elaborate on, please comment below.

106.

S-ar putea să vă placă și