一步一步的JBehave设置教程非常简单?

时间:2013-12-22 20:26:35

标签: java eclipse junit bdd jbehave

虽然我已阅读过许多关于如何使用JBehave的文章,但我无法让它工作。以下是我到目前为止所采取的步骤:

  1. 创建新的Java项目
  2. 下载了JBehave JAR文件版本3.6.8并将其添加到我的构建路径库
  3. 在我的工作区
  4. 中的测试源文件夹下创建了一个名为com.wmi.tutorials.bdd.stack.specs的包
  5. 将JBehave JAR文件添加到我的构建路径库配置
  6. 在上述包中创建了一个JBehave故事(StackBehaviourStories.story)
  7. 在上述包中创建了一个Java类(StackBehaviourStory.java)
  8. 在上述包中创建了一个Java类(StackBehaviourSteps.java)
  9. 导入了我的Java类中的Given,Named,Then,When annotations
  10. 在我的JBehave故事文件中写了两个不同的场景
  11. 然而,我无法让它工作/运行! =(

      

    故事档案:

    Narrative:
    In order to learn to with JBehave using Eclipse
    As a junior Java developer though senior in .Net and in BDD
    I want to define the behaviour of a custom stack
    
    Scenario: I push an item onto the stack
    Given I have an empty stack
    When  I push an item 'orange'
    Then  I should count 1
    
    Scenario: I pop from the stack
    Given I have an empty stack
    When  I push an item 'apple'
    And   I pop the stack
    Then  I should count 0
    
      

    故事类

    package com.wmi.tutorials.bdd.stack.specs
    
    import org.jbehave.core.configuration.MostUsefulConfiguration;
    import org.jbehave.core.junit.JUnitStory;
    
    public class StackBehaviourStory extends JUnitStory {
        @Override 
        public Configuration configuration() { return new MostUsefulConfiguration(); }
    
        @Override
        public InjectableStepsFactory stepsFactory() {
            return new InstanceStepsFactory(configuration()
                                          , new StackBehaviourSteps());   
        }
    }
    
      

    步骤类

    package com.wmi.tutorials.bdd.stack.specs
    
    import org.jbehave.core.annotations.Given;
    import org.jbehave.core.annotations.Named;
    import org.jbehave.core.annotations.Then;
    import org.jbehave.core.annotations.When;
    import org.jbehave.core.junit.Assert;
    
    public class StackBehaviourSteps {
        @Given("I have an empty stack")
        public void givenIHaveAnEmptyStack() { stack = new CustomStack(); }
    
        @When("I push an item $item")
        public void whenIPushAnItem(@Named("item") String item) { stack.push(item); }
    
        @Then("I should count $expected")
        public void thenIShouldCount(@Named("expected") int expected) {
            int actual = stack.count();
            if (actual != expected) 
                throw new RuntimeException("expected:"+expected+";actual:"+actual);
        }
    }
    

    我目前正在使用Eclipse Kepler(4.3)JEE以及使用JUnit,Google App Engine所需的一切,是的,按照Eclipse JBehave安装教程正确安装了JBehave。

    我无法让它发挥作用。那么如何使用Eclipse,JBehave和JUnit使其正常工作?

4 个答案:

答案 0 :(得分:10)

我知道我在这里参加派对已经很晚了,但是我发帖是因为这是我希望我一周前收到的信息,因为它会给我带来很多痛苦。我非常关注BDD的想法,但不幸的是,发现JBehave的文档有点像噩梦,特别是在涉及到Maven集成时。此外,我在他们的网站和其他地方发现的很多代码都不起作用。通过反复试验和许多教程,我能够拼凑出以下内容。它在Maven和Eclipse中运行,有一个将故事映射到步骤文件的绑定类,并且能够找到位于src / test / resources中的故事文件。

这是一个有效的pom文件:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>com.projectvalis.st1</groupId>
  <artifactId>st1</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>jar</packaging>

  <name>st1</name>
  <url>http://maven.apache.org</url>

  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
  </properties>

  <build>
    <pluginManagement>
      <plugins>

        <plugin>
      <artifactId>maven-compiler-plugin</artifactId>
        <version>2.3.2</version>
        <configuration>
          <source>1.8</source>
          <target>1.8</target>
        <compilerArgument></compilerArgument>
          </configuration>
        </plugin>

       <plugin>  
         <groupId>org.apache.maven.plugins</groupId>  
         <artifactId>maven-failsafe-plugin</artifactId>  
         <version>${failsafe.and.surefire.version}</version>  
         <executions>  
           <execution>  
             <id>integration-test</id>  
             <goals>  
               <goal>integration-test</goal>  
               <goal>verify</goal>  
             </goals>  
           </execution>  
         </executions>  
         <configuration>  
           <includes>  
             <include>**/*Test.java</include>  
           </includes>  
         </configuration>  
       </plugin>

       <plugin>
        <groupId>org.jbehave</groupId>
        <artifactId>jbehave-maven-plugin</artifactId>
        <version>4.0.2</version>
            <executions>  
                <execution>  
                    <id>run-stories-as-embeddables</id>  
                    <phase>integration-test</phase>  
                    <configuration>  

                    <includes>  
                        <include>**/*Test.java</include>  
                    </includes>  
                    <ignoreFailureInStories>false</ignoreFailureInStories>  
                    <ignoreFailureInView>false</ignoreFailureInView>  

                        <systemProperties>
                            <property>
                                <name>java.awt.headless</name>
                                <value>true</value>
                            </property>
                        </systemProperties>


                    </configuration>  
                    <goals>  
                    <goal>run-stories-as-embeddables</goal>  
                    </goals>  
            </execution>  
             </executions>
       </plugin>

      </plugins>
    </pluginManagement>
  </build>


  <dependencies>

    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>4.12</version>
      <scope>test</scope>
    </dependency>

    <dependency>
      <groupId>org.slf4j</groupId>
      <artifactId>slf4j-api</artifactId>
      <version>1.7.7</version>
    </dependency>

    <dependency>
      <groupId>ch.qos.logback</groupId>
      <artifactId>logback-classic</artifactId>
      <version>1.0.1</version>
    </dependency>

    <dependency>
      <groupId>ch.qos.logback</groupId>
      <artifactId>logback-core</artifactId>
      <version>1.0.1</version>
    </dependency>

    <dependency>
        <groupId>org.apache.commons</groupId>
        <artifactId>commons-lang3</artifactId>
        <version>3.4</version>
    </dependency>

    <dependency>
        <groupId>org.jbehave</groupId>
        <artifactId>jbehave-core</artifactId>
        <version>4.0.2</version>
    </dependency>

  </dependencies>
</project>

这是一个示例故事文件

Narrative:
In order to work with files to compress
As a guy who wants to win a bet with cameron
I want to ensure files are ingested and processed in the manner in which the
methods in the ingest class purport to process them. 

Scenario:  Simple test to give JBehave a test drive
Given a file, a.log
When the caller loads the file as a byte array
Then the byte array that is returned contains the correct number of bytes.

这是一个示例步骤文件

package com.projectvalis.compUtils.tests.ingest;

import java.io.File;

import org.jbehave.core.annotations.Given;
import org.jbehave.core.annotations.Named;
import org.jbehave.core.annotations.Then;
import org.jbehave.core.annotations.When;
import org.jbehave.core.steps.Steps;
import org.junit.Assert;

import com.projectvalis.compUtils.util.fileIO.Ingest;


    /**
     * BDD tests for the ingest class
     * @author funktapuss
     *
     */
    public class LoadByteSteps extends Steps {

        private String fNameS;
        private byte[] byteARR;

        @Given("a file, $filename")
        public void setFileName(@Named("filename") String filename) {
            File file = new File(getClass().getResource("/" + filename).getFile());
            fNameS = file.getPath();
        }

        @When("the caller loads the file as a byte array")
        public void loadFile() {
            byteARR = Ingest.loadFile(fNameS);
        }

        @Then("the byte array that is returned contains the "
                + "correct number of bytes.") 
        public void checkArrSize() {
            File file = new File(fNameS);
            Assert.assertTrue(
                    "loading error - "
                    + "the file and the resultant byte array are different sizes!", 
                    (long)byteARR.length == file.length());
        }


    }

这里是通用跑步者

package com.projectvalis.compUtils.tests.runner;


import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;

import org.jbehave.core.configuration.Configuration;
import org.jbehave.core.configuration.MostUsefulConfiguration;
import org.jbehave.core.io.CodeLocations;
import org.jbehave.core.io.LoadFromClasspath;
import org.jbehave.core.io.StoryFinder;
import org.jbehave.core.junit.JUnitStories;
import org.jbehave.core.reporters.Format;
import org.jbehave.core.reporters.StoryReporterBuilder;
import org.jbehave.core.steps.InjectableStepsFactory;
import org.jbehave.core.steps.InstanceStepsFactory;
import org.jbehave.core.steps.Steps;

import com.projectvalis.compUtils.tests.ingest.LoadByteSteps;



/**
 * generic binder for all JBehave tests. Binds all the story files to the 
 * step files. works for both Eclipse and Maven command line build.  
 * @author funktapuss
 *
 */
public class JBehaveRunner_Test extends JUnitStories {

    @Override 
    public Configuration configuration() { 
        return new MostUsefulConfiguration()            
                .useStoryLoader(
                        new LoadFromClasspath(this.getClass().getClassLoader()))
                .useStoryReporterBuilder(
                        new StoryReporterBuilder()
                            .withDefaultFormats()
                            .withFormats(Format.HTML, Format.CONSOLE)
                            .withRelativeDirectory("jbehave-report")
                );
    }

    @Override
    public InjectableStepsFactory stepsFactory() {
        ArrayList<Steps> stepFileList = new ArrayList<Steps>();
        stepFileList.add(new LoadByteSteps());

        return new InstanceStepsFactory(configuration(), stepFileList);       
    }

    @Override
    protected List<String> storyPaths() {
       return new StoryFinder().
               findPaths(CodeLocations.codeLocationFromClass(
                       this.getClass()), 
                       Arrays.asList("**/*.story"), 
                       Arrays.asList(""));

    }

}

跑步者住在src / test / java / /tests.runner中。 摄取测试存在于src / test / java / /tests.ingest中。 故事文件存在于src / test / resources / stories中。

据我所知,JBehave有很多选择,所以这当然不是唯一的做法。将此视为一个可以让您快速启动并运行的模板。

完整来源位于github

答案 1 :(得分:4)

逐步紧跟jbehave Getting Started教程,运行故事部分说: [...] ICanToggleACell.java类将允许自己作为JUnit运行测试

这意味着构建路径中需要JUnit库。

使用Eclipse:

  1. 选择当前项目并右键单击它,构建路径配置构建路径...
  2. [当前项目] Java构建路径的属性,单击 [添加库...]
  3. 添加库,选择 JUnit ,点击 [下一步]
  4. JUnit Library,JUnit库版本,选择您要使用的版本,单击 [Finish]
  5. Java Build Path,单击 [确定]
  6. Project Explorer,选择您的ICanToggleACell.java类,右键单击它,然后运行为,然后单击JUnit Test
  7. 因此,这与上面的示例代码相同。在将适当的库添加到Java构建路径之后,StackBehaviourStory.java类应该让自己作为JUnit测试运行。

答案 2 :(得分:0)

就我而言,我已经从Steps(来自jbehave core)扩展了我的Steps类

答案 3 :(得分:0)

我已将JunitStory更新为JunitStories,并且可以使用

公共类StackBehaviourStory扩展了JUnitStory ---> JunitStories