@simahawk it used to work. Now registry isn't cleaned anymore. I got errors on tests:

TypeError: Component 'component1' (in class <class 'odoo.addons.component.tests.test_build_component.TestBuildComponent.test_register.<locals>.Component1'>) already exists

Tried self.registry.reset_changes() from
https://www.odoo.com/documentation/15.0/developer/reference/backend/testing.html#odoo.tests.common.TransactionCase.
Doesn't help.

@simahawk it runs without issues locally, and also base_rest with this variant runs

the point is not if it works or not. The point is that the setup should happen on the class and not on each test. I'll have a look tomorrow.

the point is not if it works or not. The point is that the setup should happen on the class and not on each test. I'll have a look tomorrow.

I hope it's. I watched your OCA video about testing techniques

Missing commit history Please follow the migration procedure here: https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-15.0

@dreispt you are late 🤣 The history is there because the repo has been re-initialized w/ modules uninstallable 😉

See #420 (comment)

pls squash the last commit once you have done

@simahawk I was just flying by. Not that I read it, but I updated #418 accordingly.

@simahawk I was just flying by. Not that I read it, but I updated #418 accordingly.

alright, thanks!

@simahawk definitely didn't pay attention to other modules. Will also update test_component, but to me makes sense not to open separate PR and add just new commit here. Is it ok?

no, because the module is called test_component for a reason ;)

test_component migrated on #424

/ocabot merge nobump

This PR looks fantastic, let's merge it!
Prepared branch 15.0-ocabot-merge-pr-423-by-simahawk-bump-nobump, awaiting test results.

Congratulations, your PR was merged at 70f5dc1. Thanks a lot for contributing to OCA. ❤️

Hello @simahawk , can you give a short explanation why SavepointComponentCase was removed from the tests?
I work with a module that relies on it.

Thanks

Hello @john-herholz-dt,

I just ran into the same problem, and I found that SavepointCase was merged into TransactionCase. Just replace SavepointComponentCase by TransactionComponentCase and it should work. More info.

Regards.