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
Unit 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!
=== Automated testing frameworks === An automated testing framework provides features for automating test execution and can accelerate writing and running tests. Frameworks have been developed for [[list of unit testing frameworks|a wide variety of programming languages]]. Generally, frameworks are [[Third-party software component|third-party]]; not distributed with a compiler or [[integrated development environment]] (IDE). Tests can be written without using a framework to exercise the code under test using [[Assertion (software development)|assertions]], [[exception handling]], and other [[control flow]] mechanisms to verify behavior and report failure. Some note that testing without a framework is valuable since there is a [[barrier to entry]] for the adoption of a framework; that having some tests is better than none, but once a framework is in place, adding tests can be easier.<ref>{{cite web|url=http://www.bullseye.com/coverage.html|access-date=24 March 2009|title=Intermediate Coverage Goals|author=Bullseye Testing Technology|date=2006β2008}}</ref> In some frameworks advanced test features are missing and must be hand-coded.
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)