Tag Info

Hot answers tagged

8

The traditional definitions would be something like this: A test suite is a collection of test cases related to the same test work. You might have a suite for regression, one for build verification tests, a suite that is specific for a component, and so on. A test plan is generally a document which describes testing approach and methodologies being used for ...


5

There are lots of kinds of testing, and they vary by company and organization. Different people use different terms. There is no special value in any particular set of terms; you just need to know what the speaker means when they use them. Frankly, I think it was a stupid question, or perhaps even a trick question to see how you deal with ambiguity. ...


5

You have some choices here. You can go with formal definitions like the ISTQB definition, or you can treat the definitions the way your organization handles them. Software testing is a field where definitions tend to vary depending on the understanding of the team and how they work. That said, in my experience interface testing can be one of two things: ...


2

If we refer to ISTQB glossary of terms then test suite: A set of several test cases for a component or system under test, where the post condition of one test is often used as the precondition for the next one. test plan: A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, ...


2

I take a look into the ISTQB glossary and found this two definitions: interface testing: An integration test type that is concerned with testing the interfaces between components or systems. integration testing: Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems. See also ...


2

Smoke testing is the term teams I've been on used to describe the initial quick pass on brand new code (or at least a new build) to make sure nothing major is broken in a major way (that will block you from the majority of testing). This is the first step before you get into regression and rigorous new feature testing. You may consider Sanity Testing. ...


2

Component testing is testing of specific module or program.It may be done in isolation from rest of the system depending on the life cycle model selected for that particular application. Stub and driver are used for competent testing. These both are consider as component. Best example is given below : Suppose you are testing one application which have 3 ...


2

This is where good communication skills, alertness and good vocab comes in handy for a tester.... Looking at the meanings of the terms in question, Feature: a distinctive attribute or aspect of something. Functionality: t he quality of being suited to serve a purpose well; practicality. So with the knowledge of the meanings of these terms you can come up ...


2

Companies like it when new potential employees have similar experience because in theory it gives them some familiarity with the industry, terminology, rules and regulations, common technologies and maybe even with theirs or similar products (as a basis for comparison). In theory it also makes it easier (or more familiar) for recruiters and managers to ...


1

As with most terminology this depends on the person and or the industry. Be sure to define terminology per workplace so that everyone has the same definition, in doubt always ask. :) I have worked in market research, where route testing would mean testing all possible paths through a questionnaire. Different questions would mean skipping and or adding extra ...


1

I don't agree with the idea that "if there is a refined specification of installation it's functional otherwise not". Thinking in that way is like "do not describe in detail your non-functional requirements or they become functional". I think that non-functional requirements need to be well specified. And they continue to be non-functional. Apologies for ...


1

Feature Testing: Features are changes that add new functionality or modify existing functionality. Functional Testing: Functional Testing is a testing technique that is used to test the functionality of the Software, should cover all the scenarios. Edited as per the comments.


1

I personally agree with Kate that definition is good enough if it is agreed with all participants of the development process and everybody understand it the same way. If you need definition of term I'd suggest next: failover testing: Testing by simulating failure modes or actually causing failures in a controlled environment. Following a failure, the ...


1

Pesticide paradox can be also explained as: If the same tests are repeated over and over again, eventually the same set of test cases will no longer find any new bugs. To overcome this 'pesticide paradox', the test cases need to be regularly reviewed and revised, and new and different tests need to be written to exercise different parts of the software or ...


1

I think that it is important to understand the difference between testing and QA. There is one post you need to read on the topic by Michael Bolton, Testers get out of the QA business. The short version is that testers, who don't change code, are assisting with quality, not assuring it.


1

As Chris has said, domain experience means that - in theory - a candidate won't need the lengthy domain learning time that's needed. For instance, I'm currently working in payroll and HR management. To be able to effectively test my employer's software, I needed to learn how payroll and HR management works, and the US regulations that the company needs to ...


1

Latent bugs are bugs which exist, but have not yet been discovered. They are bugs waiting to be found. also see: http://www.allthingsquality.com/p/testing-terms-glossary.html



Only top voted, non community-wiki answers of a minimum length are eligible