Added feature --include-files

[alt440]

Added the flag --include-files to tarpaulin to only have a select amount of files that we get coverage from. It can save some time, as we are not looking at the traces of excluded files.

A condition has been added in the include_path function to make sure that --include-files is deactivated when no argument has been passed: otherwise, this would exclude all files from the report (as --include-files excludes all files by default).

Pretty much copied from the --exclude-files feature. Added some tests to make sure everything was working fine.

Here are some commands that I tested on another Rust project from the built image:
cargo tarpaulin --include-files src/jwt/mod.rs --out xml --> SUCCESS only 5 lines seen, 60% coverage
cargo tarpaulin --include-files src/jwt/* --exclude-files src/utils/* --out xml --> SUCCESS only 5 lines seen, 60% coverage.
cargo tarpaulin --exclude-files src/utils/* --out xml --> SUCCESS 101 lines seen, 3% coverage

[xd009642]

A few comments mostly minor things, it would also be nice if the tarpaulin.toml in the root is updated to add the include-files field as this is the "mega config example" where the entire config is presented.

Oh also the fmt check is failing so if you do a cargo fmt and commit the results as well when all that's done!

[xd009642]

Because we discussed it in DMs just figured I'd put it here. You should also be able to create a config object with the include-files set like:

let config = Config {
	included_files_raw: vec!["src/foo/*".to_string(), "src\\bar\\*".to_string()],
        ..Default::default()
};

[alt440]

I was really eager to try it!

But then, my excitement faded when I saw this:

included_files_raw is a private variable, just like excluded_files_raw, and for that reason I cannot set them this way.

As a bonus, I have added the LineAnalysis::new() error message. I will have issues with that as well.

I have been told that I should not make stuff public for the sole purpose of tests, but it's your call.

Do you want me to make those elements public?

[xd009642]

Oh right those are in a different module. That would only work in the tests in src/config/mod.rs

Outside the config module I'd just use the CLI Args to create the config type

[alt440]

I decided to go against the test in the src/test_loader.rs file. It wouldn't be possible: even the creation of a LineAnalysis object is not possible for the test. Plus, I already tried TarpaulinCli.parse_from method and it is not accessible

[xd009642]

Cool LGTM now, I'll merge this and look at cutting a new release 🎉