Testing Tools Interview Questions
1 What’s a ‘test case’?
Ans: A test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly. A test case should contain particulars such as test case identifier, test case name, objective, test conditions/setup, input data requirements, steps, and expected results. Note that the process of developing test cases can help find problems in the requirements or design of an application, since it requires completely thinking through the operation of the application. For this reason, it’s useful to prepare test cases early in the development cycle if possible.
2 What is the ‘software life cycle’?
Ans: The life cycle begins when an application is first conceived and ends when it is no longer in use. It includes aspects such as initial concept, requirements analysis, functional design, internal design, documentation planning, test planning, coding, document preparation, integration, testing, maintenance, updates, retesting, phase-out, and other aspects.
3 How is testing affected by object-oriented designs?
Ans: Well-engineered object-oriented design can make it easier to trace from code to internal design to functional design to requirements. While there will be little affect on black box testing (where an understanding of the internal design of the application is unnecessary), white-box testing can be oriented to the application’s objects. If the application was well-designed this can simplify test design.
4 What is verification? Validation?
Ans: Verification typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walk through, and inspection meetings. Validation typically involves actual testing and takes place after verifications are completed.
5 What are the? five common problems that occur during software development?
Ans: Poor Communication ? This is due to miscommunication for a developer as he don?t know what is needed by a customer. Or customers have unrealistic expectations. Poorly written requirements-This occurs when requirements are unclear, incomplete, not testable and too general. Schedules which are unrealistic-This occurs when too much of work is crammed in too little time. Inadequate testing ?if none knows whether or not software is good until customers complain or system crashes. Adding new features after development is underway ?This is a common practice to add new features after development is underway.
6 who is called a? good test engineer?
Ans: Good? test engineer is one s who ? Has a strong desire for quality, and? “test to break” attitude. who takes the point of view of the customer,? Has a strong desire for quality, Tactful and diplomatic ? Has good oral and written communication skill. Has previous worked in software development .
7 What is the role of documentation in QA?
Ans: In quality assurance? Documentation plays a critical role, ALL the designs,Specifications ,code changes, test plans, business rules, inspection reports, configurations, test cases, bug reports, user manuals should? be documented, all the? practices should be documented, so that they are repeatable. Use documentation change management if possible, ideally there should be a system for easily finding and obtaining of documents and determining what document will have a particular piece of information.
8 What is a software project test plan?
Ans: A software project test plan is a document that describes the objectives, scope, approach and focus of a software testing effort.? The completed document will help people outside the test group understand the why and how of product validation. It should be thorough enough to be useful, but not so thorough that none outside the test group will be able to read it. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product.
9 What is a test case?
Ans: A test case? is a document that contains particulars such as Test case Name, objective, test case identifier, test conditions/setup, Input data requirements/steps and expected results.A test case describes an input, action, or event and its expected result, in order to determine if a feature of an application is working correctly, since it requires you to completely think through the operations of the application the process of developing test cases can help find problems in the requirements or design of an application. For this reason, if possible it is useful to prepare test cases early in the development cycle.
10 What is configuration management?
Ans: Configuration management (CM) covers the tools and processes used to control, coordinate and track code, requirements, problems, designs, documentation,?? change requests,? tools, patches, compilers, libraries, who makes the changes and changes made to them. >
11 What is a software error?
Ans: One common definition of a software error is a mismatch between the program and its specification. Other definitions of software error areThere can never be an absolute definition for bugs, nor an absolute determination of their existence. The extent to which a program has bugs is measured by the extent to which it fails to be useful. This is a fundamentally human measure.??? ?A mismatch between the program and its specification is an error in the program if and only if the specification exists and is correct.?
?A software error is present for when the program does not do what its end user reason ability expects to do.?
12 How do you know when to stop testing?
Ans: Common factors in deciding when to stop testing are.
* Deadlines, e.g. release deadlines, testing deadlines.
* Test budget has been depleted.
* Bug rate falls below a certain level.
* Test cases completed with certain percentage passed.
* Coverage of code, functionality, or requirements reaches a specified point.
Beta or alpha testing period ends.
13 What is verification? Validation?
Ans: Verification typically involves reviews and meetings to evaluate documents, Code, plans, requirements, and specifications. This can be done with checklists, issues lists, walk throughs, and inspection meetings Validation typically involves actual testing and takes place after verifications are completed.
14 Explain some Software Testing Principles?
Ans: Complete testing is impossible. Software testing is not simple because
* Quality testing requires testers to understand a system/product completely.
* Quality testing needs adequate test set, and efficient testing methods.
* A very tight schedule and lack of test tools.
3. Testing is risk-based.
4. Testing must be planned.
5. Testing requires independence.
6. Quality software testing depends on:
Good understanding of software products and related domain application Cost-effective testing methodology, coverage, test methods, and tools. Good engineers with creativity, and solid software testing experience