Black box testing
BBT is a test technique that focuses on testing the functionality of the system against its specifications without knowledge of internal design or code. Tests are based on requirements and functionality.

When creating black-box test cases, the input data used is critical. Three successful techniques for managing the input data required include:

Equivalence Partitioning: Equivalence Partitioning is a technique that consists of developing test cases that focuses on data to be used for testing. In equivalence partitioning say if a program has credit limits within a given range ($10,000 - $15,000) would have three equivalence classes:
-- < $10,000 (invalid)
-- Between $10,000 and $15,000 (valid)
-- > $15,000 (invalid)

Boundary Analysis: A technique that consists of developing test cases that focus on the input and output boundaries of a given function. In same credit limit example, boundary analysis would test:
-- Low boundary +/- one ($9,999 and $10,001)
-- On the boundary ($10,000 and $15,000)    
-- Upper boundary +/- one ($14,999 and $15,001)

Error Guessing: The tester can guess how the error can occur in an application For example, in an example where one of the inputs is the date, a tester may try February 29 if it is a month having 28 days or can enter To date greater than FROM date etc.

Boundary Value analysis
BVA is a technique for test data selection. Boundary values include maximum value, minimum value, values - just inside boundaries, values - just outside boundaries, typical values, and error values. The main motive of inserting this type of data is to check whether the application works correctly for these extreme or special values.

White box testing
White box testing involves the knowledge of the internal design and logic of an application's code. It includes manual reading of code & syntax checking to find errors.