Blog‎ > ‎

Fundamentals of Software Testing

posted Apr 12, 2012, 5:23 PM by Unknown user
Fundamentals of Software Testing


I didn’t know that much about software testing. I know this is just the tip of the iceberg, but it’s new information for me. This e-book explains the basic concepts of software testing and quality assurance. It contains a lot of information to understand the different types of tests that you can do. If you know just a little bit about this subject, you have to read this e-book.


Software testing is extremely important. The quality of the software is acquired by doing many tests. Also, it’s important to test the software at early stages, as the e-book indicates. This is to avoid dragging those mistakes during the software development life cycle. We need to verify the software to validate it later. At first I was confused about these two concepts, but I learned the difference. We have to verify that the different processes (requirements, design, etc.) are right; and then, after coding, we need to validate what we’ve just created. During validation we have to create and run different tests.


There’s always a risk of letting a few bugs or errors be on the final product. As the e-book says, there’s no software that is 100% free of errors. The objective of software testing is to minimize the amount of bugs. Then, if we find more and more bugs, we need to fix them. This is the importance of applying tests in early stages. If not, we would have to fix everything that went wrong at the end of the development cycle. That costs a lot of resources.


You can find the difference between white box testing and black box testing. White box testing is when you test the software knowing how its internal processes work, and black box testing is when you test the software like if you were an end user that knows nothing about how the software works internally. The software may be working right, but not according to the customer requirements, that’s why both of them are important. Also, there is the positive testing and negative testing. Positive testing is when you test what the system is supposed to do and negative testing is when you test something that the system is not supposed to do. These are like testing the system from different points of view.


In this e-book we can find concepts and then more concepts. If you read a little further you will find… … … yes… more concepts. That’s what it’s all about, to understand the basics of manual testing and the different types of tests.


I find these really interesting, because is an essential phase while developing any project. We need to be sure that the product that we just created is high-quality software.


I wrote what I learned. The e-book taught me that I know nothing about software testing and there’s a lot to learn.


Javier Rojas D.

Comments