Exploratory Software Testing
E560745
Exploratory Software Testing is a software testing approach that emphasizes simultaneous learning, test design, and execution, relying on tester creativity and adaptability rather than strictly predefined test cases.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Exploratory Software Testing canonical | 1 |
| Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5996890 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: Exploratory Software Testing Context triple: [James Whittaker (software engineer), notableWork, Exploratory Software Testing]
-
A.
International Symposium on Software Testing and Analysis
The International Symposium on Software Testing and Analysis is a leading annual research conference focused on advancing the theory and practice of software testing, analysis, and verification.
-
B.
Agile Software Development, Principles, Patterns, and Practices
"Agile Software Development, Principles, Patterns, and Practices" is a foundational software engineering book by Robert C. Martin that explains agile methodologies through object-oriented design principles, design patterns, and best practices for building maintainable code.
-
C.
Framework for Integrated Test (FIT)
Framework for Integrated Test (FIT) is an early agile testing framework that lets customers, testers, and developers collaboratively define and automatically execute executable specifications using simple, table-based documents.
-
D.
No Silver Bullet: Essence and Accidents of Software Engineering
"No Silver Bullet: Essence and Accidents of Software Engineering" is a seminal essay arguing that no single technology or practice will yield dramatic, order-of-magnitude improvements in software productivity, reliability, or simplicity.
-
E.
Interactive Software Engineering
Interactive Software Engineering was a software company founded by Bertrand Meyer, best known for developing the Eiffel programming language and promoting object-oriented software engineering methods.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: Exploratory Software Testing Target entity description: Exploratory Software Testing is a software testing approach that emphasizes simultaneous learning, test design, and execution, relying on tester creativity and adaptability rather than strictly predefined test cases.
-
A.
International Symposium on Software Testing and Analysis
The International Symposium on Software Testing and Analysis is a leading annual research conference focused on advancing the theory and practice of software testing, analysis, and verification.
-
B.
Agile Software Development, Principles, Patterns, and Practices
"Agile Software Development, Principles, Patterns, and Practices" is a foundational software engineering book by Robert C. Martin that explains agile methodologies through object-oriented design principles, design patterns, and best practices for building maintainable code.
-
C.
Framework for Integrated Test (FIT)
Framework for Integrated Test (FIT) is an early agile testing framework that lets customers, testers, and developers collaboratively define and automatically execute executable specifications using simple, table-based documents.
-
D.
No Silver Bullet: Essence and Accidents of Software Engineering
"No Silver Bullet: Essence and Accidents of Software Engineering" is a seminal essay arguing that no single technology or practice will yield dramatic, order-of-magnitude improvements in software productivity, reliability, or simplicity.
-
E.
Interactive Software Engineering
Interactive Software Engineering was a software company founded by Bertrand Meyer, best known for developing the Eiffel programming language and promoting object-oriented software engineering methods.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
software testing approach
ⓘ
software testing technique ⓘ |
| aimsAt | finding important problems fast ⓘ |
| alignedWith | context-driven testing principles ⓘ |
| associatedWith | session-based test management ⓘ |
| benefit |
better coverage of unknown risk areas
ⓘ
flexibility to change test direction ⓘ high defect discovery rate in short time ⓘ |
| canBeAppliedTo |
functional testing
ⓘ
regression testing ⓘ usability testing ⓘ |
| canBeCombinedWith | scripted test cases ⓘ |
| canInclude |
note-taking during test sessions
ⓘ
on-the-fly test design ⓘ time-boxed test sessions ⓘ |
| challenge |
harder to measure coverage
ⓘ
harder to reproduce defects without good notes ⓘ |
| contrastsWith |
fully predefined test cases
ⓘ
scripted testing ⓘ |
| differsFrom | ad hoc testing by being goal-driven ⓘ |
| documentedIn | software testing literature ⓘ |
| emphasizes |
simultaneous learning
ⓘ
simultaneous test design ⓘ simultaneous test execution ⓘ |
| focusesOn |
critical thinking
ⓘ
tester skill ⓘ testers’ domain knowledge ⓘ |
| goal |
adapt tests based on findings
ⓘ
discover defects quickly ⓘ learn about the product ⓘ |
| oftenDocumentedBy |
session reports
ⓘ
test notes ⓘ |
| originatedIn | software testing practice community ⓘ |
| promotedBy |
Cem Kaner
NERFINISHED
ⓘ
James Bach NERFINISHED ⓘ Michael Bolton NERFINISHED ⓘ |
| relatedTo |
ad hoc testing
ⓘ
risk-based testing ⓘ |
| reliesOn |
tester adaptability
ⓘ
tester creativity ⓘ |
| requires |
continuous learning by the tester
ⓘ
real-time decision making ⓘ |
| suitableFor |
agile development environments
ⓘ
early-stage products ⓘ poorly documented systems ⓘ |
| supports | rapid feedback ⓘ |
| usedBy | professional software testers ⓘ |
| usedIn | exploratory test sessions ⓘ |
| uses | charters to guide testing sessions ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: Exploratory Software Testing Description of subject: Exploratory Software Testing is a software testing approach that emphasizes simultaneous learning, test design, and execution, relying on tester creativity and adaptability rather than strictly predefined test cases.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.