From 603c773044d75a486034be8f56359f4b11450569 Mon Sep 17 00:00:00 2001 From: Paul Cochrane Date: Thu, 25 Jun 2015 13:33:31 +0200 Subject: [PATCH 1/2] Fix minor typos in POD --- lib/Test/SQL/Translator.pm | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/lib/Test/SQL/Translator.pm b/lib/Test/SQL/Translator.pm index 1802dcf73..e1d1e4a43 100644 --- a/lib/Test/SQL/Translator.pm +++ b/lib/Test/SQL/Translator.pm @@ -532,7 +532,7 @@ __END__ ], }); -=head1 DESCSIPTION +=head1 DESCRIPTION Provides a set of Test::More tests for Schema objects. Testing a parsed schema is then as easy as writing a perl data structure describing how you @@ -545,14 +545,14 @@ tested to make sure they are still at their default value. This is a useful check that you your parser hasn't accidentally set schema values you didn't expect it to. -For an example of the output run the t/16xml-parser.t test. +For an example of the output run the C test. =head1 Tests All the tests take a first arg of the schema object to test, followed by a hash ref describing how you expect that object to look (you only need give the attributes you expect to have changed from the default). -The 3rd arg is an optional test name to pre-pend to all the generated test +The 3rd arg is an optional test name to prepend to all the generated test names. =head2 table_ok @@ -613,7 +613,7 @@ We could add skip_* items to the test hashes to allow per test skips. e.g. =item yaml test specs -Maybe have the test subs also accept yaml for the test hash ref as its a much +Maybe have the test subs also accept yaml for the test hash ref as it is much nicer for writing big data structures. We can then define tests as in input schema file and test yaml file to compare it against. From 1fb1d4b00b5dafc0660f32ed773fe5c7b59f1a9a Mon Sep 17 00:00:00 2001 From: Paul Cochrane Date: Thu, 25 Jun 2015 13:33:47 +0200 Subject: [PATCH 2/2] Add C<> formatting to code-like text elements This makes things which are basically code stand out as being such. --- lib/Test/SQL/Translator.pm | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/lib/Test/SQL/Translator.pm b/lib/Test/SQL/Translator.pm index e1d1e4a43..234035076 100644 --- a/lib/Test/SQL/Translator.pm +++ b/lib/Test/SQL/Translator.pm @@ -536,7 +536,7 @@ __END__ Provides a set of Test::More tests for Schema objects. Testing a parsed schema is then as easy as writing a perl data structure describing how you -expect the schema to look. Also provides maybe_plan for conditionally running +expect the schema to look. Also provides C for conditionally running tests based on their dependencies. The data structures given to the test subs don't have to include all the @@ -600,14 +600,14 @@ maybe_plan =item Test Count Constants -Constants to give the number of tests each *_ok sub uses. e.g. How many tests -does field_ok run? Can then use these to set up the test plan easily. +Constants to give the number of tests each C<*_ok> sub uses. e.g. How many tests +does C run? Can then use these to set up the test plan easily. =item Test skipping As the test subs wrap up lots of tests in one call you can't skip individual tests only whole sets e.g. a whole table or field. -We could add skip_* items to the test hashes to allow per test skips. e.g. +We could add C items to the test hashes to allow per test skips. e.g. skip_is_primary_key => "Need to fix primary key parsing.",