Test databases are always cleaned and then fixtures loaded, so you'll need to add any permissions into fixtures too, or create them on the fly (Permission.create, FG), as it stands.

#11206 added a method into the plugin definition to return which roles and permissions were registered, so you may be able to use this to recreate the permissions - or test that they're correct.

Oh, I didn't realize fixtures would reset the whole database, I figured it'd use transactions intelligently and keep the database at the initial state at the beginning of each test. I don't want to use fixtures in foreman_salt, but using FG works fine.

You can close this if you want.

It's less that fixtures cause the reset, just that Rails starts with an empty test database and either it, and/or database_cleaner cause the reset. Fixtures get loaded after, plus any setup mechanisms in the test (which could call FG).

I'll leave it open for now, unless you wish to close it, because I agree that Foreman could help more here, perhaps by (optionally?) populating permissions in the test setup. foreman_salt isn't the only plugin that has hit this problem when writing tests that depend on permissions, because I think it's been mentioned in foreman_discovery too.