pip install noseapp_workspace
Usage
Extension for control by file system from your test application.
Example:
ws = WorkSpace(
'/path/to/entry/point/',
permissions=(
Permissions.CREATE_FILE,
Permissions.CREATE_DIRECTORY,
),
)
bin = ws.go_to('bin')
daemon_bin = bin.path_to_bin('daemon')
logs = ws.go_to('logs')
logs.is_file('daemon.log')
logs.create_file('new.log') or logs.create_log_file('new')
tmp = ws.create_dir('tmp')
ws.is_dir('tmp')
tmp.create_file('new_tmp.tmp', content='Hello World!')
child_ws = ws.child_workspace('new_workspace')
...
See full api of noseapp_workspace.WorkSpace
Must be installed like extension:
WORKSPACE_EX = create_workspace_config(
'/path/to/entry/point/',
permissions=(
Permissions.CREATE_FILE,
Permissions.CREATE_DIRECTORY,
),
)
WorkSpace.install(app)
suite = Suite(__name__, require=['workspace'])
1 maintainer
Metadata
1 maintainer
Release files for noseapp_workspace 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| noseapp_workspace-0.4.0.tar.gz | 5.3 kB | Without provenance | Details |
Release files / noseapp_workspace-0.4.0.tar.gz
| Download URL | noseapp_workspace-0.4.0.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9332409755a02043de9bef12bee5a90bee263ff549abaf83857093dd79accbc8
|
|
BLAKE2b-256 checksum How to use checksums |
cf444e9d82e642bd1cbc4bc64a728a71af8a13aeae9b22d9b10eb5566734bde3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for noseapp_workspace 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
