In theory, we can consider software testing as a very rationale approach. You start from unit of code or requirements and then you create the tests that will prove that your software does what it is expected to do… and doesn’t create problems with edge cases. In his book Oblique Testing, Mike Talks propose to add an additional perspective to software testing using the oblique strategies approach.
Software Testing Books: Load Testing, Unit Testing, Functional Testing
Apache JMeter is one of the most well known open source tool that can be used to perform load testing or functional testing. The book Performance Testing with JMeter 2.9 written by Bayo Erinle provides you with the knowledge to start using JMeter and the basic concepts for successful performance testing.
As a major part of the software usage activity is gradually shifting to mobile devices, knowing how to test mobile applications is now a very valuable skill for software testers. The book “Tap Into Mobile Application Testing” written by Jonathan Kohl provides an extensive coverage of the mobile software testing domain written by an experience practitioner.
A paradev is defined as “anyone on a software team that doesn’t just do programming.” In his book “Pride and Paradev”, Alister Scott discusses a lot of the trade-off and issues met by software testers in an Agile software development project. As the world is not black or white, he decided to write a collection of contradictory claims about software testing; knowing that the practical implications lie somewhere in between.
Tomek Kaczanowski writes that the idea behind its “Bad Tests, Good Tests” book is “to present test code snippets and discuss ways of making them better.” To achieve this goal, he explores a large amount of code and tests to discuss all the issues that you can meet in your software testing activities.