news in Lithuania testing market

One of the first companies, offering testing services, has opened its website www.testuotojai.lt. Congratulations! "Testuotojai" means ‘the testers’ in Lithuanian language. The same as my blog's address - "testavimas" is for testing.
As they wrote, team has been working as software testers and now trying to do this as independent people, not a part of any IT company. The services description seems quite narrow for me, but ok, as it is the beginning.
The number of testers, together with the ads looking for software testing or QA specialists, has been really increasing in the last years. So, the birth of a company like this is a really natural development of software testing market in Lithuania.

Comments

Eglucia said…
As I've already seen that page, it doesn't seem to be very professional for me now. Though keeping the fact of that there was no similar services in Lithuania yet, the idea is impressively good. I am thinking of making some kind of meeting of Lithuanian testers in Vilnius. That should be interesting.
3:16 AM
ugne said…
that would be really interesting
4:00 AM
Anonymous said…
Nice... Do you have any info about who those people are?
about the meeting - I would be interested in participating :D
4:34 AM
Anonymous said…
O, pasirodo besidominčių atsiranda. :) Gal pradžiai reiktų neoficialaus meeto? :)
1:15 AM
Anonymous said…
neoficialus mytas irgi gerai :)
paskui prasides visokie oficialumai, nepelno organizacijos, 2% ant is moketoju kiseniu ir daznesni susitikimai :) juokauju
gal kasnors norit pasiulyti data ir vieta (kaip suprantu vln cia kolkas).
man asmeniskai tiktu bet kada darbo diena - na su penktadieniais tai sunkiau, bet paderinti galima viska :)
7:27 AM
Anonymous said…
Gal pradžiais apsikeičiam emailais? :) Pakalbinsiu kolegių (keista matyti testuotoją vyra Lietuvos platybėse) iš šen bei ten :)
3:42 AM
Anonymous said…
mano meilas: jonas.dobravolskas@gmail.com

keista kad keista :))))) as pazistu dar bent tris kurie visdar dirba testuotojais ir du kurie bent jau anksciau dirbo, kaip dabar tai net nezinau :))
11:51 PM
ugne said…
susidomėjusių susitikimu vis daugėja, tikiuosi 20 žmonių neviršysim :) siūlykite vietas, kur būtų galima pakankamai netriukšmingoje aplinkoje aptarti software testers life :)
12:27 AM
Anonymous said…
tai internetas labiausiai netriuksminga vieta :D :D :D
o siaip: yra stuokos guceviciaus gatvej (salia katedros) vynine tokia.
vakar ten buvau - tikrai rami ir faina vieta. tik regis staliuka reiktu rezervuotis. yra vietos lauke - nebijokit mergaites ten sildytuvas yra, tai salta tikrai nebutu :) o siaip tai cia tik pasiulymas :) laukiam daugiau
8:24 AM
Anonymous said…
po vakarykščio pašnekesio su kolega, grįžau čia - gaivinam pradinę idėją? :) Jei noro yra, gal ką sumastom kitą savaitę?
11:01 AM
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