Posts about technology and arts.
Here are the slides used in TDC 2011 - Goiânia. The same slides were used in the Testing and in the Java tracks, though with different titles. The only difference is the demo, that had more details in the latter track.
Have a great Halloween :-) Cheers
"Test Double is a generic term for any case where you replace a production object for testing purposes" . There are different types of Test Doubles: Dummy, Fake, Stubs, Spies and Mocks. In this post we will see a practical example of adding stubs to TestLink Java API.
Stubs are objects that return canned answers to calls during tests . This is useful specially when you have a system that communicates with different resources such as databases, web services, XML-RPC services and so on.
TestLink Java API is a small Java project created to act as an interface between TestLink XML-RPC API and a client program written in Java.
Yesterday I finally managed to build Jenkins using Eclipse and m2e plug-in. With Eclipse Indigo release came a new version of the Maven plug-in for Eclipse (former M2Eclipse), m2e. Since I started using Eclipse Indigo and this new plug-in I hadn't been able to build Jenkins in Eclipse anymore.
I've been having a terrible fever and thought that it would be a good thing to stop playing Minecraft for a while and find a way to build Jenkins in Eclipse + m2e :-).
The first thing I've noticed were the messages regarding the execution of some Maven plug-ins in the project life cycle. m2e delegates the execution of Maven plug-ins to an external executor. As not all Maven plug-ins have an existing executor for m2e you will receive a message similar to "Plugin execution not covered by lifecycle configuration: ...".
Unfortunately I missed JCertif last weekend. My visa was in Brazzaville but I couldn't board in a flight from Johannesburg to Congo without it. Max Bonbhel kindly tried to fax me the visa, but the last flight to Congo closed and I had to come back to Brazil sooner. :-(
Here is the slides that I was going to use there. Hope you take some time to read about TAP, SubUnit and other test protocols. There are two special points to pay attention to, one single format and extensibility.
With a single format for your test results, you won't need to write many different parsers, one for each distinct format. Extensibility refers to the fact that using formats like xUnit (like JUnit) or TestNG XML you are limited to the XML schema.
Many projects are aiming automation in different levels. Executing automated tests can lead to situations where you need to have information like the database used, JDK version, screen shots taken during some tests, exception stack traces, etc. TAP and SubUnit provide manners to extend your test result and inform to a test consumer (the tool that reads your test output) about such information.
Last weekend I attended TDC (The Developers Conference) 2011 in Florianópolis, in the south of Brazil. It was my first time in Florianópolis, but the weather was cloudy and cold, so I couldn’t check out one of the prettiest cities in Brazil :-( Bummer.
Putting the weather aside, TDC was great! Basically, there were many nice, easy-going people gathering together to talk about subjects like Java, SOA, Arduino, Testing, Agile and more. I had the chance to talk with skilled and experienced people, see different talks and catch up Guilherme Motta (@gfcmotta) from ThoughtWorks, who I have met in Porto Alegre in the beginning of this year. He gave an interesting talk about crowd testing using games as example, but varying with applications in different areas too.