What to send
Any distinct BP bug type or potential bad smell in free form. Code, traces, screenshots, diagrams, and short notes are welcome.
Research collaboration request
Behavioral Programming expert catalog
We are collecting Behavioral Programming debugging scenarios and potential bad smells for expert review.
The debugging catalog organizes 12 candidate bug types into five families, with BP-style pseudocode, explanations, and traces illustrating each failure mechanism. In addition, we present several potential BP bad smells: suspicious behavioral patterns that are not necessarily bugs, but may indicate incomplete, redundant, or problematic interactions in a BP model.
Two complementary catalogs
Choose the kind of evidence to inspect
The task
Help us refine both catalogs
Timing
We plan to keep this collection phase open for two weeks. A reminder will be sent after about a week and a half.
Goal
We will use bug types to construct a debugging dataset. Bad smells form a separate catalog of candidates for BP linting, runtime checks, and model review.
Methodology
Our methodology combines execution-based analysis of failures with structural review of requests, waits, blocks, and event relationships.
Acknowledgments
Thank you for helping shape the catalogs
We thank the BP community, researchers, lecturers, and practitioners who review these examples and contribute additional bug types or potential bad smells. Your feedback will help make the debugging dataset and bad-smell catalog more useful.
Bug types ยท Execution analysis
Debugging scenarios
Twelve candidate bug types are organized into five families. Each detail screen presents BP-style pseudocode, a focused explanation, and execution evidence that reveals the failure or an incorrectly excluded valid behavior.
Potential smell
Potential BP Bad Smells
Certain patterns in a Behavioral Programming model may be suspicious without being confirmed bugs. Evidence may come from model structure, execution behavior, or both; each smell is a reason for further inspection.