Re^6: Writing tests when you don't know what the output should be

Thanks for this. Can you please help me understand why you used an internal and external accessor for dir? I'm new to Moose and I'm not quite sure why you did that. Thanks.

$PM = "Perl Monk's";
$MCF = "Most Clueless ~~Friar~~ ~~Abbot~~ ~~Bishop~~ ~~Pontiff~~ ~~Deacon~~ Curate";
$nysus = $PM . ' ' . $MCF;
Click here if you love Perl Monks

Comment on Re^6: Writing tests when you don't know what the output should be Download Code

Replies are listed 'Best First'.
Re^7: Writing tests when you don't know what the output should be by choroba (Cardinal) on May 18, 2016 at 08:57 UTC
It depends on what you want. My solution expects the user only wants to supply the directory name and doesn't care about the internal implementation. It locks in a dependency, though, so another approach would be to accept just an object with a defined interface (dependency injection) - it's easier to test and extend. You should start with a picture, define the behaviours of the objects, and the implementation should emerge from the design, not vice versa. ($q=q:Sq=~/;[c](.)(.)/;chr(-\|\|-\|5+lengthSq)`"S\|oS2"`map{chr \|+ord }map{substrSq`S_+\|`\|}3E\|-\|`7**2-3:)=~y+S\|`+$1,++print+eval$q,q,a, [download]	[reply] [d/l]

Replies are listed 'Best First'.

Re^7: Writing tests when you don't know what the output should be
by choroba (Cardinal) on May 18, 2016 at 08:57 UTC

You should start with a picture, define the behaviours of the objects, and the implementation should emerge from the design, not vice versa.

($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,
[download]

[reply]
[d/l]