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.
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 ...
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?...
Comments