We just kicked off the third six-week cycle and I’d like to share what the plan is for the cycle.
Test insights 
We are continuing the investment in providing you with data from automation with Xcode projects by bringing you test insights. Like we did with build insights, using a scheme test post-action we’ll collect and push test results on completion, and this will work in local and remote environments.
You’ll be able to see test runs over time, and insights over a particular test case, for example how their execution time changes or whether they are flaky or not.
Having a fast and reliable test suite is strongly connected to productive app development, so it’s a must-have feature to have on the platform that we are shaping.
Agentic QA 
In a world where agents can code to implement new features or bug fixes, verifying with build-time tools that the work is valid, we believe there’ll be a need for verifying the work at runtime. Traditionally, teams did that through automation tests, which are costly to develop, maintain, and run, or QA teams that are financially costly. What if an agent could take the testing role, ensuring the testing is scoped to a particular piece of work (i.e. context-aware), and has access to the device/simulator and runtime APIs to run, assess, and diagnose issues, returning a report of their testing? Our bet is that they can do an exceptional job at that, so we are going to bring agentic QA to the platform.
We’ve got the object to be tested (i.e. previews) and a CLI to conveniently upload them. We’re investing in being able to run one-off tasks in remote Mac environments (e.g. to run the agent), and we have an integration with GitHub that we can leverage to gather context and report results back. We’ve got all the ingredients to make this happen, and we couldn’t say no.
Website redesign
We started the design of a new marketing site for Tuist, and we’ll continue the effort this cycle. Our goal is to have the most important pages ready for implementation at the end of the cycle. If you are curious about what the design will look like, here’s a sneak peek of the amazing work that the team is doing:
On-demand signing for previews
There’s nothing more frustrating than trying to install a preview on a device and not being able to do so because the device is not part of the certificate. Traditionally, teams had to go through an annoying process of incorporating the device into their developer account, re-generating the certificate with it, re-signing and sharing the app again with the person. Annoying, isn’t it? So we are going to bring sign-on-the-fly to Tuist such that if we detect that scenario, we do all of that for you in the background while you wait a few seconds until it completes.
We don’t expect to complete this work as part of the cycle, so we’ll focus in this cycle on detecting whether the destination device is included in the certificate.
Can’t wait to see all this work going live! The vision that we have for Tuist keeps getting more complete, and the integration with existing Xcode projects is getting smoother and smoother. If you have any questions, let me know in a comment below and I’ll be happy to answer.