One of the methods is an implementation of the minimax algorithm. How would I go about testing this?

I'm a bit surprised by this question. My first reaction would "test it like you always test", but apparently, that isn't working for you. Which makes me wonder, how *do* you test? I test by giving the functionality I want to test input of which I know the output should be, and whether what I get is what I expect. Why wouldn't that work for a minimax algorithm? That algorithm doesn't depend on the phases of the moon, does it?

It's the same for the XS code. Test it the same way as you test Perl code. For the user it doesn't matter whether the implementation is pure Perl or XS, so why should it matter for the tests?

Abigail

In reply to Re: (OT) Help with test design by Abigail-II
in thread (OT) Help with test design by dragonchild

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.