Skip to content

Interactive debugging #44

@rtens

Description

@rtens

Behavior should be created in an interactive way. Basically there should always be a context with an actual message with which the behavior is created. If you have several example messages and assertions regarding the visible behavior, you have basically TDD. Add easy sand-boxing and you have a very nice way to program, basically always debugging.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions