Skip to content

Conversation

@jbazant
Copy link
Contributor

@jbazant jbazant commented Dec 3, 2025

Description

Split unit tests to 2 separate pipelines to give more time to suite-native tests.

TODO: set Unit Tests Suite Native as required check

Notes for QA

Nothing to test.

Related Issue

Resolve #22848

Screenshots:

🔍🖥️ Suite web test results: View in Currents

🔍🖥️ Suite desktop test results: View in Currents

🔍🖥️ Suite native android test results: View in Currents

@jbazant jbazant force-pushed the split-unit-tests-ci branch from 679dc9a to 87b0734 Compare December 3, 2025 10:10
@trezor-bot
Copy link
Contributor

trezor-bot bot commented Dec 3, 2025

✅ Previously successful run of [Test] PR Suite Desktop e2e tests workflow has been found.
⏭️ Skipping tests for this run.
💡 If you are unsure about your latest changes, please rerun the workflow manually. (Use the Re-run all jobs option)

@trezor-bot
Copy link
Contributor

trezor-bot bot commented Dec 3, 2025

✅ Previously successful run of [Test] PR Suite Web e2e tests workflow has been found.
⏭️ Skipping tests for this run.
💡 If you are unsure about your latest changes, please rerun the workflow manually. (Use the Re-run all jobs option)

@jbazant jbazant changed the title chore(suite-native): Run unit tests as 3 separate pipelines Run unit tests as 3 separate pipelines Dec 3, 2025
@jbazant jbazant added the no-project This label is used to specify that PR doesn't need to be added to a project label Dec 4, 2025
@jbazant jbazant force-pushed the split-unit-tests-ci branch from 87b0734 to ae5167d Compare December 4, 2025 09:15
@jbazant jbazant changed the title Run unit tests as 3 separate pipelines Run native tests in separate pipeline Dec 4, 2025
@jbazant
Copy link
Contributor Author

jbazant commented Dec 5, 2025

/rebase

@github-actions
Copy link

github-actions bot commented Dec 5, 2025

@trezor-bot trezor-bot bot force-pushed the split-unit-tests-ci branch from ae5167d to 2cdd014 Compare December 5, 2025 12:21
Copy link
Member

@vdovhanych vdovhanych left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not against the change it will need to be coordinated with the team because after the merge it will break all pullrequests before i change the required checks and they rebase the branches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-project This label is used to specify that PR doesn't need to be added to a project

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Mobile Trade: Tests run for too long in CI

3 participants