Skip to content

Unexpected @depends behaviour #9

Closed
@ondrejmirtes

Description

@ondrejmirtes

When I have a tree of depending tests:

  • testBasic
    • testBar($a) (depending on testBasic)
    • testLorem($a) (depending on testBasic)
      • testFoo($a) (depending on testLorem)
    • testIpsum($a) (depending on testBasic)

They are executed linearily and still the same object is passed as argument, so for example at testIpsum, I got the object with changes from testLorem). Which I consider as unexpected and not wanted behaviour.

I think that the order of executed tests should be tree-like, everytime with a new object:

running testBasic: testBasic
running testBar: testBasic - testBar
running testLorem: testBasic - testLorem
running testFoo: testBasic - testLorem - testFoo
running testIpsum - testBasic - testIpsum

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions