Re^4: How to write testable command line script?


The stupid question is the question not asked
	PerlMonks

Re^4: How to write testable command line script?

by thechartist (Monk)

on Nov 24, 2018 at 18:47 UTC ( [id://1226266]=note: print w/replies, xml )

Need Help??

in reply to Re^3: How to write testable command line script?
in thread How to write testable command line script?

Thanks for revisiting this. I have seen a number of good solutions here, and have a better understanding of the testing tools.

My current goal is to clean up the initial script so that the test code actually runs. I've done some work on this in the morning, and I see that my tests are using numeric equality improperly.

I will be looking at some of the subs in Test::More first, then I will explore some of the ideas presented in the re-writes of my code. Once it is cleaned up, it might make for a good tutorial series to introduce newcomers the concept of testing right at the beginning of their studies.

Comment on Re^4: How to write testable command line script?

Replies are listed 'Best First'.

Re^5: How to write testable command line script?
by AnomalousMonk (Archbishop) on Nov 24, 2018 at 19:11 UTC

... introduce newcomers [to] the concept of testing right at the beginning of their studies.

I can't restrain myself from wholeheartedly endorsing this thought. More than once have I been given the task of making a simple mod to an application that had no adequate testing framework associated with it. The "simple" mod soon turned into a nightmare from which there was no waking. ("The horror... The horror...") Introducing novices to these design techniques is a wonderful gift.

Give a man a fish: <%-{-{-{-<

[reply]
[d/l]

In Section Seekers of Perl Wisdom