This is an automated email from the git hooks/post-receive script. intrigeri pushed a commit to branch master in repository libtest-bdd-cucumber-perl.
commit ba690a3bd3137a7662abebe21a7be489a6080b0c Author: poum <p...@cpan.org> Date: Sat Dec 27 18:53:44 2014 +0100 Update Tutorial.pod fix 2 typos --- lib/Test/BDD/Cucumber/Manual/Tutorial.pod | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/Test/BDD/Cucumber/Manual/Tutorial.pod b/lib/Test/BDD/Cucumber/Manual/Tutorial.pod index 197ef96..8f66be7 100644 --- a/lib/Test/BDD/Cucumber/Manual/Tutorial.pod +++ b/lib/Test/BDD/Cucumber/Manual/Tutorial.pod @@ -93,7 +93,7 @@ we look for a C<features/> directory, and search for step definitions files (matched by C<*_steps.pl>) and feature files (matched by C<*.feature>). The step matchers (the code that starts with C<Given>, C<When> and C<Then>) are -all loaded, and then we execture the feature files one by one. Let's step +all loaded, and then we execute the feature files one by one. Let's step through the feature file, and look at how it matches up to the step definitions file. @@ -168,7 +168,7 @@ I<stash> for other steps to use. There are three stashes documented in L<Test::Builder::StepContext>, C<feature>, C<scenario> and C<step>. As you might expect, C<feature> is available to all step definitions that are being executed as part of a feature, and C<scenario> is available to all steps that are being -executed as part of a feature. +executed as part of a scenario. The context is the single argument that gets passed to each step, and it contains evertything that step should need to execute. We'll be looking at some -- Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-perl/packages/libtest-bdd-cucumber-perl.git _______________________________________________ Pkg-perl-cvs-commits mailing list Pkgfirstname.lastname@example.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-perl-cvs-commits