Automatic Functional Testing for Mac and Linux? 202
"For example, a vendor has a database interface, and wants to know how many times we can access a series of records, what the results show (are the right, blank, time out?), and how long it took for the search to take place during various times of the day, and so on. So we emulate one of their data entry people by logging onto the system, putting in some search parameter from a script, and then record what the text (or error message) was when it came back. Yes, we could connect directly to the SQL database without their front end, but it's the combination of their front end and the database we usually test. We have found many examples where were can connect raw, for instance, but the front end displays a timeout. We also test things like 'What happens if the user enters a colon or asterisk?' or 'What if the text entered in the box is over 256k?' Then we tell the vendor the results, and they hopefully fix them based on the data we gave them."
xnee (Score:3, Interesting)
you could always port it to OS X ... :-)
Robot and BeanShell (Score:2, Interesting)
Funny (Score:3, Interesting)
BTW, don't use xse, which is a wrapper for XSendEvent, if you roll your own. There are so many places where it just doesn't work, or doesn't work right, because the XSendEvent function just doesn't work reliably. I lost a lot of sleep over that before I gave up and just wrote xte.
Rational Software and Linux don't mix (Score:2, Interesting)
I'll tell you, it's a major hassle to develop a product for Linux while being forced to debug it on Solaris because that's the only place our debug tools will run. The first company to make decent Linux tools that are similar to Rational's will have my business. And Rational won't.
Re:Rational Software and Linux don't mix (Score:1, Interesting)
In this particular case: Acknowledging Linux as a platform, and thus the Linux software development process as a viable approach to software engineering, would prove some of their products useless.
SCNR.