Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
White-box testing
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Basic procedure == White-box testing's basic procedures require the tester to have an in-depth knowledge of the source code being tested. The programmer must have a deep understanding of the application to know what kinds of test cases to create so that every visible path is exercised for testing. Once the source code is understood then it can be analyzed for test cases to be created. The following are the three basic steps that white-box testing takes in order to create test cases: # Input involves different types of requirements, functional specifications, detailed designing of documents, proper source code and security specifications.{{cn|date=November 2019}} This is the preparation stage of white-box testing to lay out all of the basic information. # Processing involves performing risk analysis to guide whole testing process, proper test plan, execute test cases and communicate results.{{Cn|date=November 2019}} This is the phase of building test cases to make sure they thoroughly test the application the given results are recorded accordingly. # Output involves preparing final report that encompasses all of the above preparations and results.{{Cn|date=November 2019}}
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)