17 Commits (c414e8abfa88d92e65c4ae759e10d8056b66fc80)

Author	SHA1	Message	Date
matejcik	68da6881b5	debuglink: add null debuglink, allow running tests interactively ... run with: INTERACT=1 pytest <your options here>	6 years ago
matejcik	5355ce4879	device_tests: upgrade get_marker to get_closest_marker ... This bumps pytest requirement to 3.6. But we have that everywhere already. For bonus points, get_closest_marker still exists in 4.1.	6 years ago
matejcik	85b85c67b3	trezorlib: reentrant session handling ... This fixes the breakage introduced by transport reshuffles. It's still not great and I'd love to see context manager based sessions. But it's good enough for now.	6 years ago
matejcik	aac7726824	trezorlib: transport/protocol reshuffle ... This commit breaks session handling (which matters with Bridge) and regresses Bridge to an older code state. Both of these issues will be rectified in subsequent commits. Explanation of this big API reshuffle follows: * protocols are moved to trezorlib.transport, and to a single common file. * there is a cleaner definition of Transport and Protocol API (see below) * fully valid mypy type hinting * session handle counters and open handle counters mostly went away. Transports and Protocols are meant to be "raw" APIs; TrezorClient will implement context-handler-based sessions, session tracking, etc. I'm calling this a "reshuffle" because it involved very small number of code changes. Most of it is moving things around where they sit better. The API changes are as follows. Transport is now a thing that can: * open and close sessions * read and write protobuf messages * enumerate and find devices Some transports (all except bridge) are technically bytes-based and need a separate protocol implementation (because we have two existing protocols, although only the first one is actually used). Hence a protocol superclass. Protocol is a thing that *also* can: * open and close sessions * read and write protobuf messages For that, it requires a `handle`. Handle is a physical layer for a protocol. It can: * open and close some sort of device connection (this is distinct from session! Connection is a channel over which you can send data. Session is a logical arrangement on top of that; you can have multiple sessions on a single connection.) * read and write 64-byte chunks of data With that, we introduce ProtocolBasedTransport, which simply delegates the appropriate Transport functionality to respective Protocol methods. hid and webusb transports are ProtocolBasedTransport-s that provide separate device handles. HidHandle and WebUsbHandle existed before, but the distinction of functionality between a Transport and its Handle was unclear. Some methods were moved and now the handles implement the Handle API, while the transports provide the enumeration parts of the Transport API, as well as glue between the respective Protocols and Handles. udp transport is also a ProtocolBasedTransport, but it acts as its own handle. (That might be changed. For now, I went with the pre-existing structure.) In addition, session_begin/end is renamed to begin/end_session to keep consistent verb_noun naming.	6 years ago
matejcik	620e48e4d0	tests: adapt tests to new APIs	6 years ago
matejcik	ffff11a462	style: isort & autopep	6 years ago
matejcik	c37bc9c38e	debug: improve infrastructure and expected message reporting	6 years ago
matejcik	88b50ac2ff	style: add makefile with style targets, final touchups	6 years ago
matejcik	e2d45397d4	device_tests: smarter device selection ... skips bridge, dies somewhat more cleanly when no device found	6 years ago
matejcik	3d3e9b67b4	style: apply black/isort	6 years ago
matejcik	201297a1f9	tests: close debuglink in fixture-based tests	6 years ago
matejcik	54f1599a5a	regenerate license headers ... This clarifies the intent: the project is licenced under terms of LGPL version 3 only, but the standard headers cover only "3 or later", so we had to rewrite them. In the same step, we removed author information from individual files in favor of "SatoshiLabs and contributors", and include an AUTHORS file that lists the contributors. Apologies to those whose names are missing; please contact us if you wish to add your info to the AUTHORS file.	6 years ago
matejcik	269eaa298f	tests: make a fixture out of client ... also implement Cancel tests	6 years ago
matejcik	9982ef98f9	Merge branch 'master' into matejcik/refactor	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	266e34eec4	tests/device_tests: disable protobuf outputs unless run with -v	6 years ago
matejcik	020b298020	tests/device: autodetect Trezor version and skip the appropriate tests automatically	7 years ago