This project has been archived by its maintainers, and is no longer receiving any updates.
UI-level acceptance test framework. Full documentation available on ReadTheDocs.
⚠️ Deprecation Notice ⚠️
As of 2022-02-18, bok-choy is deprecated. All tests written using bok-choy have either been removed or are slated to be removed soon. Please do not write new tests using bok-choy! In the near future, this repository will be archived.
Overview
A Python framework for writing robust Selenium tests.
Installation
As Bok Choy is a Python framework, you first need to install Python. If you’re running Linux or Mac OS X, you probably already have it installed. We recommend that you use pip to install your Python packages:
pip install bok_choyRunning Tests
To run the test suite for bok-choy itself:
Install Firefox; as of this writing, the current version 59.0.1 works with the latest selenium Python package (3.11.0)
Install phantomjs
Create a virtualenv which uses Python 3.8
With that virtualenv activated, run pip install -r requirements/ci.txt to install the tox testing tool and its dependencies
Run tox -e py38. If you want to run the tests in parallel, add the desired number of worker processes like tox -e py38 -- -n 5 or tox -e py38 -- -n auto.
To test and build the documentation, run tox -e doc
To run an individual test, run py.test tests/<test file>::<test class>::<test name>
License
The code in this repository is licensed under the Apache License, Version 2.0, unless otherwise noted.
Please see LICENSE.txt for details.
How to Contribute
Contributions are very welcome. The easiest way is to fork this repo, and then make a pull request from your fork. The first time you make a pull request, you may be asked to sign a Contributor Agreement.
Reporting Security Issues
Please do not report security issues in public. Please email security@edx.org
Mailing List and IRC Channel
You can discuss this code on the edx-code Google Group or in the testing channel on the Open edX Slack.
1 maintainer
Metadata
1 maintainer
Release files for bok-choy 2.0.2
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 |
|---|---|---|---|---|
| bok_choy-2.0.2.tar.gz | 159.1 kB | Without provenance | Details for bok_choy-2.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bok_choy-2.0.2-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for bok_choy-2.0.2-py2.py3-none-any.whl |
Total release size: 310.0 kB
Release files / bok_choy-2.0.2.tar.gz
| Download URL | bok_choy-2.0.2.tar.gz |
|---|---|
| Size | 159.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f4bf112aac866c3103b4c76fe71ae3239f69d1e047974d6655cd29fcb18087cf
|
|
BLAKE2b-256 checksum How to use checksums |
1b22c36d654c1862cfdbc9f00b08cc3dbc80327501c4826559b30bd152f53337
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / bok_choy-2.0.2-py2.py3-none-any.whl
| Download URL | bok_choy-2.0.2-py2.py3-none-any.whl |
|---|---|
| Size | 150.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
168ea62809b4ed48d7a13e24788a1cba130730caa9d107fb04d24ebb3bbfcd4b
|
|
BLAKE2b-256 checksum How to use checksums |
66207e2a0acbf4cd72a16659b03b905b4b40c3dd142f71813ded65c2362297fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for bok-choy 2.0.2
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.
