1142 Commits (17b37034e894dd7268e252dc76219892aa4627b8)

 

All Branches   

Search

Author	SHA1	Message	Date
matejcik	17b37034e8	device_tests: fix test_msg_recoverydevice for T1	6 years ago
matejcik	f8f0be9c86	device_tests: fix T1 test differences in wording	6 years ago
matejcik	7e83eb11e5	trezorctl: drop remaining stellar_sign_message command	6 years ago
matejcik	f2aee59e27	device_tests: do not xfail Lisk tests, they are now merged	6 years ago
matejcik	4b7926268e	drop Lisk and Stellar sign/verify message functionality	6 years ago
matejcik	70172520fb	protobuf: update messages from upstream. ... This drops sign/verify messages for Lisk and Stellar so we have to remove the corresponding methods.	6 years ago
Jan Pochyla	bc27089546	tests: remove lisk sign/verify	6 years ago
matejcik	ce7ee8ae30	device_tests: mark decred	6 years ago
matejcik	2225343c52	device_tests: in test_multisig, T1 raises a different message ... expected: "Pubkey not found in multisig script" actual: "signing.c:780:Pubkey not found in multisig script"	6 years ago
matejcik	013e0f6d66	device_tests: get nicer tracebacks by using pytest.raises instead of custom exception code	6 years ago
matejcik	224e3c18f5	device_tests: fix test_protection_levels for T1 ... a couple expected ButtonRequests were missing	6 years ago
matejcik	a4fe17b461	device_tests: xfail for decred. This should be investigated more though.	6 years ago
matejcik	465c01d4f7	device_tests: add more currency markers ... missed Stellar tests, plus Ethereum, for good measure	6 years ago
matejcik	af98a4071a	device_tests: allow custom runxfail ... We can now selectively runxfail certain tests. This is useful for accepting PRs into trezor-core: 1. trezor-core is going to get a pytest.ini that sets xfail_strict. That means that if an `xfail`ed test actually passes, that will break the test suite. So it will be visible when we implement a feature for which tests exist. 2. To allow PRs to pass the test suite without touching python-trezor directly, we add a new pytest.ini option: run_xfail. This adds a list of markers which will ignore `xfail`. So: 2.1 First, the python-trezor PR marks the tests with the name of the feature. This commit already does that: Lisk tests are marked `@pytest.mark.lisk`, NEMs are `@pytest.mark.nem`, etc. The tests will be also marked with `xfail`, because the feature is not in core yet. 2.2 Then, the trezor-core PR implements the feature, which makes the `xfail`ed tests pass. That breaks the test suite. 2.3 To fix the test suite, the core PR also adds a `run_xfail` to `pytest.ini`: `run_xfail = lisk`. (it can take a list: `run_xfail = lisk nem stellar`) That will make the test suite behave as if the tests are not `xfail`ed. If the feature is implemented correctly, the tests will pass. 2.4 When the PR is accepted to core, the next step should be a PR to python-trezor that removes the `xfail`s. After that, we should also remove the `run_xfail` option, just to be tidy.	6 years ago
matejcik	9f4cc74b9a	travis: set virtualenv version to restore build on py33	6 years ago
matejcik	1df0cd7094	travis: use newer pip that understands python_requires ... (should fix build on Python 3.3 because of too-new tox)	6 years ago
Tomas Susanka	e656bbf072	stellar: xdr parse move to trezorctl; client works with messages	6 years ago
Tomas Susanka	277296be90	tests/stellar: verify marked as not passing on T2	6 years ago
Tomas Susanka	3ee3083e8c	tests/device/stellar: verify message	6 years ago
Tomas Susanka	bb74950e23	stellar: message is normalized before sign/verify	6 years ago
Tomas Susanka	22560128fe	stellar: StellarSignMessage.message is bytes	6 years ago
Tomas Susanka	f97815f69a	vendor: trezor-common updated	6 years ago
Tomas Susanka	d57fe33582	tests/device/stellar: sign message	6 years ago
Tomas Susanka	77766d2d0f	tests/device/eth: known/unknown token test	6 years ago
matejcik	a289d16838	build: require typing module for python < 3.4	6 years ago
matejcik	e0d850df7d	protobuf: update generators and messages to be identical with trezor-core	6 years ago
Tomas Susanka	18adf6cc4d	tests/stellar: marked as passing on T1	6 years ago
matejcik	5329bc9463	Merge pull request #167 from zulucrypto/stellar ... [Stellar] [WIP] Add Stellar support to trezorctl	6 years ago
matejcik	dd0217c746	protobuf: update trezor-common and messages	6 years ago
matejcik	28264a4fe0	protobuf: improve description of sint_to_uint	6 years ago
matejcik	df8c3da1a2	protobuf: properly implement signed types (fixes #249)	6 years ago
matejcik	b156ec9757	travis: fix bash syntax bug in trigger-travis.sh	6 years ago
matejcik	76fea5afc4	build: move ethereum requirements to their own extra ... We only need ethereum libraries for `ethereum_sign_tx` in trezorctl, and rlp has caused us dependency problems in the past already. Also we required ethjsonrpc for the same thing but never listed that dependency anywhere. That changes now.	6 years ago
matejcik	6c033bd810	travis: trigger build of trezor-core when python-trezor is pushed	6 years ago
matejcik	43f14ac760	build: add flake8 to dev requirements	6 years ago
matejcik	4c06a613b5	ethereum: do 'int_to_big_endian' conversion manually ... instead of relying on 'rlp.utils' from which it was removed by 1.0, and moved to 'eth_utils' which don't support py3.4	6 years ago
matejcik	41d99764c6	build: reorganize requirements, mark hidapi as optional ... This drops the command line options. `libusb` is now required unconditionally (it's cffi so no harm there). hidapi is an extra. You either need to install it manually, or specify it in your requirements.txt like so: trezor[hidapi] >= 0.9.2	6 years ago
matejcik	ce7a434f2d	build: add the prebuild command as a dependency for develop ... So, 'python setup.py develop' exists. And of course it doesn't have build_py as a dependency, because of course it doesn't. We could use 'data_files' instead of 'package_data and copying', and then use pkg_resources to find the actual file location, and that could work in theory. But pkg_resources API is weird and messy and this whole area of Python packaging theory barely works as it is. Instead we will force the prebuild command to be a dependency of develop as well as build_py, and we do this by monkey-patching instead of the proper way, because at this point it seems cleaner. I wonder if there are more commands that would need this.	6 years ago
Tomas Susanka	6f032456fc	tests/device/nem: mosaic with levy test	6 years ago
ZuluCrypto	7128347975	stellar tests - added missing pytest import	6 years ago
ZuluCrypto	5fccc4381b	fix style to match flake8	6 years ago
ZuluCrypto	200b5a71df	Merge remote-tracking branch 'upstream/master' into stellar	6 years ago
ZuluCrypto	2cf6414fa5	stellar - minor cleanup and simplification of some boolean field checks	6 years ago
Tomas Susanka	7cfbe689e8	tests/device/nem: different amounts; note about what is displayed	6 years ago
Tomas Susanka	50e755be46	tests/device/nem: known/unknown mosaics test	6 years ago
Aleksey Popov	8f31422adf	lisk: Fix wrong signature in tx tests	6 years ago
matejcik	cc7e3eb9b5	travis: force setuptools>=38 which download prebuilt .whls ... this fixes a build error in dependencies that we seriously don't care about which was happening in travis's py34	6 years ago
ZuluCrypto	49025aad2b	stellar tests - fix imports and indicate that tests are currently expected to fail	6 years ago
ZuluCrypto	61f5e1df61	stellar.py now returns a tuple from parse_transaction_bytes and no longer uses a reserved argument name	6 years ago
ZuluCrypto	ea6ced4dae	client.py - refactor Stellar signing loop to make the message flow clearer	6 years ago