What is most likely NOT a characteristic of an integration test for a REST API implementation?
What is most likely NOT a characteristic of an integration test for a REST API implementation?
An integration test for a REST API implementation is typically conducted after the application has been deployed and all the source and target systems are correctly configured and accessible. It involves testing the interactions between different components and services. Therefore, the characteristic that is most likely NOT true for an integration test is that it runs immediately after the application has been compiled and packaged. This would be more typical of unit tests or automated build tests, not integration tests.
Answer: B
It cannot be B because integration tests are the last line of testing. They need all various systems configured and connected for test. Unittests or any test part of compile / package step will not have that configured usually.
Sorry that means B is the answer.. question is asking for which is NOT
The test runs immediately after the Mule application has been compiled and packaged