Test Cases Question:
Explain transaction testing, syntax testing,
domain testing, logic testing, and state testing?
Answer:
Transaction testing: Transaction testing generally refers to the testing of individual loans and is also known as
account testing, account sampling, or transaction-level testing.
Syntax testing: Syntax testing is a static,black box testing technique for protocol implementations and for testing command driven softeware and similar application.
domain testing:it is a white box testing method and to check values taken by a variable, a condition, or an index, and to prove that they are outside the specified or valid range. It also contains checking that the program acepts only valid input , because it is unlikely to get reasonable results if idiocy has been entered. Colloquially, this part can be called ``garbage in -- garbage out'' testing.
logic testing:Logic-based testers design tests from logical expressions that appear in soft-ware artifacts such as source code, design models, and requirements speci -
cations
state testing:is a load testing type apporch and with this testing great flexibility in dealing with common system test problems: limited access to the system test environment, unstable software, or changing operational conditions. Because each test case verifies correct execution on a path from the idle state to the software state under test, our method does not require the continuous execution of all test cases.
account testing, account sampling, or transaction-level testing.
Syntax testing: Syntax testing is a static,black box testing technique for protocol implementations and for testing command driven softeware and similar application.
domain testing:it is a white box testing method and to check values taken by a variable, a condition, or an index, and to prove that they are outside the specified or valid range. It also contains checking that the program acepts only valid input , because it is unlikely to get reasonable results if idiocy has been entered. Colloquially, this part can be called ``garbage in -- garbage out'' testing.
logic testing:Logic-based testers design tests from logical expressions that appear in soft-ware artifacts such as source code, design models, and requirements speci -
cations
state testing:is a load testing type apporch and with this testing great flexibility in dealing with common system test problems: limited access to the system test environment, unstable software, or changing operational conditions. Because each test case verifies correct execution on a path from the idle state to the software state under test, our method does not require the continuous execution of all test cases.