Introducing software testing - a book


a book

Found a book in the net, thought would share. to have more colors here :). It is an introduction to software testing. "Introducing Software Testing" By Louise Tamres. "Managers are becoming aware of the need to test new products, though often the task of software testing is assigned to a programmer who, although he may have extensive programming experience, has not been trained to test software, and is suddenly expected to do so with a strict project deadline approaching. This book is intended to come to the rescue of such an IT professional. It gives an brief overview of testing, then in a practical way show how to develop test cases, covering aspects such as:
- best practice documentation strategies, methods and standards; and
- tips on handling the various requirements facing the tester, including fitness for use models and presenting the case for testing to your manager.

A number of real-life case studies are introduced in the early chapters and then used throughout as examples of how to put the methods presented into practice and proceed successfully with them. These include an Object-Oriented and a Web testing example. The book will also be structured to provide extensive references out to other books in the testing area, to which the reader will be pointed to further develop his testing skills."

what is interesting, have never read a book on testing. just some resources in the web....

Comments

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