Skills Matter

Subscribe to our Erlang Factory newsletter to receive the latest updates and news

Thomas Arts
QuviQ AB

Dr. Thomas Arts is the co-founder and CTO of Quviq, a small company that produced Quick Check, as testing tool for Erlang. Thomas has over 30 publications in various industry journals and has experience refereeing conferences and workshops. He has successfully introduced some new technologies to the industry, the latest being QuickCheck, a tool for property based testing and aims to support test driven development. Thomas is also an associate professor at the IT University of Göteborg in the area of Software Engineering and Management. He holds a PhD in computer science and after his PhD has been employed at the Ericsson Computer Science Lab (Where they invented Erlang), where he worked on program verification and the development of the Erlang programming language. He has also worked in the broad spectrum theoretical computer science, formal methods and industrial case-study research, mainly applying all kind of techniques to systems written in Erlang.

Thomas Arts is Giving the Following Talks
QuickCheck Tutorial: Using QuickCheck to Test Erlang Programs

QuickCheck is an automated testing tool which addresses these problems by generating test cases from a concise specification (so that many more cases can be tested), and simplifying failing cases to a minimal example on a test failure (so that fault diagnosis is quick and easy). QuickCheck enables developers to dramatically improve test coverage, and find obscure errors at an earlier stage, lowering costs and improving quality as a result.

In this tutorial, John Hughes and Thomas Arts will use examples to show how developers write QuickCheck specifications—which are actually Erlang programs using the QuickCheck API—and use them to test code written in Erlang or other programming languages. We will show how QuickCheck’s shrinking finds tiny examples that provoke errors, making the step from observing a bug to diagnosing it very short indeed, and we will show how property driven development can produce code that is solid from the word go.