+1
While Russell had a more sophisticated explanation, you can't beat the
one second rule for clarity:-)
Ron
On 13/11/2013 10:59 AM, Stephen Connolly wrote:
On 13 November 2013 15:20, James Green <[email protected]> wrote:
I love the FAQ entry that states that it is intended for running
integration tests.
The next entry should read: What do you call an integration test?
Any test that takes more than 1 second to run is *not* a unit test.
Most tests that take more than 50ms to run are *not* unit tests... but
there can be some exceptions
If a unit test needs to call out to other systems, it will typically use a
mock.
If your test is actually calling out to other systems (which could be code
from a dependency, etc - i.e. not just a TCP socket, could be a call within
JVM) then it is testing the integration of those two parts... therefore it
is not a unit test.
There is no hard and fast rule as to where the transition occurs... but we
know that tests who's execution time is greater than 1 second are not unit
tests... and hence are integration tests...
HTH
I've asked around and no-one comes up with a consistent answer. I guess it
depends on what is executing the integration test. In this case maven is
invoking someone after the packaging phase so should I expect to run tests
against the packaged binary artefact? Is that the purpose here?
Thanks,
James
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
