Are there conventions for function names when using Perl Test :: More?

Question

Are there conventions for function names when using the Perl Test :: More or Test :: Simple modules?

I specifically ask a question about the names of the functions that are used to configure the test environment before the test and disrupt the environment after the successful completion of the test (s).

amuses

Rob

Answer 1

I do not think there are such agreements.

The only way to do this is perhaps to use BEGIN / END blocks if resources will be used throughout the file.

, , - , / .. , , .

- ...

BEGIN {
   # If you want to set some global db setting/file setting/INC changes etc
}

# Tests functionality 1...
{
     # have fun .... 
}

# Tests functionality 2...
{
     # have more fun .... 
}

END {
   # Clean up the BEGIN changes
}

, perl... http://perlandmac.blogspot.com/2007/08/using-perl-testsimple-and-testmore.html

Answer 2

XUnit, Test::Class. Test(setup) Test(teardown) , , , . ( , ) .

Answer 3

, , http://perldoc.perl.org/Test/More.html , .

Answer 4

.

perldocs, .

XUnit.

Jagmal, BEGIN END , , . , .. .t .

Test:: Most, , . .

. , BEGIN END, , , , .

,

Rob

Answer 5

Test:: More , () Perl. , , Jagmal, , .

script. , ( unit test) , , .

Answer 6

, , - Test:: More for Test:: Most

Answer 7

Perl . , , Perl script.

, , , .

, , .

, t/*. t CPAN. , , , .

Answer 8

If you can also take part in acceptance tests, such as Ruby Cucumber, take a look at this small example http://github.com/kesor/p5-cucumber , which uses Test :: More and the cucumber style of acceptance tests.