Closed JustinKyleJames closed 6 months ago
In addition to handling issues from above, I changed the checksum markers code to handle it if we got more than one marker. This test now also handles the situation where we hang looking for a marker if the checksum comes back too fast. In the latter case, we would still generate an error because we didn't see a marker but it wouldn't hang.
very cool. what's the status? it all runs and passes and gives us confidence?
Yes it runs and passes. I believe it covers most of what I test.
Some things missing:
Consider making an issue for each known missing test (category).
Consider making an issue for each known missing test (category).
I created the issues.
depends on https://github.com/irods/irods_client_globus_connector/pull/87 - merge that one first
Note that this PR right now is dependent on #87 but only because there are a couple of test cases for the fix for #87. However, I could reorganize the two to remove those two test cases and move them into the PR for #87. Otherwise I will just rebase this after that one is merged.
rebase seems fine - just keep the linking good and should be fine.
Is this ready?
87 has been merged. Please rebase once more.
Done
Missing issue number for commit Adding Ubuntu20 tests
?
might just get squashed...
Missing issue number for commit
Adding Ubuntu20 tests
?
Yes, that along with many others were intended to be squashed.
Let's # it.
Done
This is a first pass at automated testing for the Globus plugin.
Some notes:
Right now this only works against an Ubuntu20 installation of Globus. The test cases should run fine against others as long as the servers are set up properly. I have docker scripts that will set up other OS's so for now I will run the tests manually within those containers.
At the moment I have to use a lot of telnet and ftp in the tests. Some of it is intended and some is a byproduct of its use elsewhere. This is due to the following:
I can solve these limitations in the future.