Google (software) Test Automation Conference

[Michael Aivaliotis]

Today and tomorrow, there is a Google Test Automation Conference taking place in New York.

http://www.youtube.com/view_play_list?p=7D3E685B59779C16

It's unbelievable how quickly these videos have gone up.

QUOTE

Some of the most difficult challenges in creating great software are guaranteeing it works every time, for every customer, ensuring that it will scale well, and making it accessible to all users. Over the years, languages have become easier to work with, frameworks have become extensible for the creation of several products, and integrated development environments have made the software developer faster and more productive. But automation techniques, extensible testing frameworks, and easy-to-use test tools have lagged behind. While there are many good solutions for automated testing, there is plenty of room for innovation. The 2nd Annual Google Test Automation Conference (GTAC) in our New York office on August 23 and 24, 2007 addresses many of these topics. Our goal was to create a collegial atmosphere where participants could discuss challenges facing people on the cutting edge of test automation, evaluate solutions for meeting those challenges, and have a little fun.

Question, how do all of you perform testing on your LabVIEW VI's?

[i2dx]

QUOTE(Michael_Aivaliotis @ Aug 25 2007, 01:42 AM)

Question, how do all of you perform testing on your LabVIEW VI's?

hmm: that depends on the VI. I mostly work "bottom UP" and the testing is done during development. I have (developed) a tool for tracking the "review" status, which uses persistent tags and gives me the ability to view the "review status" of a VI hierarchy. I can mark a VI as "unchecked", "tested and OK", "needs review" ... etc

1. simple VI: enter the expected inputs, hit the run button and take a look at the outputs. If the result are as expected, I assume my code is correct and I test what happens, if the VI gets unexpected values. Maybe it should drop an error on unexpected inputs or deliver default values, etc ...

2. modules, e.g. a DAQmx functional global: I create a testing shell, where I can run that module "standalone" and watch the outputs, the timing behaviour, etc. If all looks fine, that VI gets the "approved mark". I also test "more complicated algorithms" within a test shell ...

3. integrating VIs: I Put all my modules, simple VIs, etc in and make the "big bang" test. Mostly this takes a little bit more time, to debug/test those VIs

4. Main VI: the Main VI is under constant testing, because I use it as the test shell for the simple VIs, modules, etc. It's probably the most tested VI in my whole application.

[Chris Davis]

QUOTE(Michael_Aivaliotis @ Aug 24 2007, 06:42 PM)

Question, how do all of you perform testing on your LabVIEW VI's?

For my whole applications I've started using AutoIt to script user functions. I'm still working on a test suite for the whole VI hierarchy.