1. What is component testing in test analysis?

Component testing, also known as unit, module and program testing, searches for defects in and verifies the functioning of software (e.g. modules, programs, objects, classes etc.) that are able to be tested separately. Component testing may be done in isolation from the rest of the system depending on the context of the development life cycle and the system.

2. When decision table testing is used?

Decision table testing is used for testing systems for which the specification takes the form of rules or cause-effect combinations. In a decision table the inputs are listed in a column with the outputs in the same column but below the inputs. The remainder of the table explores combinations of inputs to define the outputs produced.

3. Please tell me what are the white-box testing techniques as a test analyst?

White-box testing techniques use the internal structure of the software to derive test cases. They are commonly called 'glass-box' techniques (implying you can see into the system) since they require knowledge of how the software works.

4. What is exploratory testing as a test analyst?

Exploratory testing is a hands-on approach in which testers are involved in minimum planning and maximum test execution. The planning involves the creation of a test charter, a short declaration of the scope of a short (1 to 2 hour) time-boxed test effort, the objectives and possible approaches to be used. The test design and test execution activities are performed in parallel typically without formally documenting the test conditions, test cases or test scripts. This does not mean that other, more formal testing techniques will not be used. Some notes will be written during the exploratory-testing session, so that a report can be produced afterwards.