@eagleoutice/flowr - v2.10.1
    Preparing search index...

    Interface DataflowTestConfiguration

    interface DataflowTestConfiguration {
        addFiles: FlowrFileProvider<{ toString(): string }>[];
        context: "dataflow" | "call-graph";
        expectedOutput: string | RegExp;
        expectIsSubgraph: boolean;
        minRVersion: string | undefined;
        modifyAnalyzer: (
            analyzer: FlowrAnalyzer,
        ) => void | FlowrAnalyzer<KnownParser> | undefined;
        mustNotHaveEdges: [NodeId, NodeId][];
        mustNotHaveVertices: Set<NodeId>;
        needsNetworkConnection: boolean;
        needsXmlParseData: boolean;
        resolveIdsAsCriterion: boolean;
        trimOutput: boolean;
        [key: string]: unknown;
    }

    Hierarchy (View Summary)

    Indexable

    • [key: string]: unknown

    Hierarchy-Diagram

    UML class diagram of DataflowTestConfiguration
    Index

    Properties

    addFiles context expectedOutput expectIsSubgraph minRVersion modifyAnalyzer mustNotHaveEdges mustNotHaveVertices needsNetworkConnection needsXmlParseData resolveIdsAsCriterion trimOutput

    Properties

    addFiles: FlowrFileProvider<{ toString(): string }>[]

    Which files to add to the project context

    context: "dataflow" | "call-graph"

    Whether to test the call graph instead of the dataflow graph

    expectedOutput: string | RegExp

    HANDLE WITH UTTER CARE! Will run in an R-Shell on the host system!

    expectIsSubgraph: boolean

    Specify just a subset of what the dataflow graph will actually be.

    minRVersion: string | undefined

    the (inclusive) minimum version of R required to run this test, e.g., MIN_VERSION_PIPE

    modifyAnalyzer: (
        analyzer: FlowrAnalyzer,
    ) => void | FlowrAnalyzer<KnownParser> | undefined

    Allows you to modify the analyzer before running the test. (assumes side-effects and reuses the same object if you return undefined)

    mustNotHaveEdges: [NodeId, NodeId][]

    The collection of edges that should not exist

    mustNotHaveVertices: Set<NodeId>

    The collection of vertex ids that should not exist

    needsNetworkConnection: boolean
    needsXmlParseData: boolean
    resolveIdsAsCriterion: boolean

    This changes the way the test treats the NodeIds in your expected graph. Before running the verification, the test environment will transform the graph, resolving all Ids as if they are slicing criteria. In other words, you can use the criteria 12@a which will be resolved to the corresponding id before comparing. Please be aware that this is currently a work in progress.

    trimOutput: boolean

    Settings

    Member Visibility

    On This Page

    Properties