Creating a bug for this so I don't forget. After installing a base installation of remora from remora.sql and remora-test-data.sql, there are a bunch of errors due to missing addontypes, translations and files. I have most of it cleaned up, just need to do some testing and verification all errors are fixed.

Thanks, Ryan. I had a little conversation with Mike lately and we agreed that we should maybe rethink the way tests work in AMO, so we don't need to use test data anymore the way we do it right now: It becomes increasingly hard to work with test data that is up to date, yet consistent with the existing tests. Maybe working more with mock objects may be a way to get rid of our dependency on a consistent set of made-up add-ons?

Would mock objects test the database? Also, the test data is important for developers who don't or can't have access to a production dump of the database.

Do we need to test the database? But that's a good point, working test data is necessary for community contributions.

I would think we should be testing read and write functionality for our classes, which uses the database.

We should rethink the way tests work, sure, but this bug is about the installation working after running remora.sql. Is that working? If so, we should close this

Our testing strategies are going to undergo a major change and I want to have far more useful test data available. Until that day, remora.sql and the test data mostly work so this is fixed. (I say mostly because we recently pulled images out of the database. This means if you don't have them locally AMO won't have any images on it. :-/)