Answer: Dynamic testing is done by executing the code or program with
Various input values and later on the output is verified.
Q #2) What is GUI Testing?
Answer: GUI or Graphical User Interface testing is the process of testing The software’s user interface against the provided Requirements/mockups/HTML designs etc., Q #3) What is Formal Testing? Answer: Software verification, carried out by following a test plan, Testing procedures and proper documentation with approval from The customer is termed as Formal Testing. Q #4) What is Risk-Based Testing? Answer: Identifying the critical functionality in the system and then Deciding the orders in which these functionalities are to be tested
And perform testing is termed as Risk-based Testing.
Q #5) What is Early Testing? Answer: Perform testing as soon as possible in the development Lifecycle to find defects at the early stages of STLC. Early testing Is helpful to reduce the cost of fixing defects at the later stages Of STLC. Q #6) What is Exhaustive Testing? Answer: Testing functionality with all valid, invalid inputs and preconditions is called Exhaustive testing. Q #7) What is Defect Clustering? Answer: Any small module or functionality may contain a number of Defects and to concentrate more on testing these functionalities is Known as Defect Clustering. Q #8) What is Pesticide Paradox? Answer: If already prepared test cases do not find defects, add/revise Test cases to find more defects, this is known as Pesticide Paradox. Q #9) What is Static Testing? Answer: Manual verification of the code without executing the program Is called Static Testing. In this process, the issues are identified in The code by verifying code, requirement and design documents. Q #10) What is Positive Testing? Answer: It is the form of testing which is conducted on the application To determine if the system works properly or not. Basically, it is Known as the “test to pass” approach. Q #11) What is Negative Testing? Answer: Testing software with a negative approach to check if the System is not “showing error when not supposed to” and “not
Showing error when supposed to” is termed as Negative Testing.
Q #12) What is an End-to-End Testing? Answer: Testing the overall functionality of the system including the Data integration among all the modules is called End-to-End Testing. Q #13) What is Exploratory Testing? Answer: Exploring the application, understanding its functionalities, Adding (or) modifying the existing test cases for better testing is Called Exploratory testing. Q #14) What is Monkey Testing? Answer: Testing conducted on an application without any plan and Carried out randomly with the tests to find any system crash with
The intention of finding tricky defects is called Monkey Testing.
Q #15) What is Non-Functional Testing? Answer: Validating various non-functional aspects of the system such as User interfaces, user-friendliness, security, compatibility, Load, Stress, and Performance, etc., is called Non-Functional testing. Q #16) What is Usability Testing? Answer: Checking how easily the end-users are able to understand and Operate the application is called Usability Testing. Q #17) What is Security Testing? Answer: Validating whether all security conditions are properly Implemented in the software (or) not is called Security testing. Q #18) What is Performance Testing? Answer: The process of measuring various efficiency characteristics of a System such as response time, load stress transactions per minute,
Transaction mix, etc., is termed Performance Testing.
Q #19) What is Load Testing? Answer: Analyzing both the functional and performance behavior of an Application under various conditions is called Load Testing. Q #20) What is Stress Testing? Answer: Checking the application behavior under stress conditions (or) Reducing the system resources and keeping the load as constant and Checking how the application is behaving is called Stress Testing