in reply to Testing with sensitive information

I'm the author of Finance::Banking::Postbank_de, and in my module I test via two kinds:

I consider interactive test suites as very bad form, especially as I'm running CPAN smoke tests from time to time...

Replies are listed 'Best First'.
Re^2: Testing with sensitive information
by rpanman (Scribe) on Jul 09, 2007 at 18:42 UTC
    Thanks Corion.

    Sadly there's active demo (just a load of flash), so that options out :-(

    I like the thought of at least being able to check the parsing is correct using file though, I'll definitely include that.

    No worries about the interactive tests - I had a feeling there was bad karma associated and now it has been confirmed I will steer well away :-)
Re^2: Testing with sensitive information
by Limbic~Region (Chancellor) on Jul 10, 2007 at 13:24 UTC
    Corion,
    I consider it bad form for any test suite to automatically assume it is ok to contact the internet let alone phone home. I also see the interactive is bad argument. The comprimise in my opinion is to prompt the user for input with a sane timeout automatically defaulting to "no".

    With that said, I was thinking that it might be good to have continuously updating saved HTML files. I really haven't thought this through but here is the general idea. You have code that periodically logs in and pulls down sample files that are scrubbed (if no demo account available). These files are then place in a public facing location that the test suite points to if the user decides live tests are preferred.

    Cheers - L~R