we should have an assertion that all the pods in a test case become Ready and stay Ready for X milliseconds

[jstrachan]

once all the other assertions on startup have been done we should wait for Y millis for the pods to become ready. Then if they are - we should wait at least X milliseconds to check they stay Ready (and don't keep restarting etc).

So if an arquillian test doesn't do much at all; it should ensure that all the related pods are ready for Y millis and don't just barf on startup etc.

If a test takes a while to run, so that elapsed time > X then we should assert that things stay ready for that entire time

[jstrachan]

BTW here's what the default system test should look like:

             assertThat(client).deployments().pods().isPodReadyForPeriod();

which asserts that at least 1 pod starts up and becomes ready for the Deployment/DeploymentConfig/ReplicaSet/ReplicationController of the current app (by finding them on the classpath), then asserting the pod stays in a Ready state (without restarting) for a period of time. You can provide both timeouts if you wish as the function arguments