testing job in vilnius, LT

Testuotojas (-a)
Vilnius, Kaunas
Darbo pobūdis:
-klaidų nustatymas ir tinkamas jų aplinkybių suformulavimas, apibūdinimas;-užtikrinimas, kad programa atitinka funkcinius ir biznio reikalavimus;-užtikrinimas, kad programa atitinka nefukcinius reikalavimus. -testavimo atvejų ir tikrinimo sąrašų sudarymas; -testavimo metrikų sekimas.
Reikalavimai kandidatui:
Aukštasis universitetinis išsilavinimas;Išsilavinimo sritis:matematika/informatika; Ne mažesnė nei 3 metų darbo patirtis IT srityje;Testavimo žinios ir patirtis ne mažiau nei 2-3 metai;Darbo su testavimo įrankiais patirtis; Darbo su duomenų bazėmis užklausų pagalba žinios ir patirtis. Anglų kalba. Orientacija į aptarnavimą, iniciatyvumas, orientacija į tikslą, bendradarbiavimas komandoje, analitinis mąstymas, orientacija į kokybę, planavimas ir organizavimas.
Įmonė kandidatui siūlo:
darbą vienoje iš rinkos lyderės pozicijas užimančių įmonių, geras darbo sąlygas ir puikias karjeros galimybes.
CV prašome siųsti iki:
2007.09.18
Kontaktinė informacija
Konkurse galima dalyvauti tik siunčiant savo CV per topCV sistemą.
Telefonas pasiteirauti: (8-5) 276 24 97; (8 671) 97120
Kontaktinis asmuo: Ana
Kontaktinio asmens pareigos: Konsultantė

Comments

Offshore Software Development said…
Clients should ensure that selected vendor has the well documented Information Security Management (ISM) Policy. Vendors need to provide a dedicated project and data server to their clients with audit control access on all the servers. Client should check that the Vendor’s facility is secured with smart card control access and vendor’s development team members have signed the Confidentiality agreements. In addition, the development contract should include clauses for Non-compete, Non-disclosure and non-solicitation.

Software Development Company
12:06 AM
Beef Recipes said…
Thanks great blog post
6:36 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