Skip to content

Re-optimize cases collection: parametrized cases do not always need to be turned into fixtures #169

Open

Description

@smarie

As noted in #158 , since 3.0.0 all parametrized cases are turned into fixtures. This ensures solid support for all kind of complex nesting and fixtures depenencies. However maybe we could simplify this when a case is parametrized but the parametrization does not contain any fixture reference ? In that case we still need to make sure that if there are lazy values, the "lazyness" needs to be intelligently combined. OR, an alternative is to only simplify when there are no fixture refs NOR lazy values.

Activity

  1. smarie commented on Dec 18, 2020

    @smarie
    OwnerAuthor

    Note that #170 may solve this by supporting parametrized lazy_values

  2. smarie commented on May 21, 2021

    @smarie
    OwnerAuthor

    One aspect that needs not to be forgotten is how easy the parameter of a case function can be accessed afterwards. With the current situation (parametrized cases = fixtures) it is relatively easy, see #211 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions