1. Society for Clinical Data Management (SCDM). (2023). Good Clinical Data Management Practices (GCDMP).
Reference: Section 5.4.3, "Testing," discusses the requirement for testing to be based on pre-defined specifications and to cover the functionality being tested. While the document may not use the term "white box," testing individual logic conditions of an edit check is a form of unit/structural testing that falls under this principle, as it verifies the internal design of the check, not just its user-facing requirement.
2. Patton, R. (2005). Software Testing (2nd ed.). Sams Publishing. (A standard text used in university software engineering curricula).
Reference: Chapter 3, "The Tester's Role," and Chapter 8, "Code-Based Coverage," define white-box testing as a method where "the tester can see the code and designs tests to exercise the code." It explicitly mentions testing all logical decisions and paths, which directly aligns with testing "each logic condition within each rule."
3. Ammann, P., & Offutt, J. (2016). Introduction to Software Testing (2nd ed.). Cambridge University Press. (University courseware textbook).
Reference: Chapter 2, "Coverage Criteria," pp. 35-37. This section details structural coverage criteria, such as branch coverage and condition coverage, which are core concepts in white-box testing. Testing "each logic condition" is a direct application of these criteria, which are based on the source code's structure.