Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Only run tests for a single flavour #5454

Closed
mitchhentges opened this issue Sep 20, 2019 · 1 comment
Closed

Only run tests for a single flavour #5454

mitchhentges opened this issue Sep 20, 2019 · 1 comment
Labels
eng:automation Build automation, Continuous integration, .. P3 Some future sprint wontfix

Comments

@mitchhentges
Copy link
Contributor

mitchhentges commented Sep 20, 2019 •
edited by data-sync-user
Loading

When automation runs tests, it just does ./gradlew ... test ..., which means that it (probably?) runs tests for each flavour.

We should instead just run the tests for a single flavour, to improve the timings of the test task

┆Issue is synchronized with this Jira Task
@mitchhentges mitchhentges added the eng:automation Build automation, Continuous integration, .. label Sep 20, 2019
@mitchhentges mitchhentges mentioned this issue Sep 20, 2019
Closed
@boek boek added the P3 Some future sprint label Dec 28, 2019
@stale
Copy link

stale bot commented Feb 5, 2021

See: #17373 This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Feb 5, 2021
@stale stale bot closed this as completed Feb 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
eng:automation Build automation, Continuous integration, .. P3 Some future sprint wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@boek @mitchhentges