[Israel.pm] Fwd: TelFOSS Soliciting a Talk about Automated SoftwareTesting
margol at beamartyr.net
Sun Sep 19 05:41:24 PDT 2010
Looks really cool... But why not under the Test:: namespace?
On 9/19/2010 2:38 PM, Levenglick Dov-RM07994 wrote:
> I recently wrote a OOP module that provides the ability to define a set
> of criteria that have to be covered for a test to pass.
> STP.pm - main module, congregates one or more scalar and/or arrays of
> STP::Union.pm - a module to allow bundling a bunch of STP objects to
> define a more comprehensive test
> STP::Scalar.pm - a single criterion that can be required or not
> STP::Array.pm - an array of scalar criteria
> Best Regards,
> Dov Levenglick
> SmartDSP OS Development Leader
> -----Original Message-----
> From: perl-bounces at perl.org.il [mailto:perl-bounces at perl.org.il] On
> Behalf Of Shlomi Fish
> Sent: Sunday, September 19, 2010 12:02
> To: Perl in Israel
> Subject: [Israel.pm] Fwd: TelFOSS Soliciting a Talk about Automated
> ---------- Forwarded Message ----------
> Subject: TelFOSS Soliciting a Talk about Automated Software Testing
> Date: Sunday 19 September 2010, 12:01:02
> From: Shlomi Fish <shlomif at iglu.org.il>
> To: "Linux-IL" <linux-il at cs.huji.ac.il>, Tel Aviv Open Source Club
> <telux at hamakor.org.il>
> Hi all,
> following on Sawyer's talk about version control, I've been thinking of
> another talk about a different software best practice: automated
> Since I'm a big practitioner and advocate of writing automated tests and
> driven development, the topic is close to my heart and I can prove of
> assistance in researching and preparing the material for the
> presentation. But
> I'm not a good speaker so I'm looking for someone to actually deliver
> Would anyone stand forward and can give a talk about it?
> Some useful items to cover:
> 1. The motivation for automated tests - providing a spec for the
> making sure bugs not resurface, preventing bugs, avoiding
> having confidence in the code, etc.
> 2. Short introduction to automated tests by writing tests for the
> classic "add
> two numbers" demo.
> 3. Overview of various approaches for testing frameworks - TestUnit, BDD
> (rSpec, etc.), Ruby's cucumber, perl's TAP, testml, etc.
> 4. Testing various kinds of domains:
> - Testing APIs.
> - Testing Command line apps.
> - Testing terminal (curses, etc.) applications.
> - Testing websites.
> - Testing GUI programs.
> 5. Various kinds of tests:
> - Unit tests.
> - Integration tests.
> - System tests.
> 6. Test coverage and beyond (see
> http://firstname.lastname@example.org/msg04588.html ).
> - Should you aspire for full test coverage?
> If you'd like to volunteer for that, please let us know at
> taux at cs.tau.ac.il .
> Shlomi Fish
More information about the Perl