Event Handling
- Dominant language
- Java
- Stars
- 9
- Forks
- 4
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 7
Description
NIE Events should be able to be triggered in the following way in reference to the step they target :
| # | Event Start | Event Start Finish | Tear Down | How to Signal | Comment |
| - | ----------- | ------------------ | ---------- | -------------- | ---------- |
| 1 | Before Step | AFTER/DURING Step | After step | NIE_33 | Current behavious : We do not care when exactly but the next step waits for the event to finish |
| 2 | Before Step | Before Step | After step | NIE_23 | SYNCHRONEOUS : No matter if the even is sychroneous or not |
| 3 | Before Step | Before Step | Before Step | NIE_22 | |
| 4 | Before Step | Before Step | latest scenario end | NIE_20 | |
| 5 | Before Step | After Step | latest scenario end | NIE_30 | |
| 6 | Before Step | latest scenario end | latest scenario end | NIE_00 | |
![Uploading PhasedDiagrams-asynchronousEventModels.drawio.png…]()
Contributor guide
Research direction
The issue provides no file, test, or entry point; begin by locating the NIE event-handling implementation and existing tests for NIE_33, NIE_23, NIE_22, NIE_20, NIE_30, and NIE_00. Compare current behavior with the six timing models in the table, then define tests that demonstrate each event start, finish, teardown, and signaling condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100