Are our integration tests over the top?

[JonruAlveus]

As I’m going through our endless integration tests, I’ve thought about a couple of things.

We have many many integration tests
I get the principle that a test should only check one thing. I have an issue with that when the tests (if you ran them all) could end up in the hour long region. Most of the I tests we have check a single property has updated as most of what we do is essential crud actions. Could we bypass the principle and merge a lot of tests together into one bigger one that gives us the same coverage in vastly less time? Then the slow tests become manageably slow tests!

For example, if you are creating a repository, it has a bunch of string, numeric and Boolean fields. All of these just need testing in 2 states (to make sure we can set them to values other than the defaults) and if appropriate not set them at all to see that they don’t change.

Covering every route variety
As per the discussion on repo vs repositories routes, do we need to support them all? They are pretty much doubled up currently.

Attributes for account types
As per the other discussion, how should we be doing attributes for organisation tests, paid for accounts etc. There seems to be very little different between a standard and organisation account when it comes to most common routes. Do we need to test against orgs if they are the same route?