Boundary Value Analysis is based on testing the boundary values of valid and invalid partitions. The behavior at the edge of the equivalence partition is more likely to be incorrect than the behavior within the partition, so boundaries are an area where testing is likely to yield defects.
It checks for the input values near the boundary that have a higher chance of error. Every partition has its maximum and minimum values and these maximum and minimum values are the boundary values of a partition.
Decision tables are used in various engineering fields to represent complex logical relationships. This testing is a very effective tool in testing the software and its requirements management. The output may be dependent on many input conditions and decision tables give a tabular view of various combinations of input conditions and these conditions are in the form of True(T) and False(F). Also, it provides a set of conditions and its corresponding actions required in the testing.
Use Case Testing is a type of black box testing and that helps developers and testers to identify test scenarios, test strategy ,test estimation ,testbed requirement and testplan .Business experts and developers and testers must have a mutual understanding of the requirement, as it's very difficult to attain.
Use case testing is a kind of functional testing which consists Regressing testing,sanity testing ,Fire and smoke testing and vulnerability testing.
It helps to identify the testing procedures which is belong to individual modules.
It is used to describe testplan and testcases at the initial level .
Use case testing is not testing that is performed to decide the quality of the software.
Although it is a type of end-to-end testing, it won't ensure the entire coverage of the user application.
Use case testing will find out the defects in integration testing.
It is very effective in identifying the gaps in the software that won't be identified by testing individual components in isolation.
Use case-driven analysis that helps manage complexity since it focuses on one specific usage aspect at a time.
The complexity of the test cases will be reduced as the testing team will follow the path given in the use case document.
Usecases are the functional requirements of the system.
They help to identity the integration defects, defects that arise due to incorrect communication between different components.
Use cases are used to hearten designers to outcomes before attempting to specify outcomes, and thereby they help to make requirements more proactive in system development.
Usecase testing helps to identify the gaps in software that might not be identified by testing individual components.
Usecase testing is used to develop test cases at the system level or acceptance level.
This topic not yet covered in Manual testing session.