Hi all! Sometimes I run my project and forget to clear breakpoints, is there any way to clear it by script? For example, I would like to clear all breakpoints by doing something like this: function clearBreakpoints(){ // clear breakpoints magic} Anybody?

Nice :D I see that a lot of people use high number of, "on/off variables" in their projects :) I posted a new idea because of this post, being able to set "Conditional breakpoints" condition by default, if you like it, please give kudos at the post below http://community.smartbear.com/t5/TestComplete-Feature-Requests/Clear-breakpoints-by-script/idc-p/105621#M284

I did say it was a long winded and rather unpractical way to do it! I can't see a way to set a default condition but that would have been a nice feature. You could also add an annoying message box that you need to confirm before starting the tests. After seeing this a few times you would never forget about breakpoints again :smileyhappy: function RunMainTests(){ var buttons = MkSet(mbYes, mbNo); if(MessageDlg("Have you removed all breakpoints?", mtConfirmation, buttons, 0) == mrYes) { // Test code... }} Unless you click Yes the tests won't start.

You can disable all debugging from the toolbar without having to find all breakpoints. The included image shows debugging enabled. Each click toggles debuggin.

Bit of a long winded way with additional work that is essentially mimicking the toolbar button but what about using conditional breakpoints and a debugging flag? Have a variable, something like enableDebugging and set it to true by default. When adding a breakpoint put enableDebugging in the condition column. When it's true it will pause on breakpoints, when it's false it will ignore it and continue running. You can then have a SetDebuggingMode function that sets this to true/false and call it as required.

The toolbar button is left on, I'm not clicking it off. Technically I'm not disabling debugging, I'm just setting a variable that all the conditional breakpoints check, since the previous code set it to false, it means all the breakpoints are ignored. Edit: I added a ProjectSuite boolean variable called "enableDebugging", to access this (using C++ script) it's pSuite["enableDebugging"]. So to set it off in the script it's pSuite["enableDebugging"] = false;

"You could also add an annoying message box that you need to confirm before starting the tests. After seeing this a few times you would never forget about breakpoints again " Ha ha! I do this quite a lot. I have project level booleans for "Test Mode" (which disables most of my logging and reading in of data in favour of local test data in the function). After all, you have to test the test code! TFS Mode. We use an in-house custom DLL to allow my tests to talk to and update TFS. Needs to be switched off a lot to avoid spamming TFS to death! Screen Capture mode. Don't always want them. I also have a local/remote flag. But that is determined by whether or not a dummy folder is present on the C: drive of the machine the test is run on and is used to determine where logs and results are dumped to on completion. The first three are set to bring up exactly the type of annoying popup you refer to. But if it detects it's running it remote mode, the popups don't happen as there won't be anyone there to see as as most remote runs are started by a build process. Works well, but I can see how it wouldn't be much fun to reverse engineer some of it in. I've had all in this place, as part of a larger test framework, since the start. (Lessons learned from the QTPro days mostly ...)

Clear breakpoints by script | SmartBear Community

18 Replies

william_roe
Super Contributor
9 years ago
You can disable all debugging from the toolbar without having to find all breakpoints. The included image shows debugging enabled. Each click toggles debuggin.
- jorgesimoes1983
  Regular Contributor
  9 years ago
  william_roe, I knew that one, it's one of the best workarounds, although it would be nice if we were able to do it by script.
  
  Thanks anyway!
StevenN
Contributor
9 years ago
Bit of a long winded way with additional work that is essentially mimicking the toolbar button but what about using conditional breakpoints and a debugging flag?

Have a variable, something like enableDebugging and set it to true by default. When adding a breakpoint put enableDebugging in the condition column. When it's true it will pause on breakpoints, when it's false it will ignore it and continue running.

You can then have a SetDebuggingMode function that sets this to true/false and call it as required.
- jorgesimoes1983
  Regular Contributor
  9 years ago
  StevenN, that is actually a good idea, but how do you disable debugging by script (without having to press the button)?
  - StevenN
    Contributor
    9 years ago
    So, if the project variable was called "enableDebugging", The set function could be:
    
    funtion SetDebuggingMode(state)
    {
    pSuite["debuggingMode"] = state;
    }
    
    Then when running your tests have something like this:
    
    function RunMainTests()
    {
    // Sets the flag to false so any breakpoints will be ignored
    SetDebuggingMode(false);
    // Run tests...
    }
k_de_boer03
Contributor
9 years ago
NOTE: Backup your project before you try this, just in case.

Haven't got time to test this myself, but I believe the breakpoints are stored in the project suite .tcCfgExtender file.

I think this file is generated and not required to run your tests. So you could try to delete this before you run.
- jorgesimoes1983
  Regular Contributor
  9 years ago
  k_de_boer03, Good idea, but does not work :)
HKosova
SmartBear Alumni (Retired)
9 years ago
You can add and delete breakpoints only at design time.

To delete all breakpoints:

View > Debug > Breakpoints.

Ctrl+A, Del.

Or you can temporarily disable the debugger: in the Debug menu, unselect Enable Debugging. The breakpoints remain, but TestComplete won't stop on them.
- k_de_boer03
  Contributor
  9 years ago
  Yeah, thats probably better than my suggestion
- jorgesimoes1983
  Regular Contributor
  9 years ago
  HKosova, that one I knew already, usually I use shortcut CTRL+B then delete everything, but sometimes I forget breakpoints after debugging, so I was thinking of having a script do disable it or clear all breakpoing when I run project suite.
  - jorgesimoes1983
    Regular Contributor
    9 years ago
    I found this topic http://community.smartbear.com/t5/Functional-Web-Testing/Disable-debug-on-script-routine/td-p/80166
    
    I guess we can't do it, although it would be nice.
    
    Another topic about the subject
    http://community.smartbear.com/t5/Functional-Web-Testing/how-to-ignore-breakpoints/td-p/72225

Forum Discussion

Clear breakpoints by script

18 Replies

Related Content

set Breakpoint

Breakpoint did not work

Script works, setting breakpoint complains about unable to find the object

Breakpoints No Longer Working

Breakpoints No Longer Working

Recent Discussions

testcomplete feature Intelligent Quality Add Ons

SessionCreator /Timeout option not firing EventControl_OnTimeout

Object Browser does not display WPF DataGridCell Border

Issue with retrieving text from listbox items in desktop win32 application

Read data from Excel