Acme-Devel-Hide-Tiny

 view release on metacpan or  search on metacpan

CONTRIBUTING.mkdn  view on Meta::CPAN

24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
### Running tests
 
You can run tests directly using the `prove` tool:
 
    $ prove -l
    $ prove -lv t/some_test_file.t
 
For most of my distributions, `prove` is entirely sufficient for you to test any
patches you have. I use `prove` for 99% of my testing during development.
 
### Code style and tidying
 
Please try to match any existing coding style.  If there is a `.perltidyrc`
file, please install Perl::Tidy and use perltidy before submitting patches.
 
If there is a `tidyall.ini` file, you can also install Code::TidyAll and run
`tidyall` on a file or `tidyall -a` to tidy all files.
 
### Patching documentation
 
Much of the documentation Pod is generated at release time.  Some is
generated boilerplate; other documentation is built from pseudo-POD
directives in the source like C<=method> or C<=func>.



( run in 0.225 second using v1.01-cache-2.11-cpan-fd5d4e115d8 )