veyepar: Make your testing Groovy

Author(s):	Paul King
Location	Tasman Hall B/C
Date	jan Mon 16	Days Raw Files
Start	21:15	First Raw Start	20:57
Duration	0:45:0	Offset	0:17:23
End	22:00	Last Raw End	22:27
Chapters	00:00 0:11:43 0:41:43
Total cuts_time	45 min.

http://linux.conf.au/schedule/presentation/157/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf Make_your_testing_Groovy.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	We tend to take enormous care these days making sure our production code is highly refactored and easily maintainable but what about our test code? This talk looks at the benefits of using an open source scripting language and utilising a high degree of automation rather than a vendor tool for unit, functional, acceptance, customer/BDD testing. The talk uses Apache Groovy as an example testing language but also considers other polyglot options. Groovy happens to be an excellent choice as a scripting/testing language for JVM users but the techniques described in the talk are applicable to other similar languages. Similarly, while specific forms of testing will be looked at, the techniques and lessons learned can be applied to other kinds of testing. Drivers and Runners discussed will include a selection from: Native Groovy, HttpBuilder, HtmlUnit, WebTest, Watij, Selenium, WebDriver, Tellurium, JWebUnit, JUnit, TestNG, Spock, EasyB, JBehave, Cucumber, Robot Framework, JMeter, ScalaCheck and FitNesse/Slim. Some techniques discussed will include all-pairs testing, model-driven testing, data-driven testing, constraint-programming based testing scenarios and code/test coverage. Participants in this talk should leave with some new insights into possible testing approaches and techniques which they can take back and incorporate in their own projects. markdown
Comment:	production notes