ah but i also used fixture files which does make the tests act slightly differnent

but "race conditions, mostlly" could describe what i experience

its just ive had issues involving sitetree and the setup publish solved it it just wasnt a mysql v sqlite issue but never know 🙂

test IDs are not guaranteed - we just think they are because we control the environment. I've been caught by stuff like that before.

debug with a line @sander_ha - SiteTree::get()->column() - make sure your ID is as you think it is

Hmm I can try that out later. Buy yeah should work the same