Recently I happened to be in an interview where I was asked to explain feature testing and functional testing. Even after looking up so many references I am unable to find a convincing explanation ‒ can anyone explain?
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. Whether a candidate happens to know how the interviewer happens to define a set of ambiguous terms has no bearing on job performance. I hope the rest of the interview was better than that.
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: the quality of being suited to serve a purpose well; practicality.
So with the knowledge of the meanings of these terms you can come up with a good enough explanation spontaneously. As it is there are many terminologies made by people in testing. And to different people and organizations a term may have a different meaning. So it is always better to give an appropriate explanation depending on the context.... :)
Unlike for other Testing types, for the term Feature testing, you can find only a best match from well accepted testing types in Software QA domain.
- Feature testing - I think it is the sanity test. In a mature build, particular feature could be newly added, or existing feature's bug could be fixed. Then the testing has to be carried out focusing the particular feature alone. The sanity test of a mature build is also the same thing. However feature test (sanity test) alone would not qualify application for sending live. The regression test has to follow right after to make sure nothing in the whole system is broken by new addition of feature or bug fix. The link here should give you more understanding on Sanity test
Functional Testing has 2 interesting meanings depending on the context of testing
As a sub type of System Testing Types
Functional Testing - Testing to look for missing functionalities which could be useful to the end users
This is not what the simple name suggest what it could be. It is one variation out of 7 main types of system testing. System testing is also called End to end testing. One major aspect of system testing is Functional testing where testers look for missing functionalities which could be useful to the end users. Idea is to improve the quality of application by new functionality suggestions after the test.
Please refer this link for more info on system testing
Main testing type that cover many other sub testing types
Functional Testing - Test how system functions conform to the functional requirements provided by the customer.
Composed of many testing sub types involving even developers in the team to contribute. Check this link for more information on this main test type.
Feature Testing Testing enhanced things in already developed project is called feature testing.Whether its is useful for our project.Understanding the Feature,Build Test Scenarios,How it is Implemented,Deploy the Build Early are some of the things in feature testing.
Functional Tesing Functional testing means testing the application against business requirements. Functional testing is executed using the functional specifications given by the client or by the design specifications according to use cases given by the design team. Role of functional testing is to validating the behavior of an application.
Feature is something that the user perceives as a benefit. Something that can be called out in a brochure bullet point.
Function is something that gets done.
In general, features use one or more functions. For instance, "undo" is a feature. It is a cross-cutting concern, and is actually composed of many tens or hundreds of individual "undo" functions.
A function does something; features are characteristics or qualities of the function, or perhaps how it does what it does.
When assessing software, should buyers look at functions, features, or both? I would think that the focus would be on functions (what you’re looking for the system to do for you), as these are fairly easy to identify. Features may vary from vendor to vendor, though functions may be almost universally available. And so, you might consider the features of one vendor versus another, as a way to decide which you prefer.
Function is like the basic thing of the product or of particular domain for example, on a job searching site job seeker can view job which is basic functionality of all job searching site, but in particular job searching site one can send mail to the recruiter as well is feature of the particular job searching site which belongs to a particular company.
It means functionality is the basic function of the product in a domain, but features can change depending on company to company product in the same domain.