Generate test workspace in temp location

Ideas
1

When I run tuist test ... it replaces my generated workspace with one configured specifically for testing the requested targets. This is annoying when I’m working in Xcode and have AI running tests. Would it be reasonable to have the test command generate the workspace in a temp location?

1 Like
2

I think it should be fine. @marekfort can you think of any issues? Maybe not being able to reuse derived data’s content?

3

This is the behavior we used to have – but we moved away because it was problematic for two reasons:

  • projects generated in a temporary location didn’t reuse the derived data, resulting in an effectively clean build every time you ran tuist test
  • teams needed to be very meticulous about respecting the difference between SRCROOT (points to the directory where the root for sources is located) and PROJECT_DIR (location of the Xcode project). While the former should stay the same as the project is generated in different locations, the former changes. Unfortunately, usually these two variables are the same, so teams often use the two interchangeably. Respecting the difference between the two would very often cause confusion and it was a hurdle in adopting tuist test

I’d strongly lean to keep the current default behavior, but we can allow generating the project in a temporary location based on a new flag.