I'm not sure if workspace is the right terminology but I am using Katalon and have 2 irritating issues debugging. I suspect they are related..
1) Old breakpoints that have been cleared are being hit quite often (I've cleared some more recently and they are properly cleared so I wondor if there is a point in time where some were not emptied out properly)
2) One test case/script that gets called by a test suite is showing a different script when being debugged. This is very odd as it is actually running the right script in code but is sowing a different one and stopping at unrelated break points.
Is there a way to clean Katalon degug config out in some way?
Has anyone else experienced this ?
Yes, Katalon has a degug option that you can try: file > Clean.
You can try to read more here.
Related
I've been using the ESM module with VSCode and my Mocha unit tests for a long time now, a couple of years at least. Recently when I launch an individual test file in VSCode and set a breakpoint in the test file, it no longer breaks in the original file, but rather breaks in the "ESM compiled" file. I don't really know how ESM works enough to talk about it very well, but the file is compiled/transpiled/transformed in some way with all the imports converted to non-ESModule code. I'm able to step through, and it continues to step through other files as well, but each new file opened is this newly "ESM compiled" version instead of the original file, like it used to be. I only just noticed this recently. So I decided to install and older version of VSCode and see if it still happened, and it turns out it doesn't. With version 1.45.x it works as usual, but with anything newer, I get all these "ESM compiled" files opening up when I step through code.
Does anyone know why this is happening? Is there any new setting I can set in the newer VSCode versions that would cause this to not happen? It's really more of an annoyance than anything. I can still get my work done, but it's not as streamlined as it used to be. I will probably end up just downgrading permanently until I can find a way to make it not occur in the new version.
So, if anyone has experienced this, or knows of something new in VSCode that would cause this, I'd really appreciate some help. Thanks.
When running my code in debug mode, I keep getting 2 error messages:
Could not delete [path_to]\productiondb.log. May be locked by another process
I don't know what process might be locking it. It comes when I make changes to the code while my Pivotal tc Server is running in debug mode, but it dosent seem to create a lot's of trouble. Sometimes however, I get this warning:
Also due to some changes. I usally just restart the server and move on. This isen't the real problem, the real problem is that I get these messages when I havent doen any changes. Somethimes it accures when I run a certen part of the code, other times i occurs when I open certen codes in sts, however, it doen't seem to stop at the same place twice.
I am suspecting that this has something to do with git. I am using git to change between versions and doing tests. So I am thinking that STS has some of the code in memory from before I changed branche with git, and isen't updating it before I run or open the file with that code. But I am rather new to both sts and git, and can't be certan that it would work that way. If it is, does anyone know how to update sts after I have changed branch? If it is not, does anyone know what might causing it?
If you run an app in debug mode, the Eclipse Debugger tells the application when code gets changed and tries to use the debug API to swap in the new code into the running application. This is especially useful if you debug your code, hit a breakpoint, step through the code, fit the issue, change the code, and press save. At that moment, the Eclipse compiler updates the class file and tells the running JVM to swap in the new code. If that succeeds, the debugger will jump back to the last stack frame and the execution of your app will continue with the beginning of the method that you entered. This allows you to directly continue to debug and step through the updated code without restarting the app.
While this is a great feature of the JVM, it is very limited in terms of what scope of changes to the classes the JVM can deal with while doing this hot-swap. It is usually limited to method implementations. So adding new methods, adding or deleting members of the class, etc, are not supported. As a result, the above screenshot will appear. It means that the JVM wasn't able to hot-swap the changed code and will continue to run with the previously loaded code instead of the changed one.
I'm still studying for my computer science degree and have mostly focused on the mathematics side of things for now. However, in my current job I am working with Selenium IDE (specifically because it doesn't require coding knowledge) and I'm having a bit of trouble:
I need to test a Shift + click as well as a cherry-pick (Control + click) command on the web-based software we are creating, but it's not working. Manually pressing control and then clicking different elements on the screen works fine, however.
Like I said, I'm using Selenium IDE 2.9.1, and I'm using it on Firefox 50.0.2 on a Windows 10 install. My commands on that section are as follows:
Screenshot of the IDE command
The idea, obviously, being to select the object named Field1, depressing the Ctrl key, selecting the object named Field2 and then releasing the Ctrl key. This should, theoretically anyway (and does work when done manually outside of the IDE), select Field1 and then cherry-pick Field2 from the list as well.
This, however, is not the case, and it doesn't work.
Can anyone, please, advise me on how to proceed here? Should the commands be structured differently? Am I using the incorrect commands? Is there something else I can try?
As a PS: The same issue persists with the shiftKeyDown command as well.
I have searched for this issue online and found no help that actually works for me yet, hence this post.
I am looking forward to your replies, in the hope that I can find success... :)
I think that it is a Selenium IDE original command problem.
When you tried to simulate pressing Ctrl key and used "controlKeyDown/Up" command, it just changed the boolean value and did not fired a real key down/up event. Also Shift and Alt key could not work.
Maybe you should try to add a "keyDown/Up" command after "controlKeyDown/Up" command and the target could be //body .
And, if you need, please try to use the tool, SideeX, the extended version of Selenium IDE. Maybe this problem will be solve in the future and make the test case flexible. Here is the link to SideeX and there are more details about the tool.
OK, I found the solution.
When compiling the tests I test them by running through them step by step to ensure that everything is working like it should, before saving it to a test suite and letting it run on it's own. Now, this involves me double-clicking every command in the Table one by one, in sequence, and keeping and eye on the screen to ensure that it executes and behaves exactly like I want it to. Simple, understandable, logical, correct?
Well, it seems like the controlKeyDown and controlKeyUp commands DO NOT WORK in this way.
I built a bare-minimum test case using only the 4 commands: click the element, controlKeyDown, click the next element, controlKeyUp. I ran through the test a hundred times with no success, but then I started thinking - what if the controlKeyDown command is never released? That would cause issues outside of the test (on the rest of the environment, obviously), since the Ctrl key would be permanently depressed. So I figured that the Selenium IDE either 1. Releases the key in a short amount of time automatically (faster than I can execute the command to click the next element manually) or 2. It simple ignores the controlKeyDown command if it's not run in a complete test case/suite.
So I took the 4-line test case, built up a test screen with test grid elements and ran the test case - and it works. Perfectly, actually.
So, in case anyone has similar issues in the future, try to RUN the test case instead of clicking through it or executing commands manually.
I am trying to run my projects in Eclipse, whenever I used to run any program a window appear and it shows that project is launching and building.
This never happened before. In fact, it was working very okay an hour before but now, even for old created project it showing this and not moving ahead.
Is this a general thing happened in eclipse as I haven't seen this before.
I want to get out of this to move ahead and to run the project.
The Launcher looks like this :
The progress Bar is also not moving ahead if it's building the project.
It's definitely normal to see; there's times I'll see it two or three times in a day. It shows up if the launching process is waiting on anything or is expected to take more than a couple seconds.
In your case, it seems to be stuck on "Building workspace," which happens when you open Eclipse. The more projects you have in Eclipse and the more sections of workspace you have (groups of tabs), the longer it takes to build your workspace. So I'm going to wager a guess that you tried to launch a project within the first minute or two of Eclipse being open. Am I right?
If that's the case, just wait a bit, and watch the lower right corner (where it says "Launching Clock" in your screenshot). When it shows it's stopped trying to do start-up tasks, you should be good to go.
If Eclsipse had been open for a while, then perhaps Eclipse is busy with other junk and calling it "Building workspace." Maybe it's having a hard time understanding what to do with one of your projects, so check for compiler errors. You can also try to "clean" your projects (Project -> Clean).
If that also fails...hmmm...I'm sure there's other options before you get to this point, but you might need to re-install Eclipse. I suppose there's a chance that in the deep dark corners of Eclipse, a file was corrupted, causing Eclipse to hang on a task that requires a missing/bad file. But before you go this far, make you get second or third opinions, because I might be missing some simpler cause of your Eclipse hanging than what I've listed already.
I found the solution.
I don't know what was the error and why it was displaying the Launcher window and stuck there. But, I forcefully stopped eclipse using Task Manager and then restarted it.
When restarted it took few minutes (more than usual time) and I was done with it. now it's working okay.
Re-installation of Eclipse also worked but i tried this before re-installing or upgrading.
I followed this tutorial and got Eclipse to recognize the program I'm debugging.
However, after setting a break point, and steering the application to the break point, the application just seems to ignore it.
The code continues merrily as if nothing happened, and I don't get to see the variables I'm trying to look at.
Unfortunately I don't know what info to include here, so if you need more information, just let me know in the comments.
You have to be careful with what you are doing. There are some pitfalls when debugging node applications in eclipse. Here are some tips that might help you.
Start your application with node --debug-brk your-script.js
Start the debugger in eclipse
Step over (F6) the first few require statements, that import the code you want to debug.
Set your breakpoints. (Be sure you don't set breakpoints in the source files you are currently editing. When debugging, there is a "Project" in your workspace that contains all the scripts that are loaded by node. Set your breakpoints in some of these files. Otherwise the breakpoints will be ignored. Most often you want to set breakpoints at the beginning of a callback.)
Then resume (F8) the script and it will pause at the first breakpoint it passes.
Start with that until debugging works for the first time. After that you can try more unconventional cases.