Robocorp Inspector
Robocorp Inspector is a tool for exploring various user interfaces and developing ways to target elements within them. An expression that can target specific UI elemements is called a locator, and these locators can be used to automate applications typically used by humans.
Dependencies
You might need to create a .npmrc file at project level with contents similar to the following, but with your own authToken.
This is needed for private repositories.
registry=https://registry.npmjs.org/
@robocorp:registry=https://npm.pkg.github.com/
//npm.pkg.github.com/:_authToken=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
There is a hard dependency to the Inspector Commons implementation. Most of the implementation resides in
inspector-commonsand if you spot any misalignment then you should correct it
Development
The project uses invoke for overall project management, poetry for
python dependencies and environments, and yarn for Javascript dependencies
and building.
Both invoke and poetry should be installed via pip: pip install poetry invoke
- To see all possible tasks:
invoke --list - To run the project:
invoke run - For a quick build and run you can try running:
inv build-js && inv build && inv run - To clean the dev environment you can use
inv cleanorinv clean --force
All source code is hosted on GitHub.
Python & NPM
To launch the development environment you'll need:
pyenv + virtualenv -> these will help building a dedicated python virtual environment
nvm -> will help with a contained version of node + npm
In order for everything to install and build properly use the following versions:
python -> v3.8.10
node -> v16.14.2
npm -> 8.5.0
Usage
Robocorp Inspector is distributed as a Python package with all front-end components compiled and included statically.
If the package (and all required dependencies) is installed manually,
it can be run with the command: inspector.
Code Organization
Attention: these might change over time & hopefully they will be maintained.
Inspector Class Diagram
- not extremely precise
- created to show how things link together from local implementation to
inspector-commons
Metadata
Release files for robocorp-inspector 0.10.3
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 |
|---|---|---|---|---|
| robocorp_inspector-0.10.3.tar.gz | 1.7 MB | Without provenance | Details for robocorp_inspector-0.10.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| robocorp_inspector-0.10.3-py3-none-any.whl | Python 3 | none | any | Details for robocorp_inspector-0.10.3-py3-none-any.whl |
Total release size: 3.4 MB
Release files / robocorp_inspector-0.10.3.tar.gz
| Download URL | robocorp_inspector-0.10.3.tar.gz |
|---|---|
| Size | 1.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3559e3b59ab9ca150298a5adc58cee2c61fd6b61a527296916966094e2223289
|
|
BLAKE2b-256 checksum How to use checksums |
76e5e47b270eccef9ce8b0d58632397f2c2dd214f14d4f75603a61fca94c45d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.5 CPython/3.8.18 Linux/6.11.0-1018-azure
|
Release files / robocorp_inspector-0.10.3-py3-none-any.whl
| Download URL | robocorp_inspector-0.10.3-py3-none-any.whl |
|---|---|
| Size | 1.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
df1f69b4bbc16ba3c5f3c06b21522727e8a15811bf27e4e623aaa44941cc0e61
|
|
BLAKE2b-256 checksum How to use checksums |
9ef9a14c9ae39fbc593267747aa7a738be40eef6bbcd1e3f6abc815bbe963974
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.5 CPython/3.8.18 Linux/6.11.0-1018-azure
|
Security for robocorp-inspector 0.10.3
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.