User:Mehrdad714/Books/Hardware testing1

This user book is a user-generated collection of Wikipedia articles that can be easily saved, rendered electronically, and ordered as a printed book. If you are the creator of this book and need help, see Help:Books (general tips) and WikiProject Wikipedia-Books (questions and assistance).

Edit this book: Book Creator · Wikitext

Order a printed copy from: PediaPress

[ About ] [ Advanced ] [ FAQ ] [ Feedback ] [ Help ] [ WikiProject ] [ Recent Changes ]

Hardware testing[edit]

Electronic hardware[edit]

Hardware Testing: Electronic hardware; Digital electronics; Acceptance testing; Analog verification; Automated optical inspection; Automated X-ray inspection; Automatic test equipment; Bead probe technology; Black-box testing; Boundary scan; Boundary scan description language; Burn-in; Continuity test; Corelis; Debug port; Design for testing; Device under test; Diagnostic design specification; Enterprise test software; Environmental stress screening; ESD Simulator; Fault grading; Final Quality Audit; Fixtureless in-circuit test; Flying probe; Functional Testing (manufacturing); Gray box testing; In-circuit functional tester; In-circuit test; Inquisitor (hardware testing software); Integration testing; Joint Test Action Group; Level-sensitive scan design; Manufacturing test requirement design specification; Mixed flowing gas; Negative-bias temperature instability; Ongoing reliability test; PBIST; Power-off testing; Programmable load; Spy-Bi-Wire; Stress test (hardware); System testing; Test engineer; Test mode; Testbed; White-box testing; Test method; Design for manufacturability; Test plan; Fault coverage; Manufacturing; Quality assurance; Return merchandise authorization; Printed circuit board; Oscillation; Graphical user interface testing; Usability testing
Two Section: Software performance testing; Compatibility testing; Exception handling; Load testing; Volume testing; Stress testing; Security testing; Scalability testing; Sanity testing; Smoke testing (software); Exploratory testing; Ad hoc testing; Regression testing; Installation testing; Maintenance testing; Recovery testing; Computer accessibility; Americans with Disabilities Act of 1990; Section 508 Amendment to the Rehabilitation Act of 1973; Highly accelerated life test; World Wide Web Consortium; Web Accessibility Initiative; Temperature; Overclocking; Dynamic voltage scaling; Underclocking; Stress testing (software); Jinx Debugger; Destructive testing; Scenario analysis; Software testing; Technischer Überwachungsverein; Simulation; CHESS model checker; ISO/IEC 29119; Test Environment Management; Portal:Software testing; A/B testing; Acceptance test-driven development; Agile testing; All-pairs testing; American Software Testing Qualifications Board; Analytical Performance Modeling; API Sanity Checker; Applause (software company); Application performance engineering; Armitage (computing); Association for Software Testing; Attack patterns; Augmented reality-based testing; Australia and New Zealand Testing Board; Auticon; Automated Testing Framework; Basis path testing; Bebugging; Behavior-driven development; Boundary case; Boundary testing; Boundary-value analysis; Browser speed test; BS 7925-1; BS 7925-2; Bug bash; Build verification test; Burke–Fisher error repair; Business process validation; CA/EZTEST; Cantata++; Cause–effect graph; Characterization test; Classification Tree Method; Cloud testing; Code coverage; Code integrity; Codenomicon; Component-based usability testing; Concurrent testing; Conference room pilot; Conformance testing; Continued Process Verification; Continuous testing; Core Security Technologies; Corner case; Critical Quality Attributes; Crowdsourced testing; Daikon (system); Daily build; Data-driven testing; Decision table; Decision-to-decision path; Design predicates; /dev/full; Development testing; Keynote DeviceAnywhere; Domain testing; Dry run (testing); DSploit; Dynamic program analysis; Dynamic testing; Edge case; Endeavour Software Project Management; Equivalence partitioning; Error guessing; Fagan inspection; Fault injection; Framework for integrated test; Functional testing; Fuzz testing; Game testing; Gcov; Given-When-Then; Google Guice; Happy path; Hungarian Testing Board; Hybrid testing; IBM Product Test; Independent software verification and validation; International Society for Software Testing; International Software Testing Qualifications Board; InterWorking Labs; Keyword-driven testing; LDRA Testbed; Learnability; Lightweight software test automation; List of software reliability models; RadView Software; Loader.io; Login VSI; Manual testing; Matrix of pain; Mauve (test suite); Maveryx; Metamorphic testing; Metasploit Project; Microsoft Reaction Card Method (Desirability Testing); Mobile-device testing; MockServer; Model-based testing; Modified condition/decision coverage; Modularity-driven testing; Monkey test; Month of bugs; Mutation testing; National Software Testing Laboratories; NMock; Non-functional testing; Non-regression testing; Operational acceptance testing; Oracle (software testing); Original Software; Oulu University Secure Programming Group; Pair testing; Parameter validation; Parasoft; Partial concurrent thinking aloud; Penetration test; PlanetLab; Playtest; Portability testing; Probe effect; Process validation; Program animation; Program mutation; Protocol implementation conformance statement; Pseudolocalization; Pylint; Qualitest Group; Software diagnosis; Software map; Software quality; Random testing; Rapid control prototyping; Real-time testing; Reverse semantic traceability; Risk-based testing; Robot Framework; Robustness testing; Sandbox (software development); Scenario testing; Search-based software engineering; Security AppScan; Security bug; Semantic decision table; Session-based testing; SigmationTF; Soak testing; SOASTA; Software Design Engineer in Test; Software reliability testing; Software test documentation; Software testability; Software testing controversies; Software testing outsourcing; Software Testing, Verification & Reliability; Software verification; Specification by example; Sputnik (JavaScript conformance test); Squish (Froglogic); Static testing; Stream X-Machine; System integration testing; System under test; Tcov; Tessy (software); Test Anything Protocol; Test assertion; Test automation; Test bench; Test case; Test data; Test data generation; Test design; Test double; Test effort; Test execution engine; Test harness; Test management; Test Management Approach; Test script; Test strategy; Test stub; Test Studio; Test suite; Test Template Framework; Test vector generator; Continuous test-driven development; Test-driven development; Test-Driven Development by Example; Testdroid; Testing high-performance computing applications; Testing Maturity Model; TestLink; TestPlant; Testware; Think aloud protocol; Tiger team; TPS report; TPT (software); Traceability matrix; Transformation Priority Premise; Tree testing; TTCN-3; Twist (software); Unit testing; Heisenbug; Usability goals; Software verification and validation; Vulnerability (computing); Web testing; WebLOAD; White box (software engineering); Windmill (testing framework); X-Machine Testing