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 D
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 to
-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 V
g and itching and oi.
Yeah I know...
--
Leif Eriksen
Snr Developer
http://www.hpa.com.au/
phone: +61 3 9217 5545
email: [EMAIL PROTECTED]
?
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]
Plus 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]
n when it does happen is up 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]
ery lightweight unless test.This seems OK to me, but I know opinions on
this cover a wide spectrum.
The only 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]
the resulting data is the same.
Would anyone be in doubt that it should pass?
I'm guessing that is_deeply tests for 'semantic equivalence', not
'syntactic equivalence' - or is that a whole unopen can of worms?
--
Leif Eriksen
Snr Developer
http://www.hpa.com.au/
phone: +61 3 9217 5545
email: [EMAIL PROTECTED]
hnson may have this written up 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.
--
Lei
[EMAIL PROTECTED] wrote:
Leif Eriksen wrote:
Can this be right ?
--- -- -- -- --
-- --
File stmt branch condsub
time total
situation.
--
Leif Eriksen
Snr Developer
http://www.hpa.com.au/
phone: +61 3 9217 5545
email: [EMAIL PROTECTED]
ROY created new reference to dead object 'DBI::dr' during global
destruction.
Now I dont know where to go from here - have I uncovered a bug in DBI ?
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]
lock secs ( 0.33 cusr + 0.02 csys = 0.35 CPU)
I'm guessing this is the right forum to post this too - unless I should
go right ahead and file with RT...?
--
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]
I'd guess it is because you are seeing the output of the code after it
has been compiled-then-decompiled - it is compiled so it can run and
coverage statistics can be collected, then it is decompiled to relate
coverage stats to code lines. Now there are many ways to write code that
compiles to
ut to no avail.
Any pointers as to how I can progress solving this ? Do you need the
core dump ?
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
[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 but not
-- -- -- ------
------
++
[EMAIL PROTECTED] src]$ perl -MTest::More -e 'print Test::More->VERSION()'
0.47
--
Leif Eriksen
Snr Developer
http://www.hpa.com.au/
phone: +61 3 9217 5545
email: [EMAIL PROTECTED]
he exercise - 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]
#x27; runs over a long period (in this case weeks)). We'll
never know now.
Morale - 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)
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 not
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
e some interaction with Test::More::use_ok that is stopping D::C
instrumenting the module correctly ?
Is there some other switch in D::C I need to use ?
Leif Eriksen
k 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 20
27 matches
Mail list logo