Skip to content

Expected behavior of interactive tests #144

Closed

Description

@ehrenfeu

@rohangirishrao I believe the original testing instructions were created by you, could you add a line to the document, describing what should happen?

## Expected behavior / results
FIXME!!

Activity

  1. added this to the 2.1.0 milestone on Apr 8, 2026
  2. added theissue type on Apr 8, 2026
  3. added
    documentationMissing documentation, docstring conventions, ...
    on Apr 8, 2026
  4. ehrenfeu commented on Apr 8, 2026

    @ehrenfeu
    MemberAuthor

    This is also something we should check in the other interactive tests...

  5. moved this to Backlog in IMCF-Fijion Apr 9, 2026
  6. rohangirishrao commented on Apr 10, 2026

    @rohangirishrao
    Contributor

    We have 3 .md files and a .py file for the save_parameters function - do you prefer all .py files or .md? I'm guessing no one will drag and drop directly, so making a description and then a python block in .md makes more sense, right?

  7. rohangirishrao commented on Apr 13, 2026

    @rohangirishrao
    Contributor

    PR #146 - changed all files to python, and added clear expected behaviour and prerequisites.

  8. added a commit that references this issue on Jun 24, 2026
  9. modified the milestones: 2.1.0, 2.0.0 on Jun 24, 2026
  10. moved this from Backlog to Done in IMCF-Fijion Jun 24, 2026
  11. closed this as completedby moving to Done in IMCF-Fijion Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

documentationMissing documentation, docstring conventions, ...

Type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions