Functional Tests for p4oauth
============================

The functional testing environment executes a "fatjar" build of p4oauth,
integrated with "external" test applications for the different authorization
scenarios.


## Configuration

This should be automated, but documented here in case something goes awry.

### TLS

OAuth 2.0 requires TLS, and we set up a self-signed key using keytool.
This gets dumped in build/keystore. The key password and store password are both
just "password".

We then launch a background process that hosts test data via plain ol'
HTML applications. It's intended that these applications could be used via
web browsers OR our testing framework. If you use a web browser, you WILL have
to accept the self signed cert by basically accessing a page on the oauth
application. The tests are different, they'll attempt to automatically accept
use our generated keystore.

### Perforce

The p4d instance should be initialized, and then we just sign in as one of the
users.

We basically have a depot with just a single file in it, then our test app
just runs the "p4 files" command. (It's something we ought to need a
login/password for, but doesn't require a client.)