Hi all,is there a possibility to add variables and / or strings to a specific (region) checkpoint, that are displayed if a checkpoint fails?And can these strings or variables be accessed via jscript.example: (checkpoint (CP) 1 & 2 are known bugs, CP3 is a new bug)current behaviour:- CP1: "the regions are not equal."- CP2: "the regions are not equal."- CP3: "the regions are not equal."Wanted behaviour:- CP1: "the regions are not equal. Know bug, issue ID = 123"- CP2: "the regions are not equal. Know bug, issue ID = 239"- CP3: "the regions are not equal."I wanted to see directly which failed checkpoints are already known bugs and which fail for the first time.If there is a different solution to my problem, I would appreciate suggestions.Kind regards,Joachim

Hello Joachim,Currently, TestComplete does not provide an ability to add custom messages or variables to checkpoints.However, to post a custom message to the log when a checkpoint passes or fails, you can follow the following workaround:1. Disable logging by setting the value of the Log.Enabled property to False.2. Perform a checkpoint and assign its result to a variable.3. Enable logging by setting the value of the Log.Enabled property to True.4. Depending on the value of the variable that stores the checkpoint results, post your custom message to the test log.Please let us know whether this information helps you.Thank you.

Question, Julie:We're working on some validation plans for using automated testing in a regulated industry and one of the things we need is that, for any checkpoint executed, we log certain information to the log for evidence tracking. This solution you suggest sounds, really, rather excellent. I'd rather not have to write this code everywhere we call a checkpoint, though. Will this code work within the OnLogCheckpoint event handler? I'm looking to record in the log, on either a fail or pass, of a checkpoint this custom information.

Hi all,I already thought through different possibilities of workarounds for the problem, most of them are similar to your idea (@Julia).Right now I am not quite sure which one will be the best, because all of them require some work on every checkpoint and are not easy in maintanance.Enabling and disabling logging before / after each checkpoint is nothing I am keen to do. :-)Rather I'd like to use some sort of event handler that checks a variable which is set before a 'customized' checkpoint and cleard by the event handler.Something like: if variable = -1 then "new bug" else "known bug, issue id = " + variableJoachim

Robert,In general, you should be able to block messages to the log from within the event handler. At least, the following sequence works since TC3:' to prevent posting the default TestComplete messages to the LogLogParams.Locked = TrueOptions.Log.Enabled = False' Handle application Login windowIf Objects.Compare(Window, "LoginWindow") Then Options.Log.Enabled = True Log.Message .....End If' Replaces the TestComplete message with your message LogParams.Str = "My message" LogParams.Locked = False Options.Log.Enabled = True...But there might be a problem with figuring out what exact checkpoint triggered the handler and this should be investigated.

Hi all , What is the solution for below question?Test Complete's Disadvantage over HP QTP The major drawbacks are in the form of missing features like regular expressions and descriptive programming.

Adding strings or variables to each checkpoint

15 Replies

Julia_K
Alumni
14 years ago
Hello Joachim,

Currently, TestComplete does not provide an ability to add custom messages or variables to checkpoints.

However, to post a custom message to the log when a checkpoint passes or fails, you can follow the following workaround:

1. Disable logging by setting the value of the Log.Enabled property to False.

2. Perform a checkpoint and assign its result to a variable.

3. Enable logging by setting the value of the Log.Enabled property to True.

4. Depending on the value of the variable that stores the checkpoint results, post your custom message to the test log.

Please let us know whether this information helps you.

Thank you.
tristaanogre
Esteemed Contributor
14 years ago
Question, Julie:

We're working on some validation plans for using automated testing in a regulated industry and one of the things we need is that, for any checkpoint executed, we log certain information to the log for evidence tracking. This solution you suggest sounds, really, rather excellent. I'd rather not have to write this code everywhere we call a checkpoint, though. Will this code work within the OnLogCheckpoint event handler? I'm looking to record in the log, on either a fail or pass, of a checkpoint this custom information.
jsc
Regular Contributor
14 years ago
Hi all,

I already thought through different possibilities of workarounds for the problem, most of them are similar to your idea (@Julia).

Right now I am not quite sure which one will be the best, because all of them require some work on every checkpoint and are not easy in maintanance.

Enabling and disabling logging before / after each checkpoint is nothing I am keen to do. :-)

Rather I'd like to use some sort of event handler that checks a variable which is set before a 'customized' checkpoint and cleard by the event handler.

Something like:

if variable = -1 then "new bug" else "known bug, issue id = " + variable

Joachim
AlexKaras
Champion Level 1
14 years ago
Robert,

In general, you should be able to block messages to the log from within the event handler. At least, the following sequence works since TC3:

' to prevent posting the default TestComplete messages to the Log

LogParams.Locked = True

Options.Log.Enabled = False

' Handle application Login window

If Objects.Compare(Window, "LoginWindow") Then

    Options.Log.Enabled = True

    Log.Message ...

..

End If

' Replaces the TestComplete message with your message

LogParams.Str = "My message"

    LogParams.Locked = False

    Options.Log.Enabled = True

...

But there might be a problem with figuring out what exact checkpoint triggered the handler and this should be investigated.
saivadurai
Occasional Contributor
14 years ago
Hi all ,

What is the solution for below question?

Test Complete's Disadvantage over HP QTP

The major drawbacks are in the form of missing features like regular expressions and descriptive programming.
jsc
Regular Contributor
14 years ago
right now my solution is this:

function GeneralEvents_OnLogError(Sender, LogParams)

{

var MyIssue = KeywordTests.HandlerTest.Variables.issueID;



if (MyIssue == -1)

{

    LogParams.Str = "New bug: the region checkpoint failed.";

    LogParams.Color = clRed;

    LogParams.FontColor = clWhite;

}

else

{

    LogParams.Str = "Known bug (issueID = " + MyIssue + "): the region checkpoint failed.";

}

KeywordTests.HandlerTest.Variables.issueID = "-1";

}

In front of checkpoints that correspond to known bugs I have to set a variable manually to a value corresponding to the issue ID.

This works quite fine for me.

Is there any possibility to change the error-level of failed checkpoints via jscript to warning?

In the code above I was not able to do so.
jsc
Regular Contributor
14 years ago
I changed the code:

function GeneralEvents_OnLogError(Sender, LogParams)

{

var MyIssue = ProjectSuite.Variables.issueID;



if (MyIssue == -1)

{

    LogParams.Str = "New bug: the region checkpoint failed.";

}

else

{

    LogParams.Str = "Known bug (issueID = " + MyIssue + "): the region checkpoint failed.";

    Log.Warning(LogParams.Str);

    LogParams.Locked = true;

}

ProjectSuite.Variables.issueID = "-1";

}

Like this I get an error "New bug..." when a new bug appears and a warning "known bug..." when a known bug appears.

With this code there are no pictures attached to this warning.

1) How can I
attach the pictures to my warning, that normally would be shown with
the error of the checkpoint?

2) How can I access the name of the checkpoint, respectively the name of the expected picture?

(those parameters should be known within this method as they are part of the regular output)

Only drawback of this solution is, that when I doubleclick on the warning-line in the results-tab I will be redirected to my script instead of the corresponding checkpoint within the test. But that's ok...
AlexKaras
Champion Level 1
14 years ago
Hi Joachim,

> Is there any possibility to change the error-level of failed checkpoints via jscript to warning?

Yes, you should be able to do this using the approach I mentioned earlier when replying to Robert.

Something like that (untested VBScript mockup):

OnLogErrorHandler:

...

' to prevent posting the default TestComplete messages to the Log

LogParams.Locked = True

Log.Enabled = False

If (<WarningShouldBePosted>) Then

Log.Enabled = True

Log.Warning ...

End If

...

' post default TestComplete message to the Log

LogParams.Locked = False

Log.Enabled = True

<EndOfOnLogErrorHandler>

> Only drawback of this solution is, that when I doubleclick on the warning-line in the results-tab I will be redirected to my script instead of the corresponding checkpoint within the test.

Switch to the Call Stack pane in the Log (View | Panels | ... in the main menu) and I hope that the second line from the top should point to the keyword test. Double-click it and I beleive it will navigate you to the correct line in the keyword test (I just don't use keyword tests that is why I am so uncertain as for the keyword tests, but the described approach (navigation through the Call Stack pane) works great for regular coding approach).

Hope the above will help you...
jsc
Regular Contributor
14 years ago
Hi Alexis,

thanks for your reply. I already found a solution to posting a warning, but still have 2 problems:

1)

I am still not able to append the pictures that would be attached to the error (expected image & actual image) to this warning. I am reading through http://smartbear.com/support/viewarticle/12151/ and other articles but did not find a solution for it.

2)

The call stack panel just shows 1 line: "call stack", so there is no 2nd line to click onto.

Thanks for your help,

Joachim
jsc
Regular Contributor
14 years ago
2)

solved: hat to turn on EnableStackOnWarning

Log.CallStackSettings.EnableStackOnWarning = true;