From: Slick > > What do you guys do to practice? Do you practice one script > over and over again? Do you read differnt scripts and figure > out what is happening in each one? Do you think of ideas to > do things, then make the script for that?
It sounds to me like you are looking at Perl as a solution, but you haven't recognized a problem for it to solve. I suspect most of us have done it the other way around. My job is solving problems. For a long time the primary problem was lack of equipment to exercise servers, or the lack of space for that equipment. For example, I have written scripts that emulate a variety of cash registers and credit card terminals. These scripts open socket connections via TCP/IP and send messages that appear to be from real terminals. I can vary the frequency of messages, the number of terminals, the payment selection and a variety of other parameters. This allows me to do a wide range of functional tests, compatibility tests, performance tests, etc. all with a set of Perl scripts. I have also written emulations for devices that don't yet exist. By working from the protocol and message specifications I can test the interface to our transaction processors before the terminals can even be shipped by the vendors. My latest project is to use Test::Harness to drive Selenium Remote Control as it does functional and regression tests on web sites. The Selenium IDE captures the manual test as a macro and exports it to Perl. I then add additional validations, input some variables from the environment and put it into a test directory to add to the growing suite of tests. What problems do you need to solve? Bob McConnell -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
