SCPLibrary for Robot Framework
Introduction
SCPLibrary is a Robot Framework test library for performing Secure Copy (SCP) operations over SSH. Unlike the other SCPLibrary (‘robotframework-scplibrary’), this one works hand in hand with the Robot SSHLibrary (hence ‘robotframework-scpcompat’).
I wrote this because I was frustrated that the non-compatible SCPLibrary overwrote some SSHLibrary keywords and managed connections itself. I did consider changing the existing library, but that would break it for existing users.
To recap, the main differences are:
Relies on the standard SSHLibrary to manage connections
Download File and Upload File keywords use the currently active SSH connection to transfer files to the remote host
Does not conflict with any SSHLibrary keywords
Can even use an existing connection used for other SSH commands
It is operating system independent, but has only been tested with Python. Strictly speaking, the underlying ‘scp’ module is also pure Python, so let me know if you have any luck with Jython or IronPython.
SSHLibrary is open source software licensed under GNU General Public License v3.
Installation
When installing SCPLibrary on UNIX-like machines with Python, the easiest approach is using pip:
pip install robotframework-scpcompat
Note while this library supports both Python 2 and 3, SSHLibrary does not. So until SSHLibrary fixes issue #144 it doesn’t make sense to use Python 3. Hopefully though, once it’s resolved this library should also work with Python 3.
Documentation
The library is self-documenting via docstrings; additionally you can find an example robot script in this repository. You can run it against any host with SSH password authentication:
robot -v host:xxx -v user:xxx -v pass:xxx example.robot
The scp module documentation is also helpful, as this library is basically a wrapper around it.
For general information about using test libraries with Robot Framework, see Robot Framework User Guide.
Metadata
Release files for robotframework-scpcompat 0.1.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 | Actions |
|---|---|---|---|---|
| robotframework-scpcompat-0.1.0.tar.gz | 16.0 kB | Without provenance | Details for robotframework-scpcompat-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| robotframework_scpcompat-0.1.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for robotframework_scpcompat-0.1.0-py2.py3-none-any.whl |
Total release size: 35.0 kB
Release files / robotframework-scpcompat-0.1.0.tar.gz
| Download URL | robotframework-scpcompat-0.1.0.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e453df7559e5c60f93a2a2e6e59549e436418fa50dd01dcfb5ff084484ea49c
|
|
BLAKE2b-256 checksum How to use checksums |
b8ba12d8afeaf68f59d5fc7a08f27e0413b249513542ae4889ab8fc88833a280
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / robotframework_scpcompat-0.1.0-py2.py3-none-any.whl
| Download URL | robotframework_scpcompat-0.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 19.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
bc8cd97088e1e053edf6916be0cbc25a60cd4264c46867e9fb60d73aad4d5bd6
|
|
BLAKE2b-256 checksum How to use checksums |
d03071c6c13c2d26bbc86e907a5a379731b9b5cc97acc1265029bd5d0ae4168a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for robotframework-scpcompat 0.1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.