New answers tagged

1

In the context of an embedded system, interface testing is most likely to refer to testing the interface between the embedded system and whichever external system is using it. For instance, if the embedded system is the software driving something like a pin pad/payment terminal with touch screen, card reader, and so on, interface testing could include: ...


2

The term "Integration checking" are usually misused. Rainsberger has a seminal post called Integrated Tests are a Scam. By "Integrated" he means what is usually called "integration; he uses integration as @Reijmersdal did: If things can connect together. Contract checking is, here, a type of integration checking. It's about checking if the syntax the ...


3

Martin Fowler has a good article just about that Quoting him: Integration tests collect modules together and test them as a subsystem in order to verify that they collaborate as intended to achieve some larger piece of behaviour. While: Whenever some consumer couples to the interface of a component to make use of its behaviour, a contract is formed ...


1

For me integration testing means testing how multiple microservices integrate to eachother and facilitate a user-workflow. With the goal of finding configuration and wiring issues. For me contract testing means testing a single microservice API. Testing inputs and outputs of a single service to see if it meets its documented contract. This could be using a ...


Top 50 recent answers are included