QTP Interview Questions

If I give some thousand tests to execute in 2 days what do u do? - Adhoc testing is done. It Covers the least basic functionalities to verify that the system is working fine.

What does it mean when a check point is in red color? what do u do? - A red color indicates failure. Here we analyze the cause for failure whether it is a Script Issue or Environment Issue or a Application issue.

What is Object Spy in QTP? - Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object’s hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.

What is the file extension of the code file & object repository file in QTP? - Code file extension is.vbs and object repository is.tsr

Explain the concept of object repository & how QTP recognizes objects? - Object Repository: displays a tree of all objects in the current component or in the current action or entire test (depending on the object repository mode you selected). We can view or modify the test object description of any test object in the repository or to add new objects to the repository. Quicktest learns the default property values and determines in which test object class it fits. If it is not enough it adds assistive properties, one by one to the description until it has compiled the unique description. If no assistive properties are available, then it adds a special Ordinal identifier such as objects location on the page or in the source code.

What are the properties you would use for identifying a browser & page when using descriptive programming? - Name would be another property apart from title that we can use.

Give me an example where you have used a COM interface in your QTP project? - com interface appears in the scenario of front end and back end. for eg:if you r using oracle as back end and front end as VB or any language then for better compatibility we will go for an interface. of which COM will be one among those interfaces. Create object creates handle to the instance of the specified object so that we program can use the methods on the specified object. It is used for implementing Automation(as defined by Microsoft).

Explain in brief about the QTP Automation Object Model. - Essentially all configuration and run functionality provided via the Quick Test interface is in some way represented in the Quick Test automation object model via objects, methods, and properties. Although a one-on-one comparison cannot always be made, most dialog boxes in Quick Test have a corresponding automation object, most options in dialog boxes can be set and/or retrieved using the corresponding object property, and most menu commands and other operations have corresponding automation methods. You can use the objects, methods, and properties exposed by the Quick Test automation object model, along with standard programming elements such as loops and conditional statements to design your program.

Interview Questions @ CA this week

Questions gathered from interview at CA, Hyd this week.

1. Why S/W need testing?
2. How will you choose your test team?
3. Testplan shouldn't contain?
4. Extension for Object Repository in QTP? Ans: .TSR
5. How will you communicate with client in deadline situations?
6. QTP uses which script?
7. QTP and QC Integration?
8. What are list of Functional testing tools?

Will post remaining in next article. Happy Reading!

Source
Don't miss any article:Get it by E-mail

Software testing book for preparing testing interviews and learning basics of software testing [download]

I am in process to compile a list of good books on software testing. Soon I will share this list with you. But lately I am getting too many requests to share any book on software testing for preparing software testing interviews. So here is a quick post to share an online testing book I found “A Software Testing Primer” by Nick Jenkins.
Basically this book is an introduction to software testing. So those who are new to software testing field can start their preparation by reading this book. You will get basic idea of manual and automation testing.
Here is a summary of what this book is covering:

1. What is the need of software testing?
2. Different software development models
3. Testing in the software development life cycle
4. How to develop testing mindset?
5. Regression Vs. Retesting
6. White box Vs. Black box testing
7. Verification and validation
8. Alpha and beta testing
9. Unit, Integration and System testing
10. Acceptance testing
11. Automation testing - Basics
12. Testing the design
13. Usability testing
14. Performance testing
15. Test planning
16. Test estimation
17. Test cases and elements of test cases
18. Test tracking, Test planning and Test plan review
19. How to manage defects and defect reports?
20. Test metrics for testers
21. Product release control

In all this book is a nice introduction to software testing. Author explained some key software testing concepts like Regression and Retesting difference, Alpha and beta testing etc. where many testers get confused.

Download “Testing Primer” book:To download this book Click here
What is your favorite software testing book? Also share your ‘best software testing book’ experience with our readers.

Source SoftwareTestingHelp
Don't miss any article:Get it by E-mail

Interview Questions @ Infosys on this Saturday

These are the question TJG received from a source who attended for Test Engineer at Infosys,Hyd campus. According to interviewer was very cool and he got selected in that.
Total 3 rounds of interview and in that first 2 are technical followed by HR round.
Questions as follows:

1. How you came to this testing?
2. What is Testing?
3. Types of Testing?
4. What is system testing?
5. Write test cases for yahoo messenger login?
6. Tell me a real scenario which you ever faced?
7. Great bug you found in your career?
8. Problems in Communication with client?
9. What is web testing?
10. What should a successful Test Engineer should do?
11. What is Bi-directional tracability matrix?

Ofcourse you will expect answers for these questions, But i don't have enough time to link them here. You can find all these answers in this site itself. Just browse through Interview Questions section.

Don't miss any article:Get it by E-mail

Interview Questions at NCR Corp,Hyd this week

Following are the interview questions asked at NCR Corp Hyderabad for an Senior Test Engineer position. One of my friend attended it and shared the questions with me.

1. What is Static Testing?
2. What is Dynamic Testing?
3. Diff b/w above two?
4. When we should go for Automation Testing and When we shouldn't?
5. What will you do before start testing? He is asking for docs preparation!
6. What is Tracability matrix?
7. What is agile testing process?
8. What is SDLC and how many models available?
9. What is peer review and who shouldn't attend that meeting?
10. Your short term goals?
11. Why NCR?

Actually the requirement was for Manual Test Engineer with 3+ exp.Interviewer was a bit typical person and targetting candidate with saying no & wrong for every answer.

More over they are expecting candidate with good talent for less that 4 lacks Pa package.All positions were based on Hyderabad.

They are conducting one more drive on this sunday.Good luck!

Don't miss any article:Get it by E-mail

This week interview question @ DST Global Solutions HYD

1. What is a bug?
A computer bug is an error, flaw, mistake, failure, or fault in a computer program that prevents it from working correctly or produces an incorrect result.

2.What is a test case?
Test case is set of input values, execution preconditions, expected results and executionPost conditions, developed for a particular objective or test conditions, such as to exercise a particular program path or to verify compliance with a specific requirement.

3. What is the purpose of test plan in your project?
Test plan document is prepared by the test lead, it contains the contents like introduction, objectives, test strategy, scope, test items, program modules user procedures, features to be tested features not to tested approach, pass or fail criteria, testing process, test deliverables, testing, tasks, responsibilities,resources,schedule, environmental requirements, risks & contingencies, change management procedures, plan approvals, etc all these things help a test manager understand the testing he should do & what he should follow for testing that particular project.

4. When the relationships occur between tester and developer?
Developer is the one who sends the application to the tester by doing all the necessary code in the application and sends the marshal id to the tester. The tester is the one who gives all the input/output and checks whether he is getting required output or not. A developer is the one who works on inside interfacing where as the tester is the one who works on outside interfacing

5. When testing will starts in a project?
The testing is not getting started after the coding. After release the build the testers perform the smoke test. Smoke test is the first test which is done by the testing team. This is according to the testing team. But, before the releasing of a build the developers will perform the unit testing.

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail

Effective Web page testing

How do we conduct effective testing in a Web page/form when we have many different fields -- textboxes, dropdown, ListBox, etc. Do we need to implement the equivalence class partitioning and boundary value analysis for all the fields?

The short answer: All testing is risk-based; we cannot test everything. So we make educated assumptions. Certain fields may contain data which is not persisted in the database -- these fields might be lower-risk and perhaps do not need as much testing as others. Or the developer who coded the form may be poorly familiar with field validation and you may need to test more.

The long answer? Yes, each and every field should be tested. It is the challenge of a tester to rise to the occasion and develop methodologies and tools which make him or her more efficient and more effective. Through the use of automation, it may be possible to test each field for boundary and equivalence class partitions. Perhaps by writing code which creates the HTTP POST or GET, rather than filling in each form, this coverage can be obtained. Or using data-driven testing and Selenium or Watij (Watin, Watir, etc.) it might be possible to automated the form once and loop through a series (or generate a series of data programmatically) to test boundaries and equivalence classes. Also, making use of PICT tools (pairwise, interdependent, combinatorial testing) can help you use science to narrow the field of tests you need to run to gain adequate coverage.

The key to rising above other testers and QA engineers is to tackle these challenges head-on. There are many who think testers are just developers who "couldn't cut it" as developers. Unfortunately, in some cases, this is true. But the true tester will take these complicated challenges and rise above them, and will come up with creative ways to apply their engineering skills to accomplish the work at hand. And even when it's not possible to test everything, a good tester will know through logic, experience, and science when testing is complete.

So the full answer is simple, but not easy. Be smart and make use of any and all tools around you. Figure out what you can accomplish in the time given, and get to it. Be scientific and think through the problem, and leverage technology to implement the solution. The goal is to have tested as much as possible in the time provided, and you will be amazed what you can do if you just take some time to figure it out.

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail

133 Software Testing Interview Questions

I have so many questions in my mind when I think of any interview questions for Software testing / QA Engineer.These are all the questions extracted from the web and these are most asked interview questions too. Would you be able to answer all of them?

If you know the answers please post your ans along with the question number.
Ofcourse am giving links to some of the questions to find the correct answer.
Do post your answers and help the people in finding answers.

And also do mention your mail id in comment to get the answers for all the 133 Questions.
Best of luck..!!

1. What is Software Testing?
2. What is the Purpose of Testing?
3. What types of testing do testers perform?
4. What is the Outcome of Testing?
5. What kind of testing have you done?
6. What is the need for testing?
7. What are the entry criteria for Functionality and Performance testing?
8. What is test metrics?
9. Why do you go for White box testing, when Black box testing is available?
10. What are the entry criteria for Automation testing?
11. When to start and Stop Testing?
12. What is Quality?
13. What is Baseline document, Can you say any two?
14. What is verification?
15. What is validation?
16. What is quality assurance?
17. What is quality control?
18. What is SDLC and TDLC?
19. What are the Qualities of a Tester?
20. When to start and Stop Testing?
21. What are the various levels of testing?
22. What are the types of testing you know and you experienced?
23. What exactly is Heuristic checklist approach for unit testing?
24. After completing testing, what would you deliver to the client?
25. What is a Test Bed?
26. What is a Data Guidelines?
27. Why do you go for Test Bed?
28. What is Severity and Priority and who will decide what?
29. Can Automation testing replace manual testing? If it so, how?
30. What is a test case?
31. What is a test condition?
32. What is the test script?
33. What is the test data?
34. What is an Inconsistent bug?
35. What is the difference between Re-testing and Regression testing?
36. What are the different types of testing techniques?
37. What are the different types of test case techniques?
38. What are the risks involved in testing?
39. Differentiate Test bed and Test Environment?
40. What ifs the difference between defect, error, bug, failure, fault?
41. What is the difference between quality and testing?
42. What is the difference between White & Black Box Testing?
43. What is the difference between Quality Assurance and Quality Control?
44. What is the difference between Testing and debugging?
45. What is the difference between bug and defect?
46. What is the difference between verification and validation?
47. What is the difference between functional spec. and Business requirement specification?
48. What is the difference between unit testing and integration testing?
49. What is the diff between Volume & Load?
50. What is diff between Volume & Stress?
51. What is the diff between Stress & Load Testing?
52. What is the Diff between Two Tier & Three tier Architecture?
53. What is the diff between Client Server & Web Based Testing?
54. What is the diff between Integration & System Testing?
55. What is the Diff between Code Walkthrough & Code Review?
56. What is the diff between walkthrough and inspection?
57. What is the Diff between SIT & IST?
58. What is the Diff between static and dynamic?
59. What is the diff between alpha testing and beta testing?
60. What are the Minimum requirements to start testing?
61. What is Smoke Testing & when it will be done?
62. What is Adhoc Testing? When it can be done?
63. What is cookie testing?
64. What is security testing?
65. What is database testing?
66. What is the relation ship between Quality & Testing?
67. How do you determine, what to be tested?
68. How do you go about testing a project?
69. What is the Initial Stage of testing?
70. What is Web Based Application Testing?
71. What is Client Server Application Testing?
72. What is Two Tier & Three tier Architecture?
73. What is the use of Functional Specification?
74. Why do we prepare test condition, test cases, test script (Before Starting Testing)?
75. Is it not waste of time in preparing the test condition, test case & Test Script?
76. How do you go about testing of Web Application?
77. How do you go about testing of Client Server Application?
78. What is meant by Static Testing?
79. Can the static testing be done for both Web & Client Server Application?
80. In the Static Testing, what all can be tested?
81. Can test condition, test case & test script help you in performing the static testing?
82. What is meant by dynamic testing?
83. Is the dynamic testing a functional testing?
84. Is the Static testing a functional testing?
85. What are the functional testing you perform?
86. What is meant by Alpha Testing?
87. What kind of Document you need for going for an Functional testing?
88. What is meant by Beta Testing?
89. At what stage the unit testing has to be done?
90. Who can perform the Unit Testing?
91. When will the Verification & Validation be done?
92. What is meant by Code Walkthrough?
93. What is meant Code Review?
94. What is the testing that a tester performs at the end of Unit Testing?
95. What are the things, you prefer & Prepare before starting Testing?
96. What is Integration Testing?
97. What is Incremental Integration Testing?
98. What is meant by System Testing?
99. What is meant by SIT?
100. When do you go for Integration Testing?
101. Can the System testing be done at any stage?
102. What are stubs & drivers?
103. What is the Concept of Up-Down & Down-Up in Testing in integration testing?
104. What is the final Stage of Integration Testing?
105. Where in the SDLC, the Testing Starts?
106. What is the Outcome of Integration Testing?
107. What is meant by GUI Testing?
108. What is meant by Back-End Testing?
109. What are the features, you take care in Prototype testing?
110. What is Mutation testing & when can it be done?
111. What is Compatibility Testing?
112. What is Usability Testing?
113. What is the Importance of testing?
114. What is meant by regression Testing?
115. When we prefer Regression & what are the stages where we go for Regression Testing?
116. What is performance testing?
117. What is the Performance testing; those can be done Manually & Automatically?
118. What is Volume, Stress & Load Testing?
119. What is a Bug?
120. What is a Defect?
121. What is the defect Life Cycle?
122. What is the Priority in fixing the Bugs?
123. Explain the Severity you rate for the bugs found?
124. Diff between UAT & IST?
125. What is meant by UAT?
126. What all are the requirements needed for UAT?
127. What are the docs required for Performance Testing?
128. What is risk analysis?
129. How to do risk management?130. What are test closure documents?
130. What is traceability matrix?
131. What ways you followed for defect management?and finally
132. What is diff betn Smoke Testing and Sanity Testing?
133. What is the though situation you ever faced in testing?

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail

Topics to learn before attending interview

Testing is not a simple subject:
Anyway i will try to list important and most real time using things:

1. Testing Terminology
2. SDLC Models
3. Test Life cycle(STLC)
4. V-Model for testing
5. Defect Life cycle
6. Test case Preparation
7. a. Functional Test Case Preparation
8. b. GUI Test Case Preparation
9. Test Data Preparation
10. Test case Review
11. Test Case Execution
12. Smoke/Sanity Testing
13. Retesting ,Regression Testing Process
14. Bug/Defect Report writing
15. Bug or Defect Reporting and Tracking
16. Test summary Report Preparation
17. Excel using skills

The above mentioned things are minimum that you should learn to survive in software testing profession.Please try to learn atlest above things before going to any testing interview.

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail

Testing vs QA vs QC

Testing: The process of executing a system with the intent of finding defects including test planning prior to the execution of the test cases.

Quality Control: A set of activities designed to evaluate a developed working product.

Quality Assurance: A set of activities designed to ensure that the development and/or maintenance process is adequate to ensure a system will meet its objectives.

The key difference to remember is that QA is interested in the process whereas testing and quality control are interested in the product. Having a testing component in your development process demonstrates a higher degree of quality (as in QA).

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail

What is Re- test ? What is Regression Testing ?

Re- test:Retesting means we testing only the certain part of an application again and not considering how it will effect in the other part or in the whole application.

Regression Testing:Testing the application after a change in a module or part of the application for testing that is the code change will affect rest of the application.

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail

What is Ad-hoc testing?

Ad hoc testing is concern with the Application Testing without following any rules or test cases.

For Ad hoc testing one should have strong knowledge about the Application.

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail

What is Test bed and Test data ?

Test Bed is an execution environment configured for software testing. It consists of specific hardware, network topology, Operating System, configuration of the product to be under test, system software and other applications. The Test Plan for a project should be developed from the test beds to be used.

Test Data is that run through a computer program to test the software. Test data can be used to test the compliance with effective controls in the software.

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail

What is AUT ?

AUT is nothing but "Application Under Test". After the designing and coding phase in Software development life cycle, the application comes for testing then at that time the application is stated as Application Under Test.

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail

Explain Peer Review in Software Testing

It is an alternative form of Testing, where some colleagues were invited to examine your work products for defects and improvement opportunities.

Some Peer review approaches are,

Inspection: It is a more systematic and rigorous type of peer review. Inspections are more effective at finding defects than are informal reviews.Ex : In Motorola’s Iridium project nearly 80% of the defects were detected through inspections where only 60% of the defects were detected through formal reviews.

Team Reviews:It is a planned and structured approach but less formal and less rigorous comparing to Inspections.

Walkthrough:It is an informal review because the work product’s author describes it to some colleagues and asks for suggestions. Walkthroughs are informal because they typically do not follow a defined procedure, do not specify exit criteria, require no management reporting, and generate no metrics.

Pair Programming :In Pair Programming, two developers work together on the same program at a single workstation and continuously reviewing their work.

Peer Deskcheck :In Peer Deskcheck only one person besides the author examines the work product. It is an informal review, where the reviewer can use defect checklists and some analysis methods to increase the effectiveness.

Passaround:It is a multiple, concurrent peer deskcheck where several people are invited to provide comments on the product.

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail

Testing mock test 1 Answers

Answers:
1)- b
2)- b
3)- c
4)- d
5)- b
6)- a
7)- d
8 )- c
9) - b
10) - d
11) -b
12) - a
13) - c
14) - b
15) - b
16) - b
17) - b
18) - b
19) - d
20) - a
21) - d
22) - b
23) - c
24) - a
25) - d

Take test here >>>
Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail

Test your Software Testing knowledge. Take this mock test

If you are preparing for CSTE testing certification exam or thinking to give the exam in coming days then this question series will help you for preparation. Here I have included some questions from CSTE objective type question papers.

The software testing/Quality assurance professionals for how are looking to attend interviews can also take this exam to test their testing knowledge.

You can either take printout and mark the answers or note your answers somewhere on the paper serially for all 25 questions. Verify your answers at the answer page provided at the bottom of this test page.

1. Verification is:
a. Checking that we are building the right system
b. Checking that we are building the system right
c. Performed by an independent test team
d. Making sure that it is what the user really wants

2. A regression test:
a. Will always be automated
b. Will help ensure unchanged areas of the software have not been affected
c. Will help ensure changed areas of the software have not been affected
d. Can only be run during user acceptance testing

3. If an expected result is not specified then:
a. We cannot run the test
b. It may be difficult to repeat the test
c. It may be difficult to determine if the test has passed or failed
d. We cannot automate the user inputs

4. Which of the following could be a reason for a failure
1) Testing fault
2) Software fault
3) Design fault
4) Environment Fault
5) Documentation Fault
a. 2 is a valid reason; 1,3,4 & 5 are not
b. 1,2,3,4 are valid reasons; 5 is not
c. 1,2,3 are valid reasons; 4 & 5 are not
d. All of them are valid reasons for failure

5. Test are prioritized so that:
a. You shorten the time required for testing
b. You do the best testing in the time available
c. You do more effective testing
d. You find more faults

6. Which of the following is not a static testing technique
a. Error guessing
b. Walkthrough
c. Data flow analysis
d. Inspections

7. Which of the following statements about component testing is not true?
a. Component testing should be performed by development
b. Component testing is also know as isolation or module testing
c. Component testing should have completion criteria planned
d. Component testing does not involve regression testing

8. During which test activity could faults be found most cost effectively?
a. Execution
b. Design
c. Planning
d. Check Exit criteria completion

9. Which, in general, is the least required skill of a good tester?
a. Being diplomatic
b. Able to write software
c. Having good attention to detail
d. Able to be relied on

10. The purpose of requirement phase is
a. To freeze requirements
b. To understand user needs
c. To define the scope of testing
d. All of the above

11. The process starting with the terminal modules is called
a. Top-down integration
b. Bottom-up integration
c. None of the above
d. Module integration

12. The inputs for developing a test plan are taken from
a. Project plan
b. Business plan
c. Support plan
d. None of the above

13. Function/Test matrix is a type of
a. Interim Test report
b. Final test report
c. Project status report
d. Management report

14. Defect Management process does not include
a. Defect prevention
b. Deliverable base-lining
c. Management reporting
d. None of the above

15. What is the difference between testing software developed by contractor outside your country, versus testing software developed by a contractor within your country?
a. Does not meet people needs
b. Cultural difference
c. Loss of control over reallocation of resources
d. Relinquishments of control

16. Software testing accounts to what percent of software development costs?
a. 10-20
b. 40-50
c. 70-80
d. 5-10

17. A reliable system will be one that:
a. Is unlikely to be completed on schedule
b. Is unlikely to cause a failure
c. Is likely to be fault-free
d. Is likely to be liked by the users

18. How much testing is enough
a. This question is impossible to answer
b. The answer depends on the risks for your industry, contract and special requirements
c. The answer depends on the maturity of your developers
d. The answer should be standardized for the software development industry

19. Which of the following is not a characteristic for Testability?
a. Operability
b. Observability
c. Simplicity
d. Robustness

20. Cyclomatic Complexity method comes under which testing method.
a. White box
b. Black box
c. Green box
d. Yellow box

21. Which of these can be successfully tested using Loop Testing methodology?
a. Simple Loops
b. Nested Loops
c. Concatenated Loops
d. All of the above

22. To test a function, the programmer has to write a ______, which calls the function and passes it test data.
a. Stub
b. Driver
c. Proxy
d. None of the above

23. Equivalence partitioning is:
a. A black box testing technique used only by developers
b. A black box testing technique than can only be used during system testingc. A black box testing technique appropriate to all levels of testingd. A white box testing technique appropriate for component testing
24. When a new testing tool is purchased, it should be used first by:
a. A small team to establish the best way to use the tool
b. Everyone who may eventually have some use for the tool
c. The independent testing team
d. The vendor contractor to write the initial scripts

25. Inspections can find all the following except
a. Variables not defined in the code
b. Spelling and grammar faults in the documents
c. Requirements that have been omitted from the design documents
d. How much of the code has been covered

Click here to Verify your answers.

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail

Interview Question in ORACLE Corporation this week

General Ques by Manager in 3rd Round:

1. You have done your work well enough but your boss came and asked you that what man who asked you to do in this way, this is not the correct way to do the work? How will you respond like argument,convincing your boss....etc...?
2. Project in critical situation and you need leave for your personal work, how will you convince you boss to take the leave?
3. Client asked you to complete the testing with in a week, what you do ? how will you approach?
4. Imagin a application with 2 radio buttons,2 check boxes,2 text boxes and some other options and write test cases on that?
5. What is Test Bed?

Testing Ques in 2nd Round:

What is Extreme Programming?
Extreme Programming is a software development approach for risk-prone projects with unstable requirements. Unit testing is a core aspect of Extreme Programming. Programmers write unit and functional test code first - before writing the application code. Generally, customers are expected to be an integral part of the project team and to help create / design scenarios for acceptance testing.

What if the project isn't big enough to justify extensive testing?
Do risk analysis. See the impact of project errors, not the size of the project.

What if there isn't enough time for thorough testing?

Consider the following 11 scenarios:

1. Which functionality is most important from business point of view?
2. Which functionality is most visible to the user?
3. Which functionality has the largest financial impact?
4. Which aspects of the application are most important to the customer?
5. Which parts of the code are most complex?
6. Which parts of the application were developed in rush?
7. Which aspects of similar/related previous projects caused problems?
8. What do the developers think are the highest-risk aspects of the application?
9. What kinds of problems would cause the worst publicity?
10. What kinds of problems would cause the most customer service complaints?
11. What kinds of tests could easily cover multiple functionalities?

When you can stop testing?

• Deadlines (release deadlines, testing deadlines, etc.)
• Test cases completed with certain percentage passed
• Test budget depleted
• Coverage of code/functionality/requirements reaches a specified point
• Bug rate falls below a certain level Beta or alpha testing period ends

When you can start testing?

After availability of all the following things we can start the testing:

• Test initiation
• Test Plan
• Test Design(Test Scenarios and Test Cases)
• Test Strategy
• Test Report plan and tools

What is verification?
It involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. It can be done with checklists, issues lists, walkthroughs, and inspection meetings etc.

What is validation?
It involves actual testing and takes place after verifications are completed.

What is a walkthrough?
Ans. An informal meeting for evaluation or informational purposes.

What's an inspection?
It is more formalized than a 'walkthrough', typically with 3-8 people including a moderator, reader, and a recorder to take notes. The subject of the inspection is typically a document such as a requirements spec or a test plan, and the purpose is to find problems and see what's missing, not to fix anything.

Don't miss any article:Get it by E-mail

Software Testing Dictionary Part II

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.

Defect:Nonconformance to requirements or functional / program specification

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

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

Dynamic Testing:Testing software through executing it. See also Static Testing.

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

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.

Equivalence Class:A portion of a component's input or output domains for which the component's behavior is assumed to be the same from the component's specification.

Equivalence Partitioning:A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.

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

Functional Decomposition:A technique used during planning, analysis and design; creates a functional hierarchy for the software.

Functional Specification:A document that describes in detail the characteristics of the product with regard to its intended features.

Functional Testing:

• Testing the features and operational behavior of a product to ensure they correspond to its specifications.
• Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions.

Gorilla Testing:Testing one particular module,functionality heavily.
Gray Box Testing:A combination of Black Box and White Box testing methodologies: testing a piece of software against its specification but using some knowledge of its internal workings.

High Order Tests:Black-box tests conducted once the software has been integrated.
Independent Test Group (ITG):A group of people whose primary responsibility is software testing.

Inspection:A group review quality improvement process for written material. It consists of two aspects; product (document itself) improvement and process improvement (of both document production and inspection).

Integration Testing:Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.

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.

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

Loop Testing:A white box testing technique that exercises program loops.

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.

Negative Testing:Testing aimed at showing software does not work. Also known as "test to fail".

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

Penetration testing: Evaluating the security of a computer system or network by hacking. it is the process of actively evaluating your information security measures. For more datails, please see my other post on Penetration Testing

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.

Positive Testing:Testing aimed at showing software works. Also known as "test to pass".

Quality Assurance:All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer.

Quality Audit:A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.

Quality Circle:A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality.

Quality Control:The operational techniques and the activities used to fulfill and verify requirements of quality.

Ramp Testing:Continuously raising an input signal until the system breaks down.

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.

Regression Testing:Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.

Release Candidate:A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released).

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

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

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.

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.

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.

Software Testing:A set of activities conducted with the intent of finding errors in software.
Static AnalysisAnalysis of a program carried out without executing the program.

Static Analyzer:A tool that carries out static analysis.

Static Testing:Analysis of a program carried out without executing the program.

Storage Testing:Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage.

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. Often this is performance testing using a very high level of simulated load.

Structural Testing:Testing based on an analysis of internal workings and structure of a piece of software.

System Testing:Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.

Testability:The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met.

Testing:

• The process of exercising software to verify that it satisfies specified requirements and to detect errors.
• The process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs), and to evaluate the features of the software item (Ref. IEEE Std 829).
• The process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component.

Test Bed:An execution environment configured for testing. May consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, etc. The Test Plan for a project should enumerated the test beds(s) to be used.
Test Case:

• Test Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc.
• A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.

Test Driven Development:Testing methodology associated with Agile Programming in which every chunk of code is covered by unit tests, which must all pass all the time, in an effort to eliminate unit-level and regression bugs during development. Practitioners of TDD write a lot of tests, i.e. an equal number of lines of test code to the size of the production code.

Test Driver:A program or test tool used to execute a tests. Also known as a Test Harness.

Test Environment:The hardware and software environment in which tests will be run, and any other software with which the software under test interacts when under test including stubs and test drivers.

Test First Design:Test-first design is one of the mandatory practices of Extreme Programming (XP).It requires that programmers do not write any production code until they have first written a unit test.

Test Harness:A program or test tool used to execute a tests.

Test Plan:A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning.

Test Procedure:A document providing detailed instructions for the execution of one or more test cases.

Test Script:Commonly used to refer to the instructions for a particular test that will be carried out by an automated test tool.

Test Specification:A document specifying the test approach for a software feature or combination or features and the inputs, predicted results and execution conditions for the associated tests.

Test Suite:A collection of tests used to validate the behavior of a product. The scope of a Test Suite varies from organization to organization. There may be several Test Suites for a particular product for example. In most cases however a Test Suite is a high level concept, grouping together hundreds or thousands of tests related by what they are intended to test.

Test Tools:Computer programs used in the testing of a system, a component of the system, or its documentation.

Thread Testing:A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.

Top Down Testing:An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested.

Total Quality Management:A company commitment to develop a process that achieves high quality product and customer satisfaction.

Traceability Matrix:A document showing the relationship between Test Requirements and Test Cases.

Usability Testing:Testing the ease with which users can learn and use a product.

Use Case:The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities.

Unit Testing:Testing of individual software components.

Validation:The process of evaluating software at the end of the software development process to ensure compliance with software requirements. The techniques for validation is testing, inspection and reviewing.

Verification:The process of determining whether of not the products of a given phase of the software development cycle meet the implementation steps and can be traced to the incoming objectives established during the previous phase. The techniques for verification are testing, inspection and reviewing.

Volume Testing:Testing which confirms that any values that may become large over time (such as accumulated counts, logs, and data files), can be accommodated by the program and will not cause the program to stop working or degrade its operation in any manner.

Walkthrough:A review of requirements, designs or code characterized by the author of the material under review guiding the progression of the review.

White Box Testing:Testing based on an analysis of internal workings and structure of a piece of software. Includes techniques such as Branch Testing and Path Testing. Also known as Structural Testing and Glass Box Testing.

Workflow Testing:Scripted end-to-end testing which duplicates specific workflows which are expected to be utilized by the end-user.

Don't miss any article:Get it by E-mail

Software Testing Dictionary Part I

Acceptance Testing:
Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.

Accessibility Testing:
Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

Ad Hoc Testing:A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality. Can include negative testing as well. See also Monkey Testing.

Agile Testing:Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm. See also Test Driven Development.

Automated Software Quality (ASQ):The use of software tools, such as automated testing tools, to improve software quality.

Basis Path Testing:A white box test case design technique that uses the algorithmic flow of the program to design tests.

Basis Set:The set of tests derived using basis path testing.

Beta Testing:Testing of a re-release of a software product conducted by customers.

Binary Portability Testing:Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

Black Box Testing:Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.

Bottom Up Testing:An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

Boundary Testing:Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

Bug:A fault in a program which causes the program to perform in an unintended or unanticipated manner.

Boundary Value Analysis:BVA is similar to Equivalence Partitioning but focuses on "corner cases" or values that are usually out of range as defined by the specification. his means that if a function expects all values in range of negative 100 to positive 1000, test inputs would include negative 101 and positive 1001.

Branch Testing:Testing in which all branches in the program source code are tested at least once.

Breadth Testing:A test suite that exercises the full functionality of a product but does not test features in detail.

CAST:Computer Aided Software Testing.

Capture/Replay Tool:A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools.

CMM:The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.

Cause Effect Graph:A graphical representation of inputs and the associated outputs effects which can be used to design test cases.

Code Complete:Phase of development where functionality is implemented in entirety; bug fixes are all that are left. All functions found in the Functional Specifications have been implemented.

Code Coverage:An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.

Code Inspection:A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards.

Code Walkthrough:A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions.

Compatibility Testing:Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.

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.

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.
Context Driven TestingThe 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.

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

Cyclomatic Complexity:A measure of the logical complexity of an algorithm, used in white-box testing.
Don't miss any article:Get it by E-mail