 |
del.icio.us |
 |
Digg |
 |
Furl |
 |
|
 |
Rojo |
| Add to OnlyWire |
Culture · Geography · Health · History · Mathematics · Nature · Philosophy · Religion · Society · Technology
Software testing is the process used to measure the quality of developed computer software.
Usability testing is a technique used in design to allow the designer to improve a product by measuring its usability, or user-friendliness. [1]
Usability testing focuses on measuring a human-made product's capacity to meet its intended purpose. Examples of products that commonly benefit from usability testing are web sites or web applications, computer interfaces, documents, or devices. Usability testing measures the usability, or ease of use, of a specific object or set of objects, whereas general human-computer interaction studies attempt to formulate universal principles.
While Grace Hopper was working on the Harvard Mark II Computer at Harvard University, her associates discovered a moth stuck in a relay and thereby impeding operation, whereupon she remarked that they were "debugging" the system. Though the term computer bug cannot be definitively attributed to Admiral Hopper, she did bring the term into popularity. The remains of the moth can be found in the group's log book at the Smithsonian Institution's National Museum of American History in Washington, D.C..[2]
Fuzz testing or fuzzing is a software testing technique that provides random data ("fuzz") to the inputs of a program. If the program fails, the defects can be noted. The great advantage of fuzz testing is that the test design is extremely simple, and free of preconceptions about system behavior.
- "An effective way to test code is to exercise it at its natural boundaries." -- Brian Kernighan
- "Program testing can be used to show the presence of bugs, but never to show their absence!" -- Edsger Dijkstra
- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth
- "A relatively small number of causes will typically produce a large majority of the problems or defects (80/20 Rule)." -- Pareto principle
- "given enough eyeballs, all bugs are shallow." -- Linus's Law according to Eric S. Raymond
- Test Process : Behavior driven development, ISO 9000, CMM, Static code analysis, Lightweight Software Test Automation, Debugging, Mutation analysis, Equivalence Partitioning, Quality control, Software quality, Software testing, Performance engineering, Formal verification, Risk-based Testing, Fault injection, Fagan inspection, Reliability engineering, Software Quality Assurance, Software inspection, Dynamic program analysis, Symbolic computation, Extreme quality assurance, Test automation, Computerized system validation, Testing Web Sites, Testathon,
- Test types : Acceptance testing, Ad hoc testing, Black box testing, Code coverage, Compatibility testing, Conformance testing, Load testing, Localization testing, Mobile Device Testing, Sanity testing, Smoke testing, Stress testing, GUI software testing, Fuzz testing, Unit testing, White box testing, Boundary testing, Integration testing, Installation testing, Exploratory testing, All-pairs testing, Scenario testing, Soak testing, QuickCheck, Software performance testing, Regression testing, System testing, Model-based testing, Static testing, Usability testing, Game testing, Session-based testing, Hallway testing, System integration testing, Boundary Value Analysis, Pseudolocalization, Recovery testing, Software verification, Playtest, Keyword-driven testing, Monkey test, Manual testing, Combinadic, Build Verification Test,
- Famous Bugs
- People : James Bach, Brian Marick, Gene Spafford, James D. McCaffrey, Kenneth D. Cameron, Harlan Mills, Brent Hailpern, Cem Kaner, Erich Gamma, Charles E. Brady, Jr., Steven Hawley, Patrick G. Forrester, Charles D. Gemar, Stephen S. Oswald, Adam Kolawa, Vipin Dixit (Vip's), Abhinav Khanna,
- Companies : SmarteSoft, CTG, Original Software,Segue Software, Applabs, Mercury Interactive, Lionbridge, National Software Testing Laboratories, Parasoft,Compuware
- Test Management : Test Strategy, Test Plan, Test effort
- Software Tools : SmarteScript, SmarteLoad, CAST tool, CfcUnit, CFUnit, Check, Concutest, Coverity, CPPUnit, Curl-loader,Testware, Concutest, Check (unit testing framework), SIMMON, WET Web Tester, Jtest, Insure++, VectorCAST (unit and integration testing framework)
- Category: Emulator, Virtual appliance, LDRA Testbed, HttpUnit, NUnit, Soapui, xUnit, JMeter, Splint (programming tool), SimpleTest, IBM OLIVER (CICS interactive test/debug), Flawfinder, Litmus (Mozilla), PyUnit, JTiger, TestBench, SilkTest, LURCH, JUnit, DUnit, CPPUnit, Coverity, FitNesse, Framework for Integrated Test, Mauve (test suite), Test Automation Framework, CFUnit, FUnit, FindBugs, Ranorex, LoadRunner, Watir, TestLink,
- general Job requirements :
- Personal traits :
- Certification : British Computer Society, National Software Testing Laboratories, CSQE, ISTQB, CSTE
- Membership Associations : Software Engineering Institute, Association for Software Testing, American Society for Quality
- Software standards : IEEE 829
- outsourcing : Software testing outsourcing
- metrics
- education
- training
- awards
- Titles : Test Manager, Test Lead, Test Automation Engineer, Test Designer, Test Architect, Test Methodologists & Principle Tester, Senior Tester & Tester
- Online resources : [3]
- Social Network for Testing Professionals : [4]
- Wiki Lists : List of unit testing frameworks
- Terminologies : Software bug, Anomaly in software, Test case, Test suite, Test script, Unusual software bug, System under test, Mock object, Test harness, Test data, Testbed, Test bench, Debugger, Boundary case, Verification and Validation, test plan, Test Anything Protocol, Zarro boogs, Thrash (computer science), Memory debugger, Xqa,
- Popular Books:
- Magazines / Periodicals :
- Misc. :
- Expand the stubs
- Add Citation for verification
