Verification and Validation, White Box and Black Box Testing - An Evaluation

Verification and Validation, White Box and Black Box Testing - An Evaluation

This Topic was discussed by Mr. Macarayo, Mr. Asilo and Ms. Morales and to evaluate their report, I can only say that they really did deliver the true context, definition and terms about their topic. They also did differentiate verification and validation and also white box testing and black box testing. The group really did a great job and they even got an applause from the class.

Overall, their reporting was great and you can even say that they really practice on how to get everybody's attention and relay the true message and context of the topic. Kudos!

Verification and Validation, White Box and Black Box Testing - An Exploration 

Verification vs Validation: What's the Difference?

In the world of testing, the differences between Verification and Validation can cause confusion. While the distinction may seem trivial, the two fulfill very separate purposes.

Imagine being asked to do a verification on a certain project but hold off on the validation. Our first question might be how are they different? When would you start, and what would that work look like?

If the difference between them is a little confusing, you’re not alone –countless development and testing professionals are in the same boat. So, whether you are completely confused or just fuzzy on the details, hopefully we’ll make it crystal clear.

All I can say that he differences between them are significant.

Differences between Verification and Validation

Prerequisite – Verification and Validation

Verification is the process of checking that a software achieves its goal without any bugs. It is the process to ensure whether the product that is developed is right or not. It verifies whether the developed product fulfills the requirements that we have. Verification is static testing.
Verification means Are we building the product right?

Validation is the process of checking whether the software product is up to the mark or in other words product has high level requirements. It is the process of checking the validation of product i.e. it checks what we are developing is the right product. it is validation of actual and expected product. Validation is the dynamic testing.
Validation means Are we building the right product?

Another Differentiation from: http://softwaretestingfundamentals.com/verification-vs-validation/

Thoughts in V&V (Verification and Validation)

V&V processes determine whether the products of a given activity conform to the requirements and are fit for its use.

The following are a few things to note:

• Verification is “Am I building the product right?”. Validation is “Am I building the right product?”
• In very simpler terms (to avoid any kind of confusion), we just remember that Verification means the review activities or the static testing techniques and validation means the actual test execution activities or the dynamic testing techniques.
• Verification may or may not involve the product itself. Validation definitely needs the product. Verification can sometimes be performed on the documents that represent the final system.
• Verification and validation do not necessarily have to be performed by the testers. As you see above in this article some of these are performed by the developers and other teams.

Black Box vs. White Box Testing

Software Testing can be majorly classified into two categories:

1. Black Box Testing is a software testing method in which the internal structure/ design/ implementation of the item being tested is not known to the tester
2. White Box Testing is a software testing method in which the internal structure/ design/ implementation of the item being tested is known to the tester.

Differences between Black Box Testing vs. White Box Testing:

BLACK BOX TESTING	WHITE BOX TESTING
It is a way of software testing in which the internal structure or the program or the code is hidden and nothing is known about it.	It is a way of testing the software in which the tester has knowledge about the internal structure r the code or the program of the software.
It is mostly done by software testers.	It is mostly done by software developers.
No knowledge of implementation is needed.	Knowledge of implementation is required.
It can be referred as outer or external software testing.	It is the inner or the internal software testing.
It is functional test of the software.	It is structural test of the software.
This testing can be initiated on the basis of requirement specifications document.	This type of testing of software is started after detail design document.
No knowledge of programming is required.	It is mandatory to have knowledge of programming.
It is the behavior testing of the software.	It is the logic testing of the software.
It is applicable to the higher levels of testing of software.	It is generally applicable to the lower levels of software testing.
It is also called closed testing.	It is also called as clear box testing.
It is least time consuming.	It is most time consuming.
It is not suitable or preferred for algorithm testing.	It is suitable for algorithm testing.
Can be done by trial and error ways and methods.	Data domains along with inner or internal boundaries can be better tested.
Example: search something on google by using keywords	Example: by input to check and verify loops
Types of Black Box Testing: A. Functional Testing B. Non-functional testing C. Regression Testing	Tyeps of White Box Testing: A. Path Testing B. Loop Testing C. Condition testing

Data source from: https://www.geeksforgeeks.org/differences-between-black-box-testing-vs-white-box-testing/

Thoughts in Black Box and White Box Testing

Black Box Testing	White Box Testing
the main focus of black box testing is on the validation of your functional requirements.	White Box Testing (Unit Testing) validates internal structure and working of your software code
Black box testing gives abstraction from code and focuses on testing effort on the software system behavior.	To conduct White Box Testing, knowledge of underlying programming language is essential. Current day software systems use a variety of programming languages and technologies and its not possible to know all of them.
Black box testing facilitates testing communication amongst modules	White box testing does not facilitate testing communication amongst modules

Reference

1. D. Packer, “Verification vs Validation: Do you know the difference?,” Plutora, 07-Apr-2019. [Online]. Available: https://www.plutora.com/blog/verification-vs-validation. [Accessed: 30-Nov-2019].
2. “Exact Difference Between Verification and Validation with Examples,” Software Testing Help, 10-Nov-2019. [Online]. Available: https://www.softwaretestinghelp.com/what-is-verification-and-validation/. [Accessed: 30-Nov-2019].
3. J. Mahak, “Differences between Black Box Testing vs White Box Testing,” GeeksforGeeks, 17-Oct-2019. [Online]. Available: https://www.geeksforgeeks.org/differences-between-black-box-testing-vs-white-box-testing/. [Accessed: 30-Nov-2019].
4. pp_pankaj, “Differences between Verification and Validation,” GeeksforGeeks, 18-Apr-2019. [Online]. Available: https://www.geeksforgeeks.org/differences-between-verification-and-validation/. [Accessed: 30-Nov-2019].
5. “Verification vs Validation,” Software Testing Fundamentals, 03-Mar-2018. [Online]. Available: http://softwaretestingfundamentals.com/verification-vs-validation/. [Accessed: 30-Nov-2019].
6. “What is BLACK Box Testing? Techniques, Example & Types,” Guru99. [Online]. Available: https://www.guru99.com/black-box-testing.html. [Accessed: 30-Nov-2019].
7. “White Box Testing,” Software Testing Fundamentals, 03-Mar-2018. [Online]. Available: http://softwaretestingfundamentals.com/white-box-testing/. [Accessed: 30-Nov-2019].

­