well, testing field is quite narrow, much less information in comparing tech news or sport news :) here is a site for software testing news. mostly from the Quardev Laboratories news but there are some good articles.
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?" 5. "Even…
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.
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 testingColleague'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 all/any existing test…