Faster tests you can actually trust.

Run only the tests affected by your changes and flag flaky ones automatically, so a successful build truly means success.

阅读文档

功能

Faster tests, fewer surprises

Skip unnecessary tests, distribute the rest efficiently, and keep your test suite healthy with built-in insights.

TuistAppleArchiveTests TuistAuthCommandTests TuistAutomationTests TuistCASTests TuistCITests TuistCacheEETests TuistCoreTests TuistGeneratorTests TuistKitTests TuistLoaderTests TuistServerTests TuistSupportTests

41
```
final class AuthSessionStore {
```

    private let keychain: KeychainClient

    func restore() throws -> AuthSession? {

        guard let data = try keychain.read(.session) else {

46
```
            return nil
```
47
```
        }
```

        return try decoder.decode(AuthSession.self, from: data)

49
```
    }
```

        let session = try decoder.decode(AuthSession.self, from: data)

        guard session.expiresAt > Date.now else {

            try keychain.delete(.session)

53
```
            return nil
```
54
```
        }
```
55
```
        return session
```
56
```
    }
```
57

    func persist(_ session: AuthSession) throws {

        let data = try encoder.encode(session)

        try keychain.write(data, for: .session)

61
```
    }
```
62
```
}
```

Run only what changed

Skip tests that don't need to run. Tuist uses project hashing to identify what changed since the last successful run and executes only the affected tests.

0ms 5ms 10ms 15ms 20ms 25ms 30ms 35ms 40ms 45ms 50ms 55ms

Split tests intelligently

Run large test suites across multiple CI runners without creating one slow shard. Tuist uses historical test timings to balance tests so each runner finishes at roughly the same time.

Test runs 75

Skipped tests 5

Failed test runs 15

p90 test run duration 1m 40s

Know what's slowing you down

Track test performance over time, uncover slow tests, and understand failed runs without digging through CI logs.

Stop flakes from blocking CI

Automatically detect flaky tests, track them over time, and quarantine them so unreliable tests don't keep blocking CI while you fix them.

What are you waiting for?

为您的应用开发注入动力

开始使用与我们交谈

缓存

Compute

测试

预览

生成的项目

注册表

关于

Slack

Hive

社区论坛

客户

通讯

GitHub