If you have 90% coverage of your component as an integration instead of a unit test that wouldnt be horrific either. Not complete but at least its minimal effort.
But if you have 0% coverage across the board... well its your funeral, especially if you want this to be adopted and developed into the future.
Either way like I said my intention was just toa sk what you had in terms of coverage/benchmarks. Only reason i am defending my perspective at all is because you , as usual, got condescending.
Personally i dont find the conversation useful at this point. The answer is no you have no benchmarks, and no tests. I suggest against it.. good luck, and thanks for the effort.
The point of integration tests isnt because you cant test it by hand. Its so other developers who modify things dont have to do the same test you would do every single time they make a modification. To be able to have the automated.
Not every developer is going to run their own instance, not ever developer is ok using a live production server as a test bed, not every developer is going to want to test every single aspect by hand every time they make a mistake, not ever developer will even know when a change might warrant one particular test over the other.
So if you really think that fills the same need as integration testing, then it seems clear to me at this point you dont really understand the point of integration testing in the first place.
As I said as I tried to end this conversation multiple times before (but for some reason you keep extending it despite your frustration with it in the first place)... do what you want, if you dont want to write an integration test and just want to run it on your server and take the risk, go for it. Hopefully pleorma wont integrate it into the code base without proper tests, but thats on you, its your risk to take. But dont continually imply that me having an interest in integration tests is somehow silly just because you can test it manually.