Testing ServiceProviders in a standalone package?

I'm weighing the pro's and con's of testing my ServiceProviders in a standalone package.

Since the laravel application is not a dependency of the package, I don't think I should/can write integration tests.

But there are times where I make typos in the use statements that causes me to create a whole new version just for these small errors. Do you unit test your ServiceProvider bindings for additional code coverage?

Mocking closures just looks like a pain and it's looking more like expensive spell checking than actual testing.