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
Software verification
(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!
== Dynamic verification (Test, experimentation) == Dynamic verification is performed during the execution of software, and dynamically checks its behavior; it is commonly known as the [[Software testing|Test]] phase. Verification is a Review Process. Depending on the scope of tests, we can categorize them in three families: * ''Test in the small'': a test that checks a single function or class ([[Unit test]]) * ''Test in the large'': a test that checks a group of classes, such as ** Module test (a single module) ** [[Integration test]] (more than one module) ** System test (the entire system) * ''Acceptance test'': a formal test defined to check acceptance criteria for a software ** Functional test ** Non functional test (performance, [[stress testing (software)|stress test]]) The aim of software dynamic verification is to find the errors introduced by an activity (for example, having a medical software to analyze bio-chemical data); or by the repetitive performance of one or more activities (such as a stress test for a web server, i.e. check if the current product of the activity is as correct as it was at the beginning of the activity).
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)