testing conferences in Europe 2009

EuroSPI Conference September 2-4,2009 Madrid, Spain
Conquest 2009 September 16-18, 2009 Nuremberg, Germany
Software & Systems Quality Conferences October 5, 2009 London, UK
Agile Testing Days October 12-14, 2009 Berlin, Germany
expo:QA October 27-29, 2009 Madrid, Spain
EuroSTAR Nov 30 - Dec 03, 2009 Stockholm, Sweden

Comments

Roman said…
These times I think it's hard to get there...

Best Regards,
Roman
12:04 AM
ugne said…
Because of high costs? I guess it depends on a country and on a company you work at. On the whole, I do not think there are many testers from Lithuania attending such conferences
11:49 PM
Post a Comment

Popular posts from this blog

Retrofitting testing - what is it?

It is nice to meet new terms and keywords relating testing. This morning I got a question how I am planning to do 'regression as part of Code Retrofitting testing'.   Have never heard of retrofitting testing before, so did some googling. The best explanation I found was on blog  http://blog.intrepidtesting.com/retrofit-vs-retest-vs-regression-testing/    article " Retrofit vs Retest vs Regression Testing " : Retrofit testing  is carried to to test that a change in functionality is correctly implemented for existing entities. Retrofit testing is more commonly carried out when you have an incremental project, or change requests. If the time available to test is tight, retesting and retrofit testing usually takes a higher priority over regression testing Colleague's comment while trying to help me: " if I googled it correctly then they expect you to perform regression for legacy system where your changes were introduced. In this way I would ...
Read more

tester's day!

Happy testers day! Top 24 replies by programmers when their programs don't work: 24. "It works fine on MY computer" 23. "Who did you login as ?" 22. "It's a feature" 21. "It's WAD (Working As Designed)" 20. "That's weird..." 19. "It's never done that before." 18. "It worked yesterday." 17. "How is that possible?" 16. "It must be a hardware problem." 15. "What did you type in wrong to get it to crash?" 14. "There is something funky in your data." 13. "I haven't touched that module in weeks!" 12. "You must have the wrong version." 11. "It's just some unlucky coincidence." 10. "I can't test everything!" 9. "THIS can't be the source of THAT." 8. "It works, but it's not been tested." 7. "Somebody must have changed my code." 6. "Did you check for a virus on your system?...
Read more