Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

T2B1: make sure all tests are updated for the new model #2724

Open
2 of 4 tasks
matejcik opened this issue Jan 9, 2023 · 9 comments
Open
2 of 4 tasks

T2B1: make sure all tests are updated for the new model #2724

matejcik opened this issue Jan 9, 2023 · 9 comments
Assignees
Labels
code Code improvements
Milestone

Comments

@matejcik
Copy link
Contributor

matejcik commented Jan 9, 2023

  • persistence tests
  • upgrade tests
  • U2F tests
  • FIDO2 tests
@matejcik matejcik added the code Code improvements label Jan 9, 2023
@grdddj grdddj added this to the 🎨 T2B1 milestone Jan 10, 2023
@grdddj
Copy link
Contributor

grdddj commented Apr 12, 2023

Click and device tests are supported fully. Not sure what other kinds of tests (persistence, upgrade) do we want to run for TR

@Hannsek
Copy link
Contributor

Hannsek commented Jun 1, 2023

Are there any additional tests we want?

@grdddj
Copy link
Contributor

grdddj commented Jun 1, 2023

Are there any additional tests we want?

Not immediately now, but we would want to add persistence and upgrade tests

@swageeth

This comment was marked as off-topic.

@mmilata
Copy link
Member

mmilata commented Nov 7, 2023

I think we need to run a T2B1 version of every existing T2T1 test job. Notably also u2f and fido2.

@mmilata
Copy link
Member

mmilata commented Aug 29, 2024

FIDO2 tests only need the T2B1 equivalent of trezor/fido2-tests#4

@matejcik
Copy link
Contributor Author

persistence tests enabled in #3686

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code Code improvements
Projects
Status: 🎯 To do
Development

No branches or pull requests

5 participants