10-20-2011
Of course the error is the same; the code hasn't changed after all...
Unlike an IDE though, a shell does not have total control of its environment, meaning, debugging could cause radically different behavior (input meant for the script ending up in the 'wait till enter for next line' function, etc.) You're trying to build an IDE out of a shell.
Hmm. Thinking on it.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
HI
I am new to unix and need to install sco unix on a new server - could anybody help me with the steps I need to take - the hd is a 9gb scsi drive (pretty old machine)
Thanks (1 Reply)
Discussion started by: porikamu
1 Replies
2. UNIX for Dummies Questions & Answers
I am new to unix and server at my job crashed due to hardware problem. I'm now opted to install sco unix on a new server - could anybody help me with the steps I need to take (pretty old machine)
Thanks & Regards
Nancy :( (0 Replies)
Discussion started by: nensee7
0 Replies
3. Shell Programming and Scripting
Hi all,
The following script is fine when I work via command line
m=1
c=0
while
do
echo $m
gnokii --getsms IN $m > out.txt;
m=`expr $m + 1`;
cat out.txt >> message_log;
############
read first crap< <(sed -n '/Text:/{n;p;}' out.txt);
read message< <(sed -n '/Text:/{n;p;}'... (2 Replies)
Discussion started by: whamchaxed
2 Replies
4. UNIX for Dummies Questions & Answers
Hello all
i was searching the net for simple but effective tutorial to show me how debug c++ in emacs with not much luck.
im not new to unix but new to emacs , i looking for tutorial that
shows how to debug ( if possible ) c++ programs .
LIike IDE suppose to , break points step in/out variable... (0 Replies)
Discussion started by: umen
0 Replies
5. Solaris
Hi all.
This may be a stupid question but here goes:
I lost a disk on my Sun-Fire 480-r and want to replace it. I don't care about the data, I just need to get a new disk in.
Can anyone supply me with step by step procedure please. I am not an expert by any means and it is a dev box so I... (1 Reply)
Discussion started by: jamie_collins
1 Replies
6. Linux
Thank all of you.
May you explain step by step where and how I will add pseudo code
Note : I have Linux 2.6.24-26-server on x86_64
dears kindly help me (3 Replies)
Discussion started by: nonowa
3 Replies
7. What is on Your Mind?
FYI,
I'm slowly removing a lot of the bold font-styles from titles of discussions, forum titles, etc
I'm not removing bold for the entire site because we do need bold from time to time, especially in posts and sometimes in other places.
However, the original forum style had way too much... (3 Replies)
Discussion started by: Neo
3 Replies
LEARN ABOUT DEBIAN
test::bdd::cucumber::executor
Test::BDD::Cucumber::Executor(3pm) User Contributed Perl Documentation Test::BDD::Cucumber::Executor(3pm)
NAME
Test::BDD::Cucumber::Executor - Run through Feature and Harness objects
VERSION
version 0.11
DESCRIPTION
The Executor runs through Features, matching up the Step Lines with Step Definitions, and reporting on progress through the passed-in
harness.
METHODS
steps
add_steps
The attributes "steps" is a hashref of arrayrefs, storing steps by their Verb. "add_steps()" takes step definitions of the item list form:
(
[ Given => qr//, sub {} ],
),
and populates "steps" with them.
execute
Execute accepts a feature object, a harness object, and an optional Test::BDD::Cucumber::TagSpec object and for each scenario in the
feature which meets the tag requirements (or all of them, if you haven't specified one), runs "execute_scenario".
execute_scenario
Accepts a hashref of options, and executes each step in a scenario. Options:
"feature" - A Test::BDD::Cucumber::Model::Feature object
"feature_stash" - A hashref that should live the lifetime of feature execution
"harness" - A Test::BDD::Cucumber::Harness subclass object
"scenario" - A Test::BDD::Cucumber::Model::Scenario object
"background_obj" - An optional Test::BDD::Cucumber::Model::Scenario object representing the Background
"scenario_stash" - We'll create a new scenario stash unless you've posted one in. This is used exclusively for giving Background sections
access to the same stash as the scenario they're running before.
For each step, a Test::BDD::Cucumber::StepContext object is created, and passed to "dispatch()". Nothing is returned - everything is played
back through the Harness interface.
add_placeholders
Accepts a text string and a hashref, and replaces " <placeholders" > with the values in the hashref, returning a string.
dispatch
Accepts a Test::BDD::Cucumber::StepContext object, and searches through the steps that have been added to the executor object, executing
against the first matching one.
You can also pass in a boolean 'short-circuit' flag if the Scenario's remaining steps should be skipped.
skip_step
Accepts a step-context, a result-type, and a textual reason, exercises the Harness's step start and step_done methods, and returns a
skipped-test result.
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::Executor(3pm)