- Software Testing Dictionary
- Home
- A
- Acceptance Testing
- Accessibility Testing
- Active Testing
- Actual Outcome
- Ad Hoc Testing
- Age Testing
- Agile Testing
- All-pairs Testing
- Alpha Testing
- API Testing
- Arc Testing
- Anomaly
- Assertion Testing
- Audit
- Automated Software Testing
- B
- Backward Compatibility Testing
- Baseline Artifacts
- Basis Path Testing
- Basis Test Set
- Bebugging
- Behavior Testing
- Benchmark Testing
- Beta Testing
- Big-Bang Testing
- Binary Portability Testing
- Black box Testing
- Bottom Up Testing
- Boundary Testing
- Branch Testing
- Breadth Testing
- Bug
- Build Validation
- Business Process
- Business Requirement
- C
- Capability Maturity Model
- Capture/Replay Tool
- Cause-Effect Graph
- Code Coverage
- Code Freeze
- Code Inspection
- Code Review
- Code Walkthrough
- Code-Based Testing
- Code Driven Testing
- Code Free Testing
- Comparison Testing
- Compatibility Testing
- Compliance Testing
- Concurrency Testing
- Condition Coverage Testing
- Configuration Testing
- Conformance Testing
- Context Driven Testing
- Control Flow Path
- Conversion Testing
- Correctness
- Coverage Items
- Cyclomatic Complexity
- D
- Data Integrity Testing
- Data Driven Testing
- Data Flow Testing
- Database Testing
- Debugging
- Decision Coverage Testing
- Defect
- Defect Logging and Tracking
- Defect Life Cycle
- Delta Release
- Dependency Testing
- Depth Testing
- Destructive Testing
- Development Environment
- Documentation Testing
- Domain Testing
- Durability Testing
- Dynamic Testing
- E
- Emulator
- End-to-End Testing
- Endurance Testing
- Entry Criteria
- Equivalence Partitioning Testing
- Error
- Error Guessing
- Error Seeding
- Exhaustive Testing
- Exit Criteria
- Expected Outcome
- Exploratory Testing
- F
- Failover Testing
- Failure
- Fault
- Fault injection Testing
- Feasible Path
- Feature Testing
- Functional Decomposition
- Functional Requirements
- Functional Testing
- Fuzz Testing
- I
- Implementation Testing
- Incremental Testing
- Independent testing
- Infeasible Path
- Inspection
- Install/Uninstall Testing
- Integration Testing
- Interface Testing
- Internationalization Testing
- Inter Systems Testing
- Isolation Testing
- Issues
- M
- Maintainability
- Manual Testing
- Model Based Testing
- Modified Condition Testing
- Modularity Driven Testing
- Monkey Testing
- Mutation Testing
- P
- Pair Testing
- Pairwise Testing
- Parallel Testing
- Partial Test Automation
- Passive Testing
- Path Testing
- Peer Review
- Penetration Testing
- Performance Testing
- Portability Testing
- Positive Testing
- Post Condition
- Precondition
- Predicted Outcome
- Priority
- Process Cycle Test
- Progressive Testing
- Prototype Testing
- R
- Random Testing
- Recovery Testing
- Regression Testing
- Release Candidate
- Release Note
- Reliability Testing
- Requirements
- Requirements Based Testing
- Requirements Traceability Matrix
- Result
- Retesting
- Review
- Risk
- Risk Management
- Root Cause
- S
- Safety Testing
- Sanity Testing
- Scalability Testing
- Scenario Testing
- Schedule
- Script
- Security Testing
- Simulation
- Smoke Testing
- Soak Testing
- Software Requirement Specification
- Stability Testing
- State Transition
- Static Testing
- Statistical Testing
- Storage Testing
- Stress Testing
- Structural Testing
- Structured Walkthrough
- Stub
- Symbolic Execution
- Syntax Testing
- System Integration Testing
- System Testing
- System Under Test
- T
- Technical Review
- Test Approach
- Test Automation
- Test Basis
- Test Bed
- Test Case
- Test Case Design Technique
- Test Suite
- Test Completion Criterion
- Test Completion Report
- Test Completion Matrix
- Test Data
- Test Data Management
- Test Driven Development
- Test Driver
- Test Environment
- Test Execution
- Test Management
- Test Maturity Model
- Test Plan
- Test Steps
- Test Strategy
- Test Tools
- Thread Testing
- Top Down Integ. Testing
- Total Quality Management
- Traceability
- U
- Unit Testing
- Unreachable Code
- Usability Testing
- Use Case Testing
- User Acceptance Testing
- User Interface Testing
- Selected Reading
- UPSC IAS Exams Notes
- Developer's Best Practices
- Questions and Answers
- Effective Resume Writing
- HR Interview Questions
- Computer Glossary
- Who is Who
System Under Test
What is System Under Test (SUT)?
System under test (SUT) refers to a system that is being validated by the testers. The terminology is also known as application under test.
The System Under Test (SUT) also corresponds to a software that is matured and has gone through unit and integration testing.
Advertisements