I have googled many times but still not understand clearly about interface testing in software testing, who can explain this , many thanks?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
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:
Integration testing is generally what it says on the box: testing integrated components or systems to exercise the interactions between them and flush out any bugs. I've also seen integration testing used to describe testing interactions between the application in test and third party systems (where this could also be considered API testing of the AIT's use of the third party API).
As always, I tend not to focus on the official definitions because in my experience the official definitions are often modified in the field by the needs of the application in test and the testers working with it.
I take a look into the ISTQB glossary and found this two definitions:
After some research I also found this:
When thinking of interface testing, u need to stop thinking of interface as GUI, but think as a point of interaction btwn objects. So when we say interface testing we mean are the objects able to interact without any problem. Remember it start with unit test, then component testing then integration testing that leads to system. Interface testing thus is part of integration testing as you are integrating the components together, seeing whether the components can interface/communicate with each other until its integrated to a system.