Sunday, October 16, 2016

Testing Terms And How to Use Them

I was thinking about the time I first various terms of software testing methods and was like “I have no idea what this is.” Then they explain it and I’m like I have been doing that for a while now just didn’t know it was called that. So I have decided that I will help everyone out and talk about a few of the vocabulary that we should know as testers. The ones I will be addressing in this blog post I will discuss in this post black box testing, white box testing and dynamic testing.
First is black box testing is a way of testing your program that you just test the output. They call it black box because you don’t look at code at all you just look at the output.  The exact definition is that it is a way of test where you only test the functionality of the program without looking at the internal structures and workings. An example of black box testing is if you have a program that squares a given input. To black box test you have a series inputs and just look at what it outputs to make sure that it outputs the square of the input or an error if needed.
Second is white box testing. White box testing refers to looking at the guts of a program. The exact definition of white box testing is “White-box testing (also known as clear box testing, glass box testing, transparent box testing, and structural testing) is a method of testing software that tests internal structures or workings of an application, as opposed to its functionality (i.e. black-box testing).” Unit tests are way these are checked as well as manually stepping through code and doing visual checks as well.
Third is dynamic testing. You can't talk about dynamic testing without talking about static testing. So static testing is rest your program without running it at all. Dynamic testing is the opposite. It is where you use the compiler to build the program and run it. Black box testing is dynamic testing because you just test the output of the program.
Just to make a note, these testing methods or any other testing methods should not be used by itself you should always use a mixture. When you use a mixture of techniques you avoid pesticide in your program and therefore have a higher degree of confidence when you have to release to the public.
What are some testing terms that you think every tester Should know?


  1. what is configuration testing? and the differences between test plan document and test strategy document

    1. configuration testing is the process of checking the software you are testing with various types of hardware.
      Test plan document vs a Test strategy document - test plan has multiple items included in it including a test strategy where as the test strategy is just the test strategy.
      Test Strategy is the specific idea that will be used to test the software