-Original Message-
From: Aristotle Pagaltzis [mailto:[EMAIL PROTECTED]
that's the power of TAP.
...
Wasn't that a hit for Huy Lewis years ago ?...
Another option is to use IPC::System::Simple.
The driver script is a neat idea, I used this variation for testing my
harness wrapped around my Utils C library
Say I had C code in a Utils library, one source file which might have
this code
Utils.c
/**
* internal function
*/
static int
Ruby has a nice description at
http://manuals.rubyonrails.com/read/chapter/26
To quote
Fixtures is a fancy word for ‘sample data’. Fixtures allow you to populate
your testing database with predefined data before your tests run.
Think about how something like Test::MockDBI's set_retval_arry()
I know this is iseveral days old , but we in Oz get the weekend before almost
anyone else so bear with me.
When dealing with a BoM (Ball of Mud), there is a fundamental collision of two
concerns here.
1. To test the code, you need to change it.
2. Before changing the code, you should test it.
You don’t have to use objects to get the same end effects as mocking objects.
Mocking is a technique for OO code to achieve the following aim -
the code under test should not be changed to test it
The code _should_ (I'd prefer _must_ but lets not get into absolutes just yet)
NOT be
Thanx for that, I'll get onto it ASAP.
And your absolutely right, I should have lowered the VERSION.pm into a safer
namespace.
Leif
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 17 October 2006 5:05 PM
To: Leif Eriksen
Cc: perl-qa@perl.org
Subject
Thanx, I'll update.
This was a hangover from an earlier prototype, where we actually made calls to
perltidy itself, rather than the more flexible Perl::Tidy API. As such we
didn’t detect a missing perltidy install until runtime. The current code makes
no use of the perltidy program, only the
identity.
Leif Eriksen
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.408 / Virus Database: 268.13.4/477 - Release Date: 16/10/2006
**
IMPORTANT
The contents of this e-mail and its
is that coding standards
are often lumped into the 'QA'-bucket, so the QA mail-list seems
most appropriate. I hope to announce this more widely (perl monks, CPAN
maybe) in a few weeks.
Thanx for your time,
Leif Eriksen
--
No virus found in this outgoing message.
Checked by AVG Free Edition
Of course it had to be wrong didnt it -
http://sourceforge.net/projects/tidyview/
http://sourceforge.net/projects/tidyview/ if the https isnt working
for you.
Leif Eriksen
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.12.3/447
.
So I'm going for a little more feedback and stability before posting a release
to CPAN - maybe I'm being too precious, I don’t know.
Leif
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, 14 September 2006 10:45 PM
To: Leif Eriksen
Cc: perl-qa@perl.org
To: Leif Eriksen
Cc: perl-qa@perl.org
Subject: Re: TidyView - preview your perltidy options
Please excuse the stupid question, but is there any chance this could use Wx
instead of Tk, since Wx installs from CPAN cleanly everywhere now (I think) and
Tk doesn't seem to install properly.
But then I
, to
aid those who' like to try to develope a test-dashboard app, and who
need to know how many scripts are going to run.
Something like $HARNESS_SCRIPTS=count_scripts make test
This could have T::H set an envvar like HARNESS_SCRIPTS_FOUND, or
somehow communicate back its findings.
Leif Eriksen
of information. Having a test A of B in script X of Y is
nice to if you have a plan.
L
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 9 August 2006 5:06 AM
To: perl-qa@perl.org
Cc: Leif Eriksen
Subject: Re: Idea for updating the plan
On Tuesday 08
I'm confused - was this a hackathon, or Iron Chef ?
L
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, 3 August 2006 11:57 PM
To: perl-qa@perl.org
Subject: Devel::Cover hackathon
On Tuesday the first [insert desired time period here] Devel::Cover
I know we've moved on, but I'm in a completely different time zone, so please
understand...
I, like demerphq, also think that coming up with a name for each and every test
is a good idea.
It shouldn’t be hard to think of a description for each and every test.
Just note down why you wrote that
I have done the two programmers, one terminal approach advocated by
Beck for XP developments (not just TDD) and it worked well. We delivered
on time with all features present and correct (where correct means the
application passed the customers Business Acceptance Tests - first
time).
I should
I would classify what Adam does as robustness testing.
Often the first release can be classified as working, in a perfect world.
Adam lives in a World of Evil.
Let me expand. For most of us (this means Not Adam), we work during the Day
and rest at Night. We don't call it Day and Not Day,
Well it depends on what your actually studying...
1. You have written the code to implement a network bridge, and you want
to test
i. the codes correctness
ii. its ability to handle packets correctly for various
configurations and load
2. You have a network bridge, and you want
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
That said, now that TAP is well documented (yay), there's nothing wrong
with writing other harnesses.
Just as a comment, I used the TAP doco to write a VB console app for
testing the non-GUI (library) part of a VB
this seem like a
reasonable idea ?
Against it is the significant inertia the current .t regime enjoys, but
it seems an interesting idea.
--
Leif Eriksen
Snr Developer
http://www.hpa.com.au/
phone: +61 3 9217 5545
email: [EMAIL PROTECTED]
and itching and oi.
Yeah I know...
--
Leif Eriksen
Snr Developer
http://www.hpa.com.au/
phone: +61 3 9217 5545
email: [EMAIL PROTECTED]
donuts and dancing girls.
Donuts ? Did you say donuts !? What kind ?
--
Leif Eriksen
Snr Developer
http://www.hpa.com.au/
phone: +61 3 9217 5545
email: [EMAIL PROTECTED]
caveat is in regards to those psycho's who like to bless into
the '0' namespaceI believe '' and undef result in blessing into main::
--
Leif Eriksen
Snr Developer
http://www.hpa.com.au/
phone: +61 3 9217 5545
email: [EMAIL PROTECTED]
to the developer. Getting 100%
coverage via D::C is another motivation.
--
Leif Eriksen
Snr Developer
http://www.hpa.com.au/
phone: +61 3 9217 5545
email: [EMAIL PROTECTED]
situation.
--
Leif Eriksen
Snr Developer
http://www.hpa.com.au/
phone: +61 3 9217 5545
email: [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Leif Eriksen wrote:
Can this be right ?
snip
--- -- -- -- --
-- --
File stmt branch condsub
time total
somewhere, but, if not, I should
really write something up about this since I've used it to determine Perl's
test coverage.
Generating coverage tests for XS code - why are my hands shaking ?
Thanks - I'm sure it wil be needed one way or the other.
--
Leif Eriksen
Snr Developer
http://www.hpa.com.au
?
Or is it elsewhere ?
How do I interprete the stat and wstat values form D::C ?
Do I need to compile a debug version of perl and step through under the
debugger with that ?
--
Leif Eriksen
Snr Developer
http://www.hpa.com.au/
phone: +61 3 9217 5545
email: [EMAIL PROTECTED]
[, globals[, locals]])
...
This launches the debugger mid-script - nice. I've heard there has been
some talk/suggertions of doing this in Perl 6
--
Leif Eriksen
Snr Developer
http://www.hpa.com.au/
phone: +61 3 9217 5545
email: [EMAIL PROTECTED]
?
Platform info
[EMAIL PROTECTED] perl]$ uname -a
Linux itdevtst 2.4.20-31.9 #1 Tue Apr 13 18:04:23 EDT 2004 i686 i686
i386 GNU/Linux
[EMAIL PROTECTED] perl]$ perl -v
This is perl, v5.8.0 built for i386-linux-thread-multi
(with 1 registered patch, see perl -V for more detail)
--
Leif Eriksen
[EMAIL PROTECTED] wrote:
Leif Eriksen wrote:
Hi,
I am doing some testing under Devel::Cover, and get some weird
results sometimes. What should I be looking at in my code or test
cases that is provoking this discrepancy?
Look for code that sneaks past perl under normal circumstances
- the bugs you
find when you think 'its got 98% coverage, there cant possibly be any
bugs left...oh, look'
--
Leif Eriksen
Snr Developer
http://www.hpa.com.au/
phone: +61 3 9217 5545
email: [EMAIL PROTECTED]
Paul Johnson wrote:
On Sat, Nov 13, 2004 at 12:33:01PM +1100, Leif Eriksen wrote:
First, thanx so very much for responding so quickly...
That was just to make up for the short delay here, and the much longer
delay to your last mail to me ;-)
Hey, we had a weekend in between, and its
- clean up and try from scratch before hitting the 'emergency
email support' button.
Thanx so much for your patience Paul - if your ever in Melbourne, I owe
you a few shouts at the bar - I recommend a James Boags.
Leif Eriksen
aka Mr Testing SmartyPants (you can tell I'm please with myself cant you)
First, thanx so very much for responding so quickly...
Paul Johnson wrote:
On Sat, Nov 13, 2004 at 12:46:16AM +1100, Leif Eriksen wrote:
Even though Test::More is reporting (via make test) that every test
Could you try putting the use_ok inside a BEGIN block, as Test::More
recommends?
OK
that is stopping D::C
instrumenting the module correctly ?
Is there some other switch in D::C I need to use ?
Leif Eriksen
the code for a CHECK block? Do I have
to trace the dynamically generated command maually ?
--
Leif Eriksen
Snr Developer
HPA Pty Ltd
ph +61 3 9217 5545
diff -Naur test_output/cover/special_blocks.5.008
test_output/cover_new/special_blocks.5.008
--- test_output/cover/special_blocks.5.008 2004-10
38 matches
Mail list logo
