temyers / cucumber-jvm-parallel-plugin

Maven plugin to help running Cucumber features in parallel
Apache License 2.0
129 stars 122 forks source link

IT files are not being picked up in Maven for JUnit #27

Closed JasonSmiley208 closed 8 years ago

JasonSmiley208 commented 8 years ago

Even though I have this:

<includes>
    <include>**/*IT.class</include>
</includes>

The Tests are not being found. Can we just use the "Test.java" suffix instead? I can make a pull request for this, but please confirm the work allowed

JasonSmiley208 commented 8 years ago

Side note, this doesn't seem to be working for me, but, maybe its an error on my end:

<plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>${maven.surefire.version}</version>
                <executions>
                    <execution>
                        <id>acceptance-test</id>
                        <phase>integration-test</phase>
                        <goals>
                            <goal>test</goal>
                        </goals>
                        <configuration>
                            <forkCount>${parallel.test.count}</forkCount>
                            <reuseForks>true</reuseForks>
                            <includes>
                                <include>**/*IT.class</include>
                            </includes>
                        </configuration>
                    </execution>
                </executions>
            </plugin>
            <plugin>
                <groupId>com.github.temyers</groupId>
                <artifactId>cucumber-jvm-parallel-plugin</artifactId>
                <version>${cucumber.jvm.parallel.version}</version>
                <executions>
                    <execution>
                        <id>generateRunners</id>
                        <phase>validate</phase>
                        <goals>
                            <goal>generateRunners</goal>
                        </goals>
                        <configuration>
                            <!-- Mandatory -->
                            <!-- comma separated list of package names to scan for glue code -->
                            <glue>web, mobile, code, shared</glue>
                            <!-- These are the default values -->
                            <!-- Where to output the generated tests -->
                            <outputDirectory>${project.build.directory}/generated-test-sources/cucumber/</outputDirectory>
                            <!-- The diectory containing your feature files.  -->
                            <!--<featuresDirectory>src/test/resources/features/</featuresDirectory>-->
                            <!-- Directory where the cucumber report files shall be written  -->
                            <cucumberOutputDir>target/cucumber-parallel</cucumberOutputDir>
                            <!-- comma separated list of output formats -->
                            <format>json,junit,html,rerun</format>
                            <!-- CucumberOptions.strict property -->
                            <!--<strict>true</strict>-->
                            <!-- CucumberOptions.monochrome property -->
                            <monochrome>false</monochrome>
                            <!-- The tags to run, maps to CucumberOptions.tags property -->
                            <!--<tags>"@finished, @selenium, @parallel"</tags>-->
                            <!-- If set to true, only feature files containing the required tags shall be generated. -->
                            <!-- Excluded tags (~@notMe) are ignored. -->
                            <filterFeaturesByTags>true</filterFeaturesByTags>
                            <!-- Generate TestNG runners instead of JUnit ones. -->
                            <useTestNG>false</useTestNG>
                            <!-- The naming scheme to use for the generated test classes.  One of 'simple' or 'feature-title' -->
                            <namingScheme>feature-title</namingScheme>
                        </configuration>
                    </execution>
                </executions>
            </plugin>
JasonSmiley208 commented 8 years ago

Ok, so this is an error on my end. I was using the Test phase instead of the Integration-Test phase