<commit_before>=head1 NAME

OpenResty::Spec::TestSuite - Introduction to the OpenResty test suite

=head1 SYNOPSIS

    $ make test -f dev.mk
    # OR
    $ prove -Ilib -r t

=head1 DESCRIPTION

OpenResty comes with a relatively big test suite.

Most of the test suite is organized by the L<Test::Base>. The main test
scaffold is in the F<t/OpenResty.pm> file.

There's various different ways to run the suite.

The C<backend.type> option in the config file (i.e.,
F<etc/site_openresty.conf>) determines which backend the server is
using. Possible values are C<Pg>, C<PgFarm>, and C<PgMocked>. The default
value is C<PgMocked>, which is a mocked-up version of the C<Pg> backend,
so that users without a proper Pg setup (like CPAN testers) can still
run the whole test suite. Please see L<OpenResty::Backend::PgMocked>
for more information.

The C<test_suite.use_http> option in the config file determines whether
or not the test scaffold should use HTTP to test the server. When it
is set to 1, the test harness will use C<LWP::UserAgent> to test the
server specified by the C<test_suite.server> and C<test_suite.server2>
options. If set to 0, the test suite will run directly in the same
process of the OpenResty server by using a mocked-up CGI environment
provided by L<WWW::OpenResty::Embedded>.

Note that when C<test_suite.use_http> is set to 1, it's possible to test
a I<remote> OpenResty server.

=head1 AUTHOR

<NAME> (agentzh) C<< <<EMAIL>> >>

=head1 SEE ALSO

L<OpenResty>.
<commit_msg> r10482@agentz-office:  agentz | 2008-07-19 15:12:51 +0800  fixed the email address<commit_after>=head1 NAME

OpenResty::Spec::TestSuite - Introduction to the OpenResty test suite

=head1 SYNOPSIS

    $ make test -f dev.mk
    # OR
    $ prove -Ilib -r t

=head1 DESCRIPTION

OpenResty comes with a relatively big test suite.

Most of the test suite is organized by the L<Test::Base>. The main test
scaffold is in the F<t/OpenResty.pm> file.

There's various different ways to run the suite.

The C<backend.type> option in the config file (i.e.,
F<etc/site_openresty.conf>) determines which backend the server is
using. Possible values are C<Pg>, C<PgFarm>, and C<PgMocked>. The default
value is C<PgMocked>, which is a mocked-up version of the C<Pg> backend,
so that users without a proper Pg setup (like CPAN testers) can still
run the whole test suite. Please see L<OpenResty::Backend::PgMocked>
for more information.

The C<test_suite.use_http> option in the config file determines whether
or not the test scaffold should use HTTP to test the server. When it
is set to 1, the test harness will use C<LWP::UserAgent> to test the
server specified by the C<test_suite.server> and C<test_suite.server2>
options. If set to 0, the test suite will run directly in the same
process of the OpenResty server by using a mocked-up CGI environment
provided by L<WWW::OpenResty::Embedded>.

Note that when C<test_suite.use_http> is set to 1, it's possible to test
a I<remote> OpenResty server.

=head1 AUTHOR

<NAME> (agentzh) C<< <<EMAIL>> >>

=head1 SEE ALSO

L<OpenResty>.

{'fraction_non_alphanumeric': 0.08126631853785901, 'fraction_numerical': 0.013381201044386422, 'mean_word_length': 4.37719298245614, 'pattern_counts': {'":': 0, '<': 49, '<?xml version=': 0, '>': 49, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1057332', 'n_tokens_mistral': 1041, 'n_tokens_neox': 990, 'n_words': 439}