Testing

Testing in basic words is just executing the program that we created to get the output that is expected. Here I will be talking about how testing is not just one basic step of running, but thinking in an abstracted way on how things really work while doing the testing. I will divide it into 4 levels in order to make a testing that is efficient.

1. There should be a test plan. A test plan is a document that acts like a record that specifies what data and input should the program include to run the program that is created. A test case is a special word used for the data input. A test plan must not only include the instructions but there should be reasoning or an explanation of the the data, such as the values, and it should include an expected output from the user in each case.

2. There should be code coverage. Code coverage is a layout on how the designed test cases are able to ensure if each statement in the program is executed. In order words its also called clear box testing because all the code is visible or shown in front of the tester or the person who inputs the information into the program, leading from the word "Clear".

3. There should be data coverage. Data coverage is another layout for designing the test cases which will ensure that the limits that has been set for that particular data is covered. In order words its called black-box testing because this layout is based on the input rather than the code.

4. There should be a test plan implementation. This process is rather the final step because we're running the test cases according to the test plan and be able to record the results of the runs. If there is flaws in the results (not expected), you should go back and debug (fix the errors). You can stop this process when all the results came out as expected. The implementation test is like proof for your results of the test cases by running the program.

Each step or each term is really important for testing because they're a basis for checking the input or code that has been entered by planning out a test plan, making code, and data coverage, and finally conduct the test plan implementation. Testing is important because we're able to ensure the mistakes in the input and code to be able to debug the it by running tests. Each test that you make should be planned because you're able to fix it easier by breaking it into different pieces. Always created an expected results so when you test the program you are able to predict if the results are the same or not, so you can go off and debug the code you made. Different techniques are used for testing for example a program that reads in three values and sums them. We should use the clear-box test because the inputer is always able to see the data. Overall testing a program is something that needs to be planned before head even before inputting the code and be able to match the expected result with the actual result.