Hugo Testing - How to Contribute and Help

@tommasop @teknico @oscar_b @bjornerik @mohae @spf13

Folks, if you’ve not yet seen it @spf13 has merged in some of my tests and fixes into master.
@spf13 - ta, very much :slight_smile:

I’ve just done a quick catchup and I’m seeing test coverage of:

$ go test -cover ./…
? GitHub - owenwaller/hugo: A Fast and Flexible Static Site Generator built with love by spf13 in GoLang [no test files]
ok github.com/owenwaller/hugo/commands 0.023s coverage: 11.5% of statements
? github.com/owenwaller/hugo/create [no test files]
ok github.com/owenwaller/hugo/helpers 0.013s coverage: 46.4% of statements
? github.com/owenwaller/hugo/hugofs [no test files]
ok github.com/owenwaller/hugo/hugolib 0.114s coverage: 65.0% of statements
? github.com/owenwaller/hugo/livereload [no test files]
ok github.com/owenwaller/hugo/parser 0.006s coverage: 42.6% of statements
ok github.com/owenwaller/hugo/source 0.007s coverage: 45.7% of statements
ok github.com/owenwaller/hugo/target 0.005s coverage: 49.2% of statements
ok github.com/owenwaller/hugo/transform 0.009s coverage: 52.2% of statements
ok github.com/owenwaller/hugo/utils 0.002s coverage: 11.1% of statements
? github.com/owenwaller/hugo/watcher [no test files]

So what I’m going to suggest is that we take a package each (or in pairs - however folks want to wok) and see if we can up the coverage.

So I’ll take the utils package as that’s at 11% and I’ll see if I can up helpers back up again. I seems to have gone down post refactor.

Are there any other takers for the other modules?

Owen