Improve Test Coverage about caddy

[mholt]

Yes indeed. You are more than welcome to write tests. I'm actually writing an example test file for the rewrite middleware right now (it's simple; a good starting point).

[mholt]

@j-mcnally See b2ee663

[hackintoshrao]

I'm keen on writing tests ..What would the best place to start writing tests ?

[mholt]

@Karthic-Hackintosh Welcome! Any of the middlewares here: https://github.com/mholt/caddy/tree/master/middleware

Each middleware has an associated "setup" file that also needs testing: https://github.com/mholt/caddy/tree/master/config/setup - all these do is parse the configuration and set up the middleware so it's ready to use.

Those would be great places to start.

[miko-code]

Hi ,
Are you still need help to test stuff ?
Where i can find the example test you wrote ?

[mholt]

@miko-code We've made lots of progress, but still need help. For example, https://github.com/mholt/caddy/blob/master/config/setup/root.go needs tests. You can see an example of similar tests here (though these are more complicated): https://github.com/mholt/caddy/blob/master/config/setup/tls_test.go

root.go is super-easy to test and only needs one or a few assertions I think.

[Makpoc]

Hi,
As with everyone before me in this thread I would also like to help with some tests. I saw that the root.go is still without test so I'll take a look at it whenever I have time and try to write some. I'll need to get familiar with the functionallity first, but hopefully it won't take long..

[mholt]

@Makpoc We'd totally welcome your help :) Feel free to join us in Slack if you have any questions!

[mholt]

I'm closing this since we have tests in every package now and have vastly improved from having no tests at all. Thanks to all who have got us this far.

Tests will always be changing and needing improvements and more thorough coverage, so if you see this issue later, please don't hesitate to jump in to help with tests. Even though the issue is closed, we are always working on improving tests and test coverage. Feel free to ask if you want to get some pointers to get started contributing!