Test initilization with TCAReducer

[grahamhindle]

i have a @fetchall in my struct
@ObservableState
public struct State: Equatable, Sendable {
@ObservationStateIgnored
@fetchall(
Avatar
.order(by: .dateCreated)
.limit(10)
.select { PopularAvatar.Columns(avatar: $0) }
)
var popularAvatarRecords: [PopularAvatar] = []

    var popularAvatars: [Avatar] {
        let allPopular = popularAvatarRecords.map(\.avatar)
        // Filter popular avatars based on current detailType
        return allPopular.filter { avatar in
            switch detailType {
            case .all:
                true
            case .publicAvatars:
                avatar.isPublic
            case .privateAvatars:
                !avatar.isPublic
            }
        }
    }
    ...

and a testfile that initilizes a test database
@suite(
.dependencies {
$0.date.now = baseDate
$0.context = .test
$0.defaultDatabase = try appDatabase()
try $0.defaultDatabase.write { try $0.seedTestData() }
}

)

a test
extension BaseTestSuite {
@mainactor
struct AvatarFeatureTests {
@test func getRecords() async throws {

        let store = TestStore(initialState: AvatarFeature.State()) {
            AvatarFeature()
        }
        
        try await store.state.$avatarRecords.load()

        #expect(store.state.avatarRecords.count == 3)
    }
}

}

when i run individual tests - all is good, and the tests run as expected. However, if i exercise the individual tests, or the suite all works fine, but if i exercise the whole test target, even with just one suite, i get an exception.

The 'xcodebuild' command exited with error code 65 and message:
2025-08-14 08:43:36.060 xcodebuild[15510:4376109] [MT] IDETestOperationsObserverDebug: 15.623 elapsed --
Testing started completed.
2025-08-14 08:43:36.060 xcodebuild[15510:4376109] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000
sec -- start
2025-08-14 08:43:36.060 xcodebuild[15510:4376109] [MT] IDETestOperationsObserverDebug: 15.623 sec, +15.623
sec -- end
Testing failed:
xctest (15843) encountered an error (Early unexpected exit, operation never finished bootstrapping - no
restart will be attempted. (Underlying Error: Crash: xctest (15843) ))
** TEST FAILED **

any help in understanding this would be helpful. My theory is that the store is initialized before the database is initialized and seeded.

[mbrandonw]

Hi @grahamhindle, can you reproduce this problem in a minimal project and share it? The info provided isn't enough for me to know what is going on.

[grahamhindle]

I’m almost certain now that it is a problem with crest. I have 15 modules , and there seems to be a problem with the test. It’s only at the target level. When I run a test suite using tca with sharinggrdb, all the tests run. In every module, no matter if I have complex queries in the feature. It I’ve tried to run from Tuist, swift test, removed the fetch. I’ve tried swift 6.1,6.1.2, 6.2 with iOS 18.4, 18.5, 18.6, iOS 26.0, but all gave the same resultI’ve created a smaller app, with a framework, and my database framework which I will send you. I’ve tried a number of Tuist versions as wellThanks for your support and I am making extensive use of SharingGRDB. It’s a great library Sent from my iPhoneOn 14 Aug 2025, at 15:54, Brandon Williams ***@***.***> wrote: Hi @grahamhindle, can you reproduce this problem in a minimal project and share it? The info provided isn't enough for me to know what is going on. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[mbrandonw]

If you believe this is a problem with Tuist then you should start a discussion on their repo.

[grahamhindle]

Thanks for your help.
XCTest was bringing in symbols from other test suites that had been excluded from the build, and this was causing the exception at startup, but when i ran the individual tests, or just the test suite it was fine. However, the real problem was me. There was a missing dependency in my test target. A lot of detective work narrowed it down. i have kept the xcodeproj files, and will send to Tuist to see if they can shed any light on it.