Skip to content

Commit 67bb17a

Browse files
Suggested updates
Co-authored-by: Kory Draughn <korydraughn@ymail.com>
1 parent f31f771 commit 67bb17a

File tree

4 files changed

+7
-7
lines changed

4 files changed

+7
-7
lines changed

irods/test/scripts/test_support_functions

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ set_up_ssl() {
2121
}
2222

2323
# Clears out environment and resets to rodsadmin 'rods'.
24-
# Meant mostly to allow initial steps by a rodsadminfor setting up tests.
24+
# Meant mostly to allow initial steps by a rodsadmin for setting up tests.
2525

2626
iinit_as_rods() {
2727
rm -fr ~/.irods

test_harness/multiple_node/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,14 +23,14 @@ Currently the database server is fixed as Postgres.
2323

2424
The file `.github/workflows/run-the-tests.yml` describes a Github action which
2525
will be started to run the client test suite in response to creating a pull
26-
request, or pushing new commits to the Github branch, containing it.
26+
request, or pushing new commits to the GitHub branch, containing it.
2727

2828
The command-line recipe outlined in the file also supports running the
2929
test suite on any workstation with docker compose installed.
3030

3131
A summary of how to run the tests "at the bench" follows:
3232

33-
1. Change the working directory to the repository top directory, e.g.:
33+
1. Change the working directory to the root directory of the repository, e.g.:
3434
```
3535
cd /path/to/python-irodsclient
3636
```
@@ -39,7 +39,7 @@ A summary of how to run the tests "at the bench" follows:
3939
```
4040
./docker-testing/start_containers.sh 4.3.4 3.11
4141
```
42-
This builds and runs the docker images for the project, with "4.3.4" being the iRODS
42+
This builds and runs the docker images for the project, with "4.3.4" being the iRODS
4343
version installed on the provider and "3.11" is the version of python run on the client side.
4444
4545
3. Run:

test_harness/single_node/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
## Description
44

5-
A series of docker images which support running isolated test scripts (using BATS, bash, or Python).
5+
A series of Docker images which support running isolated test scripts (using BATS, bash, or Python).
66
Once built, the images allow loading and customizing the Docker container environment for a given
77
test script.
88

@@ -50,7 +50,7 @@ Sample command lines to build Docker images:
5050
Builds (ignoring docker cache) images based on specific iRODS package version and desired
5151
Python Interpreter version, optionally with a restricted list of Docker files in need of rebulding.
5252

53-
### To run a test script.
53+
### To run a test script
5454

5555
```
5656
$REPO_ROOT/irods/test/harness/docker_container_driver.sh $REPO_ROOT/irods/test/scripts/run_local_suite

test_harness/single_node/setup_python_rule_engine

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ if [ -n "$wait" ]; then
8282
times=0
8383
OUTFILE=/tmp/irule_output.stderr
8484
while :; do
85-
irule -a 2>/dev/null| grep irods_rule_engine_plugin-python-instance >/dev/null
85+
irule -a 2>/dev/null | grep irods_rule_engine_plugin-python-instance >/dev/null
8686
[ ${PIPESTATUS[1]} -eq 0 ] && break
8787
sleep 1
8888
if [ $((++times)) -ge 10 ]; then

0 commit comments

Comments
 (0)