-
-
Notifications
You must be signed in to change notification settings - Fork 194
Issues with library testing #5
Comments
Also you see errors because you have no TREZOR device connected. |
Yes, but they should respond to It was connected, so that means that tests fail on OSX as of now run-separate.sh shouldn't return any OK/FAIL status for each test? |
Do you have run-separate outputs into |
@prusnak tests require debuglink, correct? That said, nothing in /tests/ will run against stock firmware... |
@prusnak I have, setup.py installed them as dependencies and install succeeded. I have lots of @slush0 if that's correct, it should be mentioned that tests are not to test device accesibility, state and state of library against platform, probably remove the tests from public repository and replace them with tests that user/developer can run against stock firmware? |
Does running the script as root work? If yes then my guess would be that you need to do something similar like udev rules on Linux (https://github.com/trezor/trezord/blob/master/release/linux/trezor.rules for inspiration). No unit tests can be run on stock firmware, because they need to know internal data of TREZOR that stock firmware never shares for obvious reasons. |
Environment OS X, x64, 10.9.4 (not relevant probably)
Python version 2.7.8
run.sh
orrun-separate.sh
?python setup.py test
doesn't react, should execute given tests after in-place build./run-separate.sh
gives no output on tests success/failure, example output:./run.sh
intests
folder, gives 99 errors like this:The text was updated successfully, but these errors were encountered: