Step 3 is done. The result is that the orphans have dropped from 63% to 53%.
So, I now start step 4:
STEP4: Boolean Matches Man Page Name with Post Text
I will take the remaining man pages without any similar threads and repeat step three but matching the name of the man page (only the query, for example 'sshd') against the page text for each post and get the threadid from the post, and order the matches by the number of times the thread was thanked by users, and keep up to 15 matches, as before.
We will see how many man page orphans find thread relatives in this step 4 manner.
Running...... looks like this query and update will take around a week or so, as not to overload the server.
.and so far, it looks like the orphans will be only reduced by a relatively small amount (less than 15% of total remaining orphans, I guess... let's see)
Hello ,
I just installed openssh in my system . I actually tried to man sshd but it says no entry , though there is a man directory in the installation which have the man pages for sshd .
Can anyone tell me how should i install these man pages .
DP (2 Replies)
Hi,
I've written now a man pages, but I don't knwo how to get 'man' to view them. Where have I to put this files, which directories are allowed??
THX Bensky (3 Replies)
When reading man pages, I notice that sometimes commands are follwed by a number enclosed in parenthesis. such as:
mkdir calls the mkdir(2) system call.
What exactly does this mean? (4 Replies)
can anybody explain me how to read unix
man pages?
for example when i want to get information about ps command
man ps gives me this output:
***********************************
Reformatting page. Please wait... completed
ps(1) ... (2 Replies)
Hi,
I want to install man pages package from solaris 10.
Solaris 10 has already been installed on my servor but I have to add the man pages packages. I search for a long time on internet this package but I didn't find a compatible one... So I downloaded Solaris 10 from Sun site to get this... (1 Reply)
Hello sir,
I am using FEDORA 9.
I wanted to know why do we have ".1" extension in the archives of man pages. I know we are giving format.
I want to know the importance or purpose of this format.
Can you please tell me :confused: (2 Replies)
Hi everyone,
I have a small query, in solaris the man pages get displayed on half of the terminal , can i get a full terminal or full screen display ?:) (2 Replies)
Can anyone supply me with the man pages for:
omnidatalist
omnibarlist
omnisap.exe
I prefer the source man pages in nroff format.
A clue about the software bundles which supply these man pages is fine as well.
OS: HP-UX
TIA (11 Replies)
what command should i use for displaying the manual pages for the socket, read and connect system calls? (1 Reply)
Discussion started by: Nabeel Nazir
1 Replies
LEARN ABOUT DEBIAN
test::bdd::cucumber::manual::steps
Test::BDD::Cucumber::Manual::Steps(3pm) User Contributed Perl Documentation Test::BDD::Cucumber::Manual::Steps(3pm)NAME
Test::BDD::Cucumber::Manual::Steps - How to write Step Definitions
VERSION
version 0.11
INTRODUCTION
The 'code' part of a Cucumber test-suite are the Step Definition files which match steps, and execute code based on them. This document
aims to give you a quick overview of those.
STARTING OFF
Most of your step files will want to start something like:
#!perl
use strict;
use warnings;
use Test::More;
use Test::BDD::Cucumber::StepFile;
use Method::Signatures;
The fake shebang line gives some hints to syntax highlighters, and "use strict;" and "use warnings;" are hopefully fairly standard at this
point.
Most of my Step Definition files make use of Test::More, but you can use any Test::Builder based testing module. Your step will pass its
pass or fail status back to its harness via Test::Builder - each step is run as if it were its own tiny test file, with its own localized
Test::Builder object.
Test::BDD::Cucumber::StepFile gives us the functions "Given()", "When()", "Then()" and "Step()". These pass the step definitions to the
class loading the step definitions, and specify which Step Verb should be used - "Step()" matches any.
Method::Signatures allows us to use a small amount of syntactic sugar for the step definitions, and gives us the "func()" keyword you'll
see in a minute.
STEP DEFINITIONS
Given qr/I have (d+)/, func ($c) {
$c->stash->{'scenario'}->{'count'} += $1;
}
When "The count is an integer", func ($c) {
$c->stash->{'scenario'}->{'count'} =
int( $c->stash->{'scenario'}->{'count'} );
}
Then qr/The count should be (d+)/, func ($c) {
is( $c->stash->{'scenario'}->{'count'}, $c->matches->[0], "Count matches" );
}
Each of the exported verb functions accept a regular expression (or a string that's used as one), and a coderef. The coderef is passed a
single argument, the Test::BDD::Cucumber::StepContext object. To make this a little prettier, we use Method::Signatures's "func()" keyword
so we're not continually typing: "sub { my $c = shift; ... ".
We will evaluate the regex immediately before we execute the coderef, so you can use $1, $2, $etc, although these are also available via
the StepContext.
NEXT STEPS
How step files are loaded is discussed in Test::BDD::Cucumber::Manual::Architecture, but isn't of much interest. Of far more interest
should be seeing what you have available in Test::BDD::Cucumber::StepContext...
AUTHOR
Peter Sergeant "pete@clueball.com"
LICENSE
Copyright 2011, Peter Sergeant; Licensed under the same terms as Perl
perl v5.14.2 2012-05-20 Test::BDD::Cucumber::Manual::Steps(3pm)