assuming you are in the . directory, your tests are the default
t/*.t , and your module lives as
lib/AI/Embedding.pm , then
prove -l lib
If you have XS binaries (I haven't looked at AI::Embedding, so I don't know), then you may need to build it first (which puts modules in blib/lib ), and then use prove -b blib
prove describes all of these options, and more.
And if you're using a standard build system, then the standard incantation
perl Makefile.PL
make
make test
(or your build system's equivalent incantation) will also make use of your in-progress copy rather than a previously installed.
edit 1: standard incantation
edit 2: remove ambiguous sentence full-stop in first paragraph, because it looked like part of the prove command, when it wasn't intended to
edit 3: strike out lib and blib : per Re^3: Path to prove and Re^4: Path to prove, -l and -b options do not take arguments; use the -I path argument if you need to specify a specific directory.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.