Trying to run SpecFlow test I receive an error:
Missing resource DefaultSkeletonTemplates.sftemplates
I have:
The feature file
Feature class (generated code)
Feature step
All classes bound
What could be the problem?
I've run into this issue when the step isn't defined or can't be found.
You can run the test using statlight.exe on the command line to see SpecFlow's detailed output on the console.
In the feature file, right-click on the step and select "Go To Step Definition".
If a step can't be found, a message appears with the text "No matching step binding found for this step! Do you want to copy the step binding skeleton to the clipboard?"
Select Yes to copy the code for the step to the clipboard.
Then paste the code in a SpecFlow bound class and try running the scenario again.
Related
I am trying to see configuration page of the KNIME node which i just published to my KNIME analytics tool.
Getting error "Error while creating node dialog for 'Readadwords': The configName must be a non-empty string" where Readadwords is my node dialog class which i created in eclipse.
Either in my Nodemodel or Nodedialog there is not a single config and i have defaulted it some or other string value.
Can some one help me where to look to fix my error and also please let me know if i can debug my knime plugin from eclipse rather than doing it in Analytics tool.
Debugging is explained in their developer guide, this page is the most relevant for that.
When you save your settings you have not specified the key for your config, that is what this error message is about. Like in this place assuming "" were used instead of "colName", I would expect a similar error message.
Issue is KNIME is not picking up the changes i have done to the code and i had to change version in plugin.xml file then it started working after copying new jar file to dropins folder of KNIME
When i select any class and testmethod as Junit 4 test case, it disapears as soon as i click something else and a default test case comes up that gives me a null exception,for eg: groovy test case/Selenese Test Case. I require the Groovy Library for my test case.
This happens only in Jmeter 2.13, but this unchecking thing does not happen in Jmeter 2.11, but i need to use the Backend Listener that is only in Jmeter 2.13.
Image that shows the selection of the junit testcase
Image that shows that the test selected is rechecked by some default groovy test case/Selenese Test case
Screenshot of jmeter using Nightly Build
I need a solution to this, please help me out. Thank you
It appears you are facing a NPE in a process related to undo/redo feature:
https://github.com/apache/jmeter/blob/v2_13/src/core/org/apache/jmeter/gui/GuiPackage.java#L853
Could you try to remove jmeter-plugins 1.4.0 which is a developer snapshot.
Try without it, and if it works report a bug to jmeter-plugins.org
Then try with jmeter-plugins-1.3.1 which is the stable version, it might work but the bug might also be in it.
I created bug:
- https://bz.apache.org/bugzilla/show_bug.cgi?id=58795
It is now fixed in nightly build so you will have more informations to provide to jmeter-plugins or jmeter.
To use nightly build:
http://jmeter.apache.org/nightly.html
Download the _bin and _lib files
Unpack the archives into the same directory structure
The other archives are not needed to run JMeter.
Need to run a job in Jenkins after successfully running the tests it needs to perform as post-build action for generating test reports
For this i have configured
Publish JUnit test result report
In the field
Test Report XMLs: continuum/*/target/surefire-reports/*TestSuite.xml
'continuum/*/target/surefire-reports/TestSuite.xml' doesn't match anything: 'continuum' exists but not 'continuum//target/surefire-reports/*TestSuite.xml'
Can you please help me out in resolving the error....??
I assume you have an 'Execute JUnit tests' Build step. This will produce a JUnit XML file to a location you specify, say, TestOutput/junitresults.xml.
In the 'Publish JUnit test result report' Post Build step you just need to specify TestOutput/junitresults.xml.
As long as your tests executed and produced the output file the Post Build step won't fail to publish it, whether the tests failed or not.
You shouldn't be trying to publish files in the surefire-reports directory unless that it where you told JUnit to write its output file. Normally you wouldn't.
If you want to make it even simpler just tell JUnit to write its output file to the Jenkins WORKSPACE root by removing the TestOutput/ and just specify junitresults.xml.
I'm stuck configuring tests for Jenkins. In the Publish JUnit test result report I have test-reports/*.xml but I'm getting the error:
'test-reports/*.xml' doesn't match anything: 'test-reports' exists but not 'test-reports/*.xml'
When I try */.xml I get:
Did not manage to validate **/*.xml (may be too slow)
When I throw an .xml file into test-reports folder manually it is deleted after the build.
What do?
It might actually be an issue with XCode. We figured out that it was actually skipping the application tests and it just wasn't evident anywhere on Jenkins' console output.
I've set up a FlexUnit test on my Adobe Air project and want to test some functionality that uses NativeProcess. When I run the test it gives this error:
Error: Error #3219: The NativeProcess could not be started. 'Not supported in current profile.'
This is because the FlexUnitApplication-app.xml doesn't have this line enabling NativeProcess:
<supportedProfiles>extendedDesktop</supportedProfiles>
The problem is that FlexUnitApplication-app.xml gets auto generated each time it builds without that line.
I've been able to get it to work by running the test using "Run all tests" from the FlexUnit Results window and letting it fail. Then I add the line to FlexUnitApplication-app.xml in bin-debug and running the tests again. If anything in the project changes I need to repeat these steps so this isn't ideal.
You need to add it to your launch profile: click on the little arrow next to the bug icon and select Debug Configurations (or select the project properties > run/debug settings)
Choose the launch configuration you want to edit on the left of the new dialog. In the "main" tab of this config, the last option is "Profile", you can switch between "desktop" and "extendedDesktop" there.