added cromwell tests docs in readme

[sckott]

#33

[sckott]

@seankross the failing test is unrelated since the only change here is in the readme. can you approve now?

[sckott]

ping @seankross

[seankross]

@sckott lemme run through this myself locally and then I will approve

[sckott]

@seankross let me know if you run into any issues

[seankross]

@sckott I just tried to run this and got this error. I likely need to investigate further, maybe my api key isn't right.

ImportError while loading conftest '/Users/skross/Developer/wdl-unit-tests/tests/cromwell-api/conftest.py'.
tests/cromwell-api/conftest.py:8: in <module>
    cromwell_url = proof_api.cromwell_url()
tests/cromwell-api/proof.py:36: in cromwell_url
    self.start_if_not_up()
tests/cromwell-api/proof.py:32: in start_if_not_up
    if not self.is_cromwell_server_up():
tests/cromwell-api/proof.py:22: in is_cromwell_server_up
    return not self.status()["canJobStart"]
E   KeyError: 'canJobStart'

[seankross]

I tried this with PROOF_API_TOKEN_DEV set in plain text (without using 1pw) and it worked, se we'll need to figure out how to integrate 1pw into this. Let's put this on hold for now though.

[sckott]

@seankross can you try this:

# set the env var
export PROOF_API_TOKEN_DEV="op://Shared/PROOF Test User/dev token"
# check that it's working 
op run --no-masking -- printenv PROOF_API_TOKEN_DEV
# run pytest in the repo
op run -- uv run pytest tests/cromwell-api --verbose

I checked to make sure my env var of the same name was unset in my own dot files, and that the workflows started by the test suite were in fact in the test user account, which they were, so I think this is working "ON MY MACHINE" at least. lemme know howitdo

[seankross]

That did it! Ugh I didn't read the docs closely enough.

[seankross]

See #70

[sckott]

woops, been a while since this was opened, and need to change some things, will send a new PR