We downloaded the uf2 file from the release page onto our pico, and it seems to function as a key properly when registering the key with google. However, when running the tests, the key fails a lot of them. Are the tests all meant to pass when using the release image? Are the tests testing special features that need to be enabled?
What are the tests testing for?
Do they normally fail with the code built for a non-w pico?
Some of the tests are encountering errors with the fido2 errors or errors with setting up the tests. Is there a dependency we are missing or a flag that needs to be set?
Tests are designed to test FIDO and other funcionalities as well to ensure proper CD/CI.
Tests should not fail (except for phy u2f, which might fail due to OS timing aspects).
Tests shall be executed sequentially. Do not execute specific tests because prior tests might be designed to reset the memory onto a clean state, like seems happening in the screenshot. Avoid using -k flag and let start from the beginning.
We downloaded the uf2 file from the release page onto our pico, and it seems to function as a key properly when registering the key with google. However, when running the tests, the key fails a lot of them. Are the tests all meant to pass when using the release image? Are the tests testing special features that need to be enabled?