Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Torsten Kilias <[email protected]>
  • Loading branch information
ckunki and tkilias authored May 22, 2024
1 parent 164ba41 commit 997f4d5
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion justfile
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ default:

# Run tests for one or multiple projects within this respository
test +projects=PROJECTS:
#!/usr/bin/env python
#!/usr/bin/env python3
import subprocess, sys
rc = 0
def run(command):
Expand Down
4 changes: 2 additions & 2 deletions pytest-saas/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,13 +22,13 @@ pip install pytest-exasol-saas

By default the fixtures in pytest-exasol-saas Plugin will create instances of Exasol SaaS database with scope `session`.

If you want to use an existing instance instead, then you can provide the instance's ID with command line option `--saas-database-id <ID>` to pytest.
If you want to use an existing instance instead, then you can provide the instance's ID with the command line option `--saas-database-id <ID>` to pytest.

### Keeping Database Instances After the Test Session

By default the fixtures in pytest-exasol-saas Plugin will remove the created database instances after the session or in case of errors.

However, if you provide command line option `--keep-saas-database` then pytest-exasol-saas Plugin will _keep_ these instances for subsequent inspection or reuse.
However, if you provide the command line option `--keep-saas-database` then the pytest-exasol-saas plugin will _keep_ these instances for subsequent inspection or reuse.

Please note hat long-running instances will cause significant costs.

Expand Down

0 comments on commit 997f4d5

Please sign in to comment.