# Restrict selective test results uploads to specific branch or environment

**URL:** https://community.tuist.dev/t/restrict-selective-test-results-uploads-to-specific-branch-or-environment/146
**Category:** RFCs
**Created:** [October 25, 2024, 12:22pm UTC](https://community.tuist.dev/t/restrict-selective-test-results-uploads-to-specific-branch-or-environment/146 "2024-10-25T12:22:48Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![marekfort](https://community.tuist.dev/user_avatar/community.tuist.dev/marekfort/32/8_2.png) [@marekfort](https://community.tuist.dev/u/marekfort)
#### Post date: [October 25, 2024, 12:39pm UTC](https://community.tuist.dev/t/restrict-selective-test-results-uploads-to-specific-branch-or-environment/146/3 "2024-10-25T12:39:16Z")

</div>

> [@pepicrft](#):
>
> I wonder if `--no-upload` is explicit enough about what’s being uploaded by the flag. This is something that we can solve with the documentation of the flag, but I was wondering if we can make the naming explicit enough to make that unnecessary.

The motivation behind using `--no-upload` was to have something a bit more generic as it’s likely that if you don’t want selective test results to be uploaded, nor would you want that for binary cache.

Alternatively, we can have specific categories as a list, such as `tuist test --no-upload selectiveTests`. If you don’t specify any, we would default to all categories. That would be in line with how `tuist clean` works where you can run `tuist clean` to clean everything, but you can also run `tuist clean selectiveTests` to clean only selective test results.

What do you think?

---

_[View the full topic](https://community.tuist.dev/t/restrict-selective-test-results-uploads-to-specific-branch-or-environment/146)._