11 Commits (7bd3cd6b136e756ba30a27c68f81974d6adb2cf2)

Author	SHA1	Message	Date
matejcik	3d3e9b67b4	style: apply black/isort	6 years ago
matejcik	c0ef1ec535	tests: use new API	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
Tomas Susanka	63222931be	tests/device: nem is not xfail anymore	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	579adb1871	tests: update to use parse_path	6 years ago
Tomas Susanka	51d9a809bc	tests: pytest xfail is used instead of skipping	7 years ago
Pavol Rusnak	70e6d13c23	device tests: simplify, drop unittest dependency	7 years ago
Pavol Rusnak	41b75c5655	device_tests: use skip_t1 and skip_t2 markers	7 years ago
Saleem Rashid	1c8f03968c	tests: Move to trezorlib.tests	7 years ago