I have the following in a step "Given('I am logged in/as {string}')". This works and the test passes using either of the options in or as. It is however being flagged with the "Unable to find step for" error.
Previously no error was being displayed for this but has all of a sudden appeared. I am using cucumber in a wdio project and have not made any changes in this area in a while.
Related
I've just started using the tests functionality in the Python extension. I want to debug my test however when I hit the debug button in the tests extension the debugger runs but doesn't stop on a bug and display a red box with the error - it just reports a failed test in the debug console. This means I can't examine the variables that caused the error.
I've tried just running the normal debugger (not from within the tests section) on the test file but the same thing happens. I've tried the normal debugger on a non-test file and it works fine.
Is the test debugger supposed to work in the same way as the normal debugger, i.e. stop on a bug?
Edit:
Worth me mentioning that the bug is occurring in the function I'm testing rather than the test file itself
Edit_2:
I've tested break points and they seem to be working ok. Can't get a conditional one to work though
So I have anaconda installed and make a separate environment for all my projects. Normally I just use PYDEV to create a new interpreter pointing to the anaconda enviornment and load the project in eclipse and all is good. After doing the last one though 95% of the time I go to debug I keep getting the error
An internal error occurred during: "Debug Source Lookup".
java.lang.IllegalArgumentException
The other 5% it kind of works as I can follow one script or a function before it starts breaking.
I've tried reloading the project, interpreter and conda enviornment to no luck. All my past projects which use to work are also now giving the same error.
The funny thing is when I'm in the debug perspective though it does seem to be working (I can see the Variables and use the interactive console to test stuff), but anytime I try to step into, over ect I get the error (even though it does seem to be working). So for the image above I can go through the code fine until it tries to jump to the other file which throws the error, but if I step into it I can manually open that file and walk through the function (just each step throws the error) and still interact with the code which is in the position through the console.
Any ideas how to fix?
Well, it may be something specific to this use-case (for instance, if the code for some object is evaluated and the source code is not really available for the debugger this is actually expected).
Can you provide the full stacktrace from the error log? (see: http://www.pydev.org/faq.html#HowdoIReportaBUG for details on how to get it)
I have this error message: "Unable to find the apex source" after running a test in the Winter 16' version of Apex in Eclipse, when the project is located in a Git depository. I mean that the test runs. Even shows, at the end, coverage results but there is no System Debug Log information, neither User Debug Log information and instead of writing the name of the class next to the "green V" signaling that the test passed, nothing is written and when I click on it, I have this error message.
Note that when the project is simply in the Eclipse workspace (not in a Git depository), there is no problem, and there is also System Debug Log and User Debug Log information.
I've tried to configure the test running configuration, but with no success.
Is there anyone who knows how to handle that?
Resharper 9.0 says 'No tests found in selected solution items.' Yet there are over 100 tests.
I right click my solution in Visual Studio 2013 and click the "Run Unit Tests" option near the bottom of the context menu. I get the error message: "No tests found in selected solution items.".
Every once in a while, they do show up and run, but most of the time, they don't show up and I get the error message.
I have NCover installed and it has a 'Bolt Tests' tab from which I can run all the tests. However, I would prefer to run the tests from the main menu using Resharper.
Does anybody know why these tests aren't showing up and how to get them to consistently be discovered?
Thanks,
Curtis
Looks like the latest update of 9.1 solved the problem. Thanks everybody.
I'm trying to use Eclipse CDT's headlessbuild feature for integrating Eclipse with TeamCity. I use a command line call to build my projects as descriped in this question. If there is a compilation error, a message box pops up saying "Java was started but returned exit code=1". I'd rather not have this message but get the return code so I can process it further in my script. Is there any way to do this?
Thanks!
You can suppress the popup and redirect output to be included with your script:
Add "--launcher.suppressErrors" to your command line arguments for eclipse
The error needs to be tracked down in the GUI from what I can tell, because the headless mode doesn't support very good error reporting from sub-tasks yet.
From there I used output from the GUI-based build to narrow down why my project failed to build.
Sources:
http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg15343.html
http://www.eclipse.org/forums/index.php?t=msg&goto=481938&S=c88d71260a7d130eebdccb8f2e5537f2
http://www.eclipse.org/forums/index.php?t=msg&goto=481938&S=c88d71260a7d130eebdccb8f2e5537f2
https://bugs.eclipse.org/bugs/show_bug.cgi?id=209080#c21