writing test case live from Jenkins Office Hours
2nd test case live
Two arg version of the waitForCond should support a magic constant to indicate the default timeout.

This way, calling code that provides its own tweakable timeout wouldn't have to hard-code the value again
[maven-release-plugin] prepare release acceptance-test-harness-1.6
[maven-release-plugin] prepare for next development iteration
Update JUNIT.md

Added description for @WithCredentials annotation
Fixe a race condition.

See my comment to the CapybaraPortingLayer.all() method why this change was needed.
last() should wait like find()
narrow the search to the pop-up so that we don't find something else that happens to match
Unified the way a drop-down menu button is clicked
Unified the way a drop-down menu button is clicked (take 2)
doc improvement
If the dependency is already installed, don't try to overwrite them.
Fixing fragile test albeit in a poor way.

When scheduling a job, the state transition of queued items happens asynchronously from the UI thread.
So if we hit the UI immediately afterward, you might not see the item in the pending state. Queue.maintain()
might not have run that to determine that it's in the pending state (as opposed to in the waiting state.)

So adding some delay artificially to work around this problem.

Ideally we should use something like waitForCond() to repeatedly test this until we find one, so that
we don't have to always wait for 3 secs, and instead wait at most 3 secs.
got rid of this 2nd argument after some more thought.
Fixing test bug.

The relative path resolution logic now removes redundant '/', so we cannot produce this weird path expression
Minor comment updates for GerritTriggerTest.
Merge branch 'patch-1' of https://github.com/itgkarl/acceptance-test-harness