what about crisis?

everyone has been talking about crisis, The Crisis, already more than a year. so, what is the crisis impact for software testing and testers? "software consulting firm Ovum claims that the worldwide software testing services market is projected to reach 56 billion dollars by 2013, despite the global economic crisis".
In my background, all IT sector has less sofware projects. Companies save money first of all cutting IT expenses.
IT software companies may start saving with fewer testers. One person commented: "a client does want to buy testing services. He will test the product himself". Developers and coders are more valuable - they code and then test the product. And the tester remains as a luxury for better times.
When considering among testers, company would necessarily cut manual testers first over technical testers.
How do you feel crisis as a tester?

Comments

Roman said…
Less projects, less quality -> more motivation to learn, to read books about testing

Best Regards,
Roman
11:56 PM
ugne said…
Roman, please mention a few books here
11:58 PM
Roman said…
now reading: Systematic Software Testing. a bit old (year 2002) but like it because it is based on the IEEE Std. 828-1998. Process that is described in this book is called STEP "The Systematic Test and Evaluation Process"

looking for next book: "How We Test Software at Microsoft". Heard that there are very good case-studies. And of course everyone is interested how they make and test software :)
1:30 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