Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[perl #37887] Patch for tests.pod talking about testing parrot

0 views
Skip to first unread message

Ambs @ Cpan . Org

unread,
Dec 11, 2005, 2:24:26 PM12/11/05
to bugs-bi...@rt.perl.org
# New Ticket Created by am...@cpan.org
# Please include the string: [perl #37887]
# in the subject line of all future correspondence about this issue.
# <URL: https://rt.perl.org/rt3/Ticket/Display.html?id=37887 >


---
osname= linux
osvers= 2.4.26
arch= i486-linux
cc= cc
---
Flags:
category=docs
severity=none
ack=no
---

Index: docs/tests.pod
===================================================================
--- docs/tests.pod (revision 10449)
+++ docs/tests.pod (working copy)
@@ -5,12 +5,34 @@

docs/tests.pod - Testing Parrot

-=head1 A basic guide to writing tests for Parrot
+=head1 A basic guide to writing and running tests for Parrot

This is quick and dirty pointer to how tests for Parrot should be written. The
testing system is liable to change in the future, but tests written following
the guidelines below should be easy to port into a new test suite.

+=head1 How to test parrot
+
+The easy way to test parrot is running C<make test>. If you have
+updated your code recently and tests began failing, go for a C<make
+realclean> and recompile parrot before complaining.
+
+If you architecture suport JIT, you can test parrot JIT engine using
+C<make testj>. It works just like C<make test>, but uses the JIT
+engine when possible.
+
+=head2 Submitting smoke test results
+
+Parrot has a status page with smoke test results
+L<http://smoke.parrotcode.org/smoke.html>. You can supply new tests
+results just running C<make smoke>. It will run the same tests as
+C<make test> would, but creating a HTML table with the test
+results. At the end, it will try to upload the test results to the
+smoke server.
+
+It is also possible to run a smoke test on JIT. For that, try running
+C<env PARROT_ARGS=-j make smoke>.
+
=head1 How to write a test

New tests should be added to F<*.t> files. These test files can be found in the

---
Summary of my parrot 0.4.0 (r10446) configuration:
configdate='Sun Dec 11 17:43:04 2005'
Platform:
osname=linux, archname=i486-linux
jitcapable=1, jitarchname=i386-linux,
jitosname=LINUX, jitcpuarch=i386
execcapable=1
perl=/usr/bin/perl5.8.5
Compiler:
cc='cc', ccflags=' -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE',
Linker and Libraries:
ld='cc', ldflags=' -L/usr/local/lib',
cc_ldflags='',
libs='-lnsl -ldl -lm -lcrypt -lutil -lpthread -lrt -lgmp'
Dynamic Linking:
share_ext='.so', ld_share_flags='-shared -L/usr/local/lib -fPIC',
load_ext='.so', ld_load_flags='-shared -L/usr/local/lib -fPIC'
Types:
iv=long, intvalsize=4, intsize=4, opcode_t=long, opcode_t_size=4,
ptrsize=4, ptr_alignment=1 byteorder=1234,
nv=double, numvalsize=8, doublesize=8

---
Environment:
HOME LANG LANGUAGE LC_ALL LC_COLLATE LD_LIBRARY_PATH LOGDIR PATH PERL5_CPANPLUS_CONFIG SHELL

Chromatic

unread,
Dec 11, 2005, 7:32:28 PM12/11/05
to perl6-i...@perl.org, bugs-bi...@rt.perl.org
On Sun, 2005-12-11 at 11:24 -0800, via RT wrote:

> Index: docs/tests.pod

Thanks, applied as 10451, along with some other spelling corrections.

-- c

0 new messages