Testing

Question 1

Software Testing

Answer 1

Assessment of software quality to verify and validate the software system under development, reduce the risk of software failure in operation, and ensure software meets stakeholder needs

Question 2

Testing Principles

Answer 2

Testing reduces the probability of defects but cannot prove the absence of defects; testing cannot be exhaustive and requires prioritization; testing early reduces derived defects, time, and cost

Question 3

Static Testing

Answer 3

Testing without code execution, often used to test specifications, designs, and code early in the development process (e.g., reviews, walkthroughs, and analysis)

Question 4

Dynamic Testing

Answer 4

Testing that involves executing the code, focusing on functionality, performance, security, and other aspects of the software behavior

Question 5

Black-Box Testing

Answer 5

Testing based on specifications without knowledge of the internal structure of the software (e.g., equivalence partitioning and boundary value analysis)

Question 6

White-Box Testing

Answer 6

Testing based on the internal structure of the software, aiming for test coverage of statements, branches, paths, and conditions (e.g., statement testing and branch testing)

Question 7

Test Levels

Answer 7

Component testing (testing individual units of code), integration testing (testing how components work together), system testing (testing the entire system), and acceptance testing (testing to ensure the system meets user needs)