Editing White-box testing (section)

== Advantages ==
# Side effects of having the knowledge of the source code is beneficial to thorough testing.{{cn|date=November 2019}}
#Optimization of code becomes easy as inconspicuous bottlenecks are exposed.{{cn|date=November 2019}}
#Gives the programmer introspection because developers carefully describe any new implementation.{{cn|date=November 2019}}
#Provides traceability of tests from the source, thereby allowing future changes to the source to be easily captured in the newly added or modified tests.<ref name=binder>{{cite book |last=Binder |first=Bob |date=2000 |title=Testing Object-oriented Systems |url=https://archive.org/details/testingobjectori00bind |url-access=registration |publisher=Addison-Wesley Publishing Company Inc. |isbn=9780201809381 }}</ref>
#Easy to automate.<ref name=introtest />
#Provides clear, engineering-based rules for when to stop testing.<ref name=myers>{{cite book |last=Myers |first=Glenford |author-link=Glenford Myers |date=1979 |title=The Art of Software Testing |url=https://archive.org/details/artofsoftwaretes00myer |url-access=registration |publisher=John Wiley and Sons |isbn=9780471043287 }}</ref><ref name=introtest />