Issue Tracking

    Availability: BiG EVAL DQM Version 2.7.0 and up

    Using the following functions, you can control the behavior of the issue-tracking feature out of the control-script of a testcase.

    Note:

    • The following commands have an effect only if a testcase fails and an issue gets created. That means that the creation of issues must be enabled in the testcase-editor.
    • If an issue already exists, the testresult will be attached to the existing issue only. During this process, there will be no change in the issues title, description, owner or assignee. The following commands have no effect in that case.

     

    Set Identification

    Each issue that gets tracked by BiG EVAL is identified by a character string. This could be the ID of a testcase, the ID of a data record or any other character string. This identifier allows BiG EVAL to combine testresults that belong together.

    How the identifier is built can usually be configured in the testcase-editor. In specific scenarios - especially if you use the scripting-functionallity of BiG EVAL- it makes sense to set the identifier manually. You can use the following command to do so:

    SetIssueIdentifier("example-identifier");

     

    Set title and description

    Use the following commands to set the title and the description of the issue that gets created.

    Set the title:

    SetIssueTitle("My issue title");

    Set the description:

    SetIssueDescription("My description");

     

    Set the responsible person

    Use the following commands to set the responsible person of an issue. The only parameter of the function is either the user ID within BiG EVAL, the users e-mail address or the username.

    SetIssueOwnedBy("e0c67a85-e967-4a16-b88f-36419111f3d8");

    or:

    SetIssueOwnedBy("user@domain.com");

     

    Assign issue to a user

    Use the following commands to assign the issue to a specific person. The only parameter of the function is either the user ID within BiG EVAL, the users e-mail address or the username.

    SetIssueAssignedTo("e0c67a85-e967-4a16-b88f-36419111f3d8");

    or:

    SetIssueAssignedTo("user@domain.com");

     

    Example:

    // Query the available sales stores from the ERP.
    var stores = QueryTable("AW ERP", "SELECT Name, ManagerEmail FROM Sales.Store");

    // Loop through all the stores and execute the testcase for each of them.
    foreach(DataRow storeRow in stores.Rows)
    {
        // Extract ID and Name of the current sales territory.
        var storeName = storeRow["Name"].ToString();
        var managerEmail = storeRow["ManagerEmail"].ToString();

        // Write a comment to the test-result to show the current store.
        SetComment($"Store: {storeName}");

        // Configure the issue-tracking
        SetIssueIdentifier($"{Test.TestId}-{storeName}");
        SetIssueTitle($"Customer count test failed for store {storeName}");
        SetIssueDescription("The test failed because customer-count couldn't be resolved correctly.");
        SetIssueOwnedBy(managerEmail);
        SetIssueAssignedTo(managerEmail);

        // Set the name of the store as a parameter
        SetParameter("StoreName", storeName);

        // Execute the test.
        await ExecuteAsync();
    }

     

     

    Was this article helpful?
    0 out of 0 found this helpful

    Comments