[jbehave-dev] [jira] (JBEHAVE-1058) Hungarian language support
Title: Message Title Nagy Lszl created an issue JBehave / JBEHAVE-1058 Hungarian language support Issue Type: Improvement Assignee: Unassigned Created: 02/Dec/14 8:29 AM Priority: Minor Reporter: Nagy Lszl Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1058) Hungarian language support
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1058 Hungarian language support Change By: Mauro Talevi Fix Version/s: 3.9.6 Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1058) Hungarian language support
Title: Message Title Mauro Talevi commented on an issue Re: Hungarian language support Can you please provide a patch with the Hungarian version of keywords: https://github.com/jbehave/jbehave-core/blob/master/jbehave-core/src/main/resources/i18n/keywords_en.properties Add Comment JBehave / JBEHAVE-1058 Hungarian language support This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1056) ResolveToPackagedName path resolver is broken on Windows
Title: Message Title Mauro Talevi updated an issue JBehave / JBEHAVE-1056 ResolveToPackagedName path resolver is broken on Windows Change By: Mauro Talevi Affects Version/s: 3.x Affects Version/s: 3.9.5 Fix Version/s: 3.9.6 Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1056) ResolveToPackagedName path resolver is broken on Windows
Title: Message Title
Mauro Talevi commented on an issue
Re: ResolveToPackagedName path resolver is broken on Windows
Could you please provide an example project reproducing this behaviour, in particular the configuration you use.
Add Comment
JBehave / JBEHAVE-1056
ResolveToPackagedName path resolver is broken on Windows
Current implementation of 'org.jbehave.core.reporters.FilePrintStreamFactory.ResolveToPackagedName' is the following: {code:java} public static class ResolveToPackagedName extends AbstractPathResolver { public String resolveName(StoryLocation storyLocation , String extension) { String name = storyLocation .getPath().replace...
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1057) Jenkins plugin broken, unmatched dependency
Title: Message Title Lukas Dziadkowiec commented on an issue Re: Jenkins plugin broken, unmatched dependency Please have a look at the post at stackoverflow. I'm not author of the patched plugin. ... Have Jenkins 1.588 installed. I looked into source code, seems that they used a package which doesnt exists anymore link! What to do? ... java.lang.NoClassDefFoundError: com/thalesgroup/dtkit/metrics/hudson/api/descriptor/TestTypeDescriptor Add Comment JBehave / JBEHAVE-1057 Jenkins plugin broken, unmatched dependency Current available jenkins plugin has unmatched dependency. When installing it crashes with: WARNING: Failed to load org.jBehavePluginType$DescriptorImpl jbehave is then not available in product configuration for processing the output. I'm not only one with this problem. Here is a workaround which works great, modified jenkins package without the ... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1057) Jenkins plugin broken, unmatched dependency
Title: Message Title Mauro Talevi commented on an issue Re: Jenkins plugin broken, unmatched dependency The DTKit dependency comes from the Jenkins xunit plugin. Could you please try building the jbehave-jenkins-plugin with the latest updated version $ mvn clean install -Dxunit.plugin.version=1.92 to see if this fixes the problem? The currently used version of the xunit plugin is 1.62. Add Comment JBehave / JBEHAVE-1057 Jenkins plugin broken, unmatched dependency Current available jenkins plugin has unmatched dependency. When installing it crashes with: WARNING: Failed to load org.jBehavePluginType$DescriptorImpl jbehave is then not available in product configuration for processing the output. I'm not only one with this problem. Here is a workaround which works great, modified jenkins package without the ... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please
[jbehave-dev] [jira] (JBEHAVE-1053) Allow entire story to be restarted
Title: Message Title Brent Barker commented on an issue Re: Allow entire story to be restarted I updated the restarting.story to reflect these changes, and are in pull request https://github.com/jbehave/jbehave-core/pull/71 Add Comment JBehave / JBEHAVE-1053 Allow entire story to be restarted For selenium tests that keep the same browser / context throughout the story, there are countless things that can go wrong such as network latency, slow application, etc. Since a false positive can cause people to quickly lose trust in the tests, others advised that the story should restart x amount of times before failing the test. There is a way to... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] (JBEHAVE-1056) ResolveToPackagedName path resolver is broken on Windows
Title: Message Title
Dmitry Pelevin commented on an issue
Re: ResolveToPackagedName path resolver is broken on Windows
You can get project with the same configuration at GitHub:
https://github.com/OpsIT/berlin-clock
But I need to notice that gradlew.bat from this repository is broken and you have to replace it with gradle.bat from any other source, or just use standalone Gradle.
Before running this example project update com.ubs.opsit.interviews.BerlinClockFixture class to make test always pass:
public class BerlinClockFixture {
//...
@Then(the clock should look like $)
public void thenTheClockShouldLookLike(String theExpectedBerlinClockOutput) {
//assertThat(berlinClock.convertTime(theTime), is(equalTo(theExpectedBerlinClockOutput)));
Assert.assertTrue(true);
}
}
After this change you will be able to see failed tests (because of path resolver). Just run:
gradle check
If you wish to check the fact that the reason of this fail is path resolver - you need to update update com.ubs.opsit.interviews.support.BehaviouralTestEmbedder and replace path resolver with org.jbehave.core.reporters.FilePrintStreamFactory.ResolveToSimpleName implementation:
public final class BehaviouralTestEmbedder extends ConfigurableEmbedder {
//...
static class SandboxStoryReporterBuilder extends StoryReporterBuilder {
public SandboxStoryReporterBuilder() {
withCodeLocation(codeLocationFromClass(SandboxStoryReporterBuilder.class));
withDefaultFormats();
withFormats(HTML, TXT, CONSOLE);
withFailureTrace(true);
// you need to add the following line
withPathResolver(new FilePrintStreamFactory.ResolveToSimpleName());
}
}
}
Add Comment
