Thursday, 30 September 2010

Making Git working with Hudson

Once again I've started building CI infrastructure for another test automation project. Everything was clear and obvious. Actually, just another "toolset zoo" was involved. There were: PHPUnit, Selenium-RC, PHPDocumentor, Ant, Hudson and Git. Well, everything was obvious and clear. Ant makes all the stuff to prepare all resources and run single command. Hudson was supposed to download resources from Git and run the build.

Wednesday, 11 August 2010

Behavior-driven development introduction

What is the behavior-driven development approach. It's just another approach to build automated tests, like decomposition, keyword-driven, data-driven, object-based. Key feature of this approach is that each action is represented with some specific sentence describing actions to be done. And it's usually natural-language instruction. So, we actually describe some behaviour of AUT after some actions with it. So, at the highest level test is represented something like that:

Tuesday, 27 July 2010

Development skills for test automation

The more time I work with test automation the more times I'm assured that there's nothing to do in this area without development vision of the overall solution. Where it is essential?

Tuesday, 20 July 2010

SOA Testing: what should we know about it

It's obvoius that testing is not limited by clicks on application GUI. All we have as a part of the product should be tested. And sometimes we can interact on non-GUI level. In particular it key feature of services testing.

Monday, 10 May 2010

Test Automation infrastructure in Java

In general, it's good when you set up your automated testing using the same programming language as the application under test is written on. It provides the integration with unit tests, integration tests which are typically interact on code level.

Another good thing is that all the infrastructure and approaches generally used for development are applicable for test automation.

Wednesday, 5 May 2010

Choose proper test automation tool

Proper automation starts with proper approach selection and proper processes definition. But these are just first steps which require further correlations and updates as long as automation grows. And in most cases these updates/corellations are related to the specifics of used toolset. So, the more project specifics your toolset fits the less corrective actions you should make in your automation processes.

What should we do for proper test automation tools selection?