Made a discovery this morning. Was too lazy to read the book „the testing practitioner“, mentioned in previous post. And felt a desire to listen to something on Software testing topic. Yes! The internet! Of course – the YouTube site. Well, did not do the big research what to look at, took on the first - Google Tech Talks, December 9, 2005, Agile testing by Elisabeth Hendrickson.
My impressions – first, it is very interesting to find out one more source of information. Feels like participating at the conference. Will come back for sure and do some more watching and listening the other day.
The topic itself, agile testing. Am not familiar with it, and especially after the teaching feel it is something different I am working with. What I caught up, the agile testing is something anti-classical approach to testing, everyone is testing and testers are the developers, there are many iterations with the releases, all of them tested and working fine, there is much about test automation and the development is test driven. Also Elisabeth Hendrickson is test obsessed and evil person to software, as she says.
If you are interested in agile testing, may have a look. It was done 2 years ago, so there may be some new things to be added.
PROGRAMINĖS ĮRANGOS KOKYBĖS UŽTIKRINIMO SPECIALISTAS Aprašymas: SIŪLOMAS DARBAS PROGRAMINĖS ĮRANGOS KOKYBĖS UŽTIKRINIMO SPECIALISTUI VILNIUJE ARBA KAUNE. Detali informacija: “CVO Technology Recruitment” klientas – viena didžiausių IT įmonių Lietuvoje ir kitose Baltijos šalyse. Pagrindiniai įmonės privalumai - verslo procesų išmanymas, ilgametė projektų valdymo patirtis Lietuvoje ir užsienyje bei techniniai programinės įrangos vystymo įgūdžiai. Šiuo metu įmonė plečiasi ir į komandą VILNIUJE arba KAUNE kviečia prisijungti PROGRAMINĖS ĮRANGOS KOKYBĖS UŽTIKRINIMO SPECIALISTĄ (-Ę). Darbo pobūdis: Sistemų testavimas: klaidų taisymas ir tinkamas jų aplinkybių suformulavimas; Tarpinių ir galutinių testavimo rezultatų apibendrinimas; Komandos darbo koordinavimas bei konsultavimas testavimo klausimais; Srities naujienų sekimas ir pasiūlymai dėl jų diegimo. Reikalavimai kandidatui: Ne mažesnė nei 3 metų darbo patirtis
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 ask for
My previous employer organised internal security training for QAs. As coming not from development background, they were good, but too tough for me. There is really good free resource on pluralsight.com by Troy Hunt " Hack yourself first ". It is declared for developers to deepen their knowledge of security. Myself I found it really cool as the author explains everything clearly with good examples.
Comments