Skip to content

Intersuite dependencies at level 3 or more of nesting #25

@humbienri

Description

@humbienri

Hello @kiranz!

Am really enjoying trying out this tool for a Proof of Concept. Thank you for this!

I think I've read all (or most) of your documentation but have not figured it out. If a have a multi-level dependency set up where a test A in one suite A needs to first call a test B in another suite B, which in turn needs to call a test C in yet another suite C...can I just sort of "chain" them like that and test A in suite A only has to worry about calling/using the test B in suite B and assume that the test B will automatically take care of using/calling test C?

Test C is for authenticating and getting a token. Test B is for getting some default values that will be used across all other numerous tests and suites, such as those in suite A.

Or does it mean that tests in Suite A has to explicitly call both the dependency test B as well as explicitly call/use the dependency in test C?

Again, thanks for this tool and your time! I am not a JS developer so this sort of helps us bridge that gap w/ the actual Dev team.

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