This release is a pre-release and may not be stable for production use.
testsuite
A useful script to running FATE’s testsuites.
quick start
(optional) create virtual env
python -m venv venv source venv/bin/activateinstall fate_testsuite
pip install fate_testsuite fate_testsuite --helpnew and edit the testsuite_config.yaml
# create a testsuite_config.yaml in current dir testsuite config new # edit priority config file with system default editor # filling some field according to comments fate_testsuite config editrun some testsuites
fate_testsuite suite -i <path contains *testsuite.json>useful logs or exception will be saved to logs dir with namespace showed in last step
testsuite_config.yaml examples
no need ssh tunnel:
9999, service: service_a
10000, service: service_b
and both service_a, service_b can be requested directly:
work_mode: 1 # 0 for standalone, 1 for cluster data_base_dir: <path_to_data> parties: guest: [10000] host: [9999, 10000] arbiter: [9999] services: - flow_services: - {address: service_a, parties: [9999]} {address: service_b, parties: [10000]}need ssh tunnel:
9999, service: service_a
10000, service: service_b
service_a, can be requested directly while service_b don’t, but you can request service_b in other node, say B:
work_mode: 0 # 0 for standalone, 1 for cluster data_base_dir: <path_to_data> parties: guest: [10000] host: [9999, 10000] arbiter: [9999] services: - flow_services: - {address: service_a, parties: [9999]} - flow_services: - {address: service_b, parties: [10000]} ssh_tunnel: # optional enable: true ssh_address: <ssh_ip_to_B>:<ssh_port_to_B> ssh_username: <ssh_username_to B> ssh_password: # optional ssh_priv_key: "~/.ssh/id_rsa"
command options
exclude:
testsuite suite -i <path1 contains *testsuite.json> -e <path2 to exclude> -e <path3 to exclude> ...will run testsuites in path1 but not in path2 and path3
replace:
testsuite suite -i <path1 contains *testsuite.json> -r '{"maxIter": 5}'will find all key-value pair with key “maxIter” in data conf or conf or dsl and replace the value with 5
glob:
testsuite suite -i <path1 contains *testsuite.json> -g "hetero*"will run testsuites in sub directory start with hetero of path1
Metadata
Release files for sage-testsuite 0.1.0a6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| sage_testsuite-0.1.0a6.tar.gz | 12.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sage_testsuite-0.1.0a6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.2 kB
Release files / sage_testsuite-0.1.0a6.tar.gz
| Download URL | sage_testsuite-0.1.0a6.tar.gz |
|---|---|
| Size | 12.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d5cdc25c73fa5f5d84e8326dbdbb96f91fc97d4c3755c349c8bd95c71e5e37bf
|
|
BLAKE2b-256 checksum How to use checksums |
db69c37dd438269ef17609504b7d0c995ba7621ca1089c2918c4d6a1553f4b0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.10 CPython/2.7.16 Darwin/19.5.0
|
Release files / sage_testsuite-0.1.0a6-py3-none-any.whl
| Download URL | sage_testsuite-0.1.0a6-py3-none-any.whl |
|---|---|
| Size | 16.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
12757904afd70d6d38440a16a2408858742f690029d98b3a6295ff17c66209fe
|
|
BLAKE2b-256 checksum How to use checksums |
7da07395b3e17c0996114881535a4108af5134906278df8be891a527b279f8b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.10 CPython/2.7.16 Darwin/19.5.0
|