| # | Summary | Reporter | Assignee | Status | Type | Created | Fix Version |
|---|---|---|---|---|---|---|---|
| 307 | klieber | klieber | open | 2016-09-14 | 3.0 | ||
| 306 | klieber | klieber | closed | 2016-09-14 | 3.0 | ||
| 305 | Next major version will only support Java 8. | klieber | klieber | closed | 2016-09-14 | 3.0 | |
| 254 | Tests/suits that are disabled with xit/xdescribe yields failures when run with the jasmine:test maven goal (works fine with the jasmine:bdd goal). | kjarnet | klieber | closed | bug | 2014-08-27 | 2.0 |
| 221 | gejgalis | closed | enhancement | 2014-01-22 | 1.3.1.5 | ||
| 220 | **jasmine-maven-plugin** is not friendly for projects using [WebJars](http://www.webjars.org/) or other dependent artifacts containing JS files. It is required to unpack dependencies to temporary directory to load used libraries within test page. [wro4j](https://code.google.com/p/wro4j/wiki/ResourceTypes) allows accessing WebJars using [webjars-locator](https://github.com/webjars/webjars-locator) queries: // pom.xml <dependency> <groupId>org.webjars</groupId> <artifactId>jquery</artifactId> <version>1.10.2</version> </dependency> // wro.xml <js>webjar:jquery.js</js> `webjar:jquery.js` is resolved as `META-INF/resources/webjars/jquery/1.10.2/jquery.js` and used for processing. I propose to add similar functionality to plugin server: // jasmine-maven-plugin configuration <preloadSources> <!-- /webjar/ context uses webjars-locator queries --> <source>webjar/jquery.js</source> <!-- /classpath/ context matches exact path from dependent *.jar or *.war --> <source>classpath/META-INF/resources/webjars/jquery/1.10.2/jquery.js</source> ... </preloadSources> It means you may access JS files at following URLs: http://localhost:8234/webjar/jquery.js http://localhost:8234/classpath/META-INF/resources/webjars/jquery/1.10.2/jquery.js I'm going to send pull request soon. | gejgalis | closed | enhancement | 2014-01-21 | 1.3.1.5 | |
| 217 | Hi guys, I'm trying to run my jasmine tests with your plugin using Selenium's Chrome WebDriver. Based on [this documentation](https://sites.google.com/a/chromium.org/chromedriver/capabilities) it appears that WebDriverCapabilities for Google Chrome must be set by placing key-value pairs in a ChromeOptions Map<String, Object> which is then placed in webDriverCapabilities in the following way: ``` Map<String, Object> chromeOptions = new Map<String, Object>(); chromeOptions.put("binary", "/usr/lib/chromium-browser/chromium-browser"); DesiredCapabilities capabilities = DesiredCapabilities.chrome(); capabilities.setCapability(ChromeOptions.CAPABILITY, chromeOptions); WebDriver driver = new ChromeDriver(capabilities); ``` Looking at the source for the plugin I see that on line 21 of WebDriverFactory.java, webDriverCapabilities is a Map of <String, String>. Am I correct in thinking that it's impossible to configure ChromeDriver with this plugin? When I run 'mvn jasmine:test -X' I see the following in my debug output ``` [DEBUG] (f) webDriverCapabilities = {ChromeOptions.CAPABILITY=null} ``` Here's the section of my pom that uses your plugin. ``` <plugin> <groupId>com.github.searls</groupId> <artifactId>jasmine-maven-plugin</artifactId> <version>1.3.1.3</version> <executions> <execution> <id>Run jasmine tests</id> <phase>test</phase> <goals> <goal>test</goal> </goals> </execution> </executions> <configuration> <webDriverClassName>org.openqa.selenium.chrome.ChromeDriver</webDriverClassName> <jsSrcDir>${basedir}/build/javascripts</jsSrcDir> <jsTestSrcDir>${basedir}/spec/javascripts</jsTestSrcDir> <specExcludes> <exclude>**/fixture.js</exclude> <exclude>**/sunrun.js</exclude> </specExcludes> <webDriverCapabilities> <ChromeOptions.CAPABILITY> <binary>'/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome'</binary> <args>['crash-test']</args> </ChromeOptions.CAPABILITY> </webDriverCapabilities> </configuration> </plugin> ``` | chrishenzie | klieber | closed | enhancement | 2014-01-07 | 1.3.1.4 |
| 216 | Adding support for com.github.klieber.phantomjs-maven-plugin | worldjoe | closed | documentation | 2013-12-31 | 1.3.1.4 | |
| 215 | fixes #87 - with alternative approach as suggested in https://github.com/searls/jasmine-maven-plugin/pull/87 Coffee Script compilation can be disabled when using REQUIRE_JS spec runner template by setting 'coffeeScriptCompilationEnabled' to false: <specRunnerTemplate>REQUIRE_JS</specRunnerTemplate> <!-- Need to disable compilation within this plugin as RequireJS will compile the CoffeeScript with an AMD loader plugin --> <coffeeScriptCompilationEnabled>false</coffeeScriptCompilationEnabled> | aphethean | closed | enhancement | 2013-12-31 | 1.3.1.4 | |
| 210 | updated to jasmine version 2.0.0.rc5 Since I'm completely new to this, some review would be appropriate ;) ... ** only tested with FIREFOX_3_6 & INTERNET_EXPLORER_8 ** jasmine:test goal works now with console.js (provided by jasmine team in dist) instead of custom buildReport.js, however output of console.js is less verbose ** jasmine:bdd goal works ** surefire reports are correctly generated but output may need some tuning ... ** tests (src/test/java) should be updated to reflect changes | elslander-cedric | closed | enhancement | 2013-11-27 | 2.0 | |
| 209 | Hi team, I have recently made a syntax mistake while writing unit test: `describe('some class', function {});` Is it expected that this file is just skipped and there is no error output, if it is run through mvn test ? | VladyslavGoloshchapov | klieber | closed | 1.3.1.1 | 2013-11-22 | 1.3.1.4 |
| 208 | allows to pass phantom js and ghostdriver arguments as String arrays to phantom js drivers - fixes inability to pass arguments as described in Issue #200 of searls/jasmine-maven-plugin | tomdw | closed | enhancement | 2013-11-20 | 1.3.1.4 | |
| 206 | We have a following setup: 1. customConfigurationRunner runner is first extracted to target/ directory (as it comes from external dependency) 2. configure jasmine maven plugin to use this customConfigurationRunner 3. launch the build using mvn -DskipTests install Jasmine maven plugin fails at not finding the file Error message: com.github.searls:jasmine-maven-plugin:1.3.1.2:test (default) on project XY: Invalid value for parameter 'customRunnerConfiguration'. File does not exist: XY/target/jasmine/src/ext/requirejs-config.js The code should not check this condition if -DskipTests is set | marosurbanec | klieber | closed | 1.3.1.2 | 2013-11-18 | 1.3.1.4 |
| 202 | ddumont | closed | enhancement | 2013-11-05 | 1.3.1.4 | ||
| 200 | Looking at the source code of ```org.openqa.selenium.phantomjs.PhantomJSDriverService#findCLIArgumentsFromCaps```, it seems that it expects the capability to be in the form of either ```String[]``` or a ```Collection```. As the type passed by ```jasmine-maven-plugin``` is always ```String```, this test will always fail and thus it is not currently possible to specify ```phantomjs.cli.args```. This could perhaps be seen as a bug in PhantomJSDriverService, which should allow a String to be used as a single argument. | joebandenburg | klieber | closed | 1.3.1.1 | 2013-10-24 | 1.3.1.4 |
| 199 | Update project dependencies in pom.xml and Gemfile | klieber | klieber | closed | 2013-10-02 | 1.3.1.3 | |
| 198 | ... the RemoteWebDriver. | skrall | klieber | closed | enhancement | 2013-09-23 | 1.3.1.4 |
| 195 | klieber | klieber | closed | documentation | 2013-08-27 | 1.3.1.3 | |
| 192 | Prepare for the release of Jasmine 2.0.0. The 2nd release candidate was published a couple of weeks ago. https://groups.google.com/forum/m/#!topic/jasmine-js/it1EtF-cI00 | klieber | klieber | closed | enhancement | 2013-08-17 | 2.0 |
| 191 | ddumont | klieber | closed | enhancement | 2013-08-15 | 1.3.1.3 | |
| 186 | magnusstahre | closed | 2013-07-31 | 1.3.1.3 | |||
| 184 | It seems Internet explorer needs the client to be on an HTTPS server in order to connect to HTTPS, which makes sense (oddly, chrome and firefox while using this plugin don't care somehow). Is there an option to enable SSL for the jetty server? Or is it possible to at least override the configuration of the jetty server being used? I'm not exactly a maven expert so am not sure if this is possible.. | gerahe | klieber | closed | enhancement | 2013-07-11 | 1.3.1.4 |
| 179 | Makes Javascript [packaged into META-INF/resources classpath JARs](http://alexismp.wordpress.com/2010/04/28/web-inflib-jarmeta-infresources/) available during testing. | cgalesanco | klieber | closed | enhancement | 2013-05-13 | 1.3.1.5 |
| 176 | when I run 1.3.1.1 with a configuration of <webDriverClassName>org.openqa.selenium.firefox.FirefoxDriver</webDriverClassName> it breaks with the following exception. I found https://code.google.com/p/selenium/issues/detail?id=5470 discussing a similar stacktrace but I was unable to resolve it by adding selenium 2.32 as the dependency of jasmine-maven-plugin using this code: ```xml <plugin> <groupId>com.github.searls</groupId> <artifactId>jasmine-maven-plugin</artifactId> <version>1.3.1.1</version> <!-- ... SNIP... --> <dependencies> <dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId>selenium-java</artifactId> <version>2.32.0</version> </dependency> </dependencies> </plugin> ``` This is the error printed by maven when running install or jasmine:test ``` [ERROR] Failed to execute goal com.github.searls:jasmine-maven-plugin:1.3.1.1:test (default) on project myproject: The jasmine-maven-plugin encountered an exception: [ERROR] java.lang.reflect.InvocationTargetException [ERROR] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [ERROR] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [ERROR] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [ERROR] at java.lang.reflect.Constructor.newInstance(Constructor.java:525) [ERROR] at com.github.searls.jasmine.driver.WebDriverFactory.createCustomWebDriver(WebDriverFactory.java:67) [ERROR] at com.github.searls.jasmine.driver.WebDriverFactory.createWebDriver(WebDriverFactory.java:47) [ERROR] at com.github.searls.jasmine.mojo.TestMojo.createDriver(TestMojo.java:92) [ERROR] at com.github.searls.jasmine.mojo.TestMojo.executeSpecs(TestMojo.java:77) [ERROR] at com.github.searls.jasmine.mojo.TestMojo.run(TestMojo.java:43) [ERROR] at com.github.searls.jasmine.mojo.AbstractJasmineMojo.execute(AbstractJasmineMojo.java:387) [ERROR] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) [ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) [ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) [ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) [ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) [ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) [ERROR] at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) [ERROR] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [ERROR] at java.lang.reflect.Method.invoke(Method.java:601) [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) [ERROR] Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.io.IOUtils.closeQuietly(Ljava/io/Closeable;)V [ERROR] at org.openqa.selenium.firefox.FirefoxProfile.updateUserPrefs(FirefoxProfile.java:333) [ERROR] at org.openqa.selenium.firefox.FirefoxProfile.layoutOnDisk(FirefoxProfile.java:450) [ERROR] at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:77) [ERROR] at org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:244) [ERROR] at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110) [ERROR] at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:188) [ERROR] at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:183) [ERROR] at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:100) [ERROR] ... 31 more [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.github.searls:jasmine-maven-plugin:1.3.1.1:test (default) on project myproject: The jasmine-maven-plugin encountered an exception: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at com.github.searls.jasmine.driver.WebDriverFactory.createCustomWebDriver(WebDriverFactory.java:67) at com.github.searls.jasmine.driver.WebDriverFactory.createWebDriver(WebDriverFactory.java:47) at com.github.searls.jasmine.mojo.TestMojo.createDriver(TestMojo.java:92) at com.github.searls.jasmine.mojo.TestMojo.executeSpecs(TestMojo.java:77) at com.github.searls.jasmine.mojo.TestMojo.run(TestMojo.java:43) at com.github.searls.jasmine.mojo.AbstractJasmineMojo.execute(AbstractJasmineMojo.java:387) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.io.IOUtils.closeQuietly(Ljava/io/Closeable;)V at org.openqa.selenium.firefox.FirefoxProfile.updateUserPrefs(FirefoxProfile.java:333) at org.openqa.selenium.firefox.FirefoxProfile.layoutOnDisk(FirefoxProfile.java:450) at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:77) at org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:244) at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110) at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:188) at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:183) at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:100) ... 31 more at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: The jasmine-maven-plugin encountered an exception: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at com.github.searls.jasmine.driver.WebDriverFactory.createCustomWebDriver(WebDriverFactory.java:67) at com.github.searls.jasmine.driver.WebDriverFactory.createWebDriver(WebDriverFactory.java:47) at com.github.searls.jasmine.mojo.TestMojo.createDriver(TestMojo.java:92) at com.github.searls.jasmine.mojo.TestMojo.executeSpecs(TestMojo.java:77) at com.github.searls.jasmine.mojo.TestMojo.run(TestMojo.java:43) at com.github.searls.jasmine.mojo.AbstractJasmineMojo.execute(AbstractJasmineMojo.java:387) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.io.IOUtils.closeQuietly(Ljava/io/Closeable;)V at org.openqa.selenium.firefox.FirefoxProfile.updateUserPrefs(FirefoxProfile.java:333) at org.openqa.selenium.firefox.FirefoxProfile.layoutOnDisk(FirefoxProfile.java:450) at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:77) at org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:244) at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110) at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:188) at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:183) at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:100) ... 31 more at com.github.searls.jasmine.mojo.AbstractJasmineMojo.execute(AbstractJasmineMojo.java:391) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at com.github.searls.jasmine.driver.WebDriverFactory.createCustomWebDriver(WebDriverFactory.java:67) at com.github.searls.jasmine.driver.WebDriverFactory.createWebDriver(WebDriverFactory.java:47) at com.github.searls.jasmine.mojo.TestMojo.createDriver(TestMojo.java:92) at com.github.searls.jasmine.mojo.TestMojo.executeSpecs(TestMojo.java:77) at com.github.searls.jasmine.mojo.TestMojo.run(TestMojo.java:43) at com.github.searls.jasmine.mojo.AbstractJasmineMojo.execute(AbstractJasmineMojo.java:387) ... 21 more Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.io.IOUtils.closeQuietly(Ljava/io/Closeable;)V at org.openqa.selenium.firefox.FirefoxProfile.updateUserPrefs(FirefoxProfile.java:333) at org.openqa.selenium.firefox.FirefoxProfile.layoutOnDisk(FirefoxProfile.java:450) at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:77) at org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:244) at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110) at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:188) at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:183) at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:100) ... 31 more [ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException ``` | patrick-a-cavanaugh | klieber | closed | 1.3.1.1 | 2013-04-19 | 1.3.1.2 |
| 175 | Hi I'm using jasmine-maven-plugin 1.3.1.1. The jasmine:test goal executed successfully and all specs are passed. However when I execute jasmine:bdd and open the browser with the specified port, nothing is shown in browser. Do you have any idea how to troubleshoot this? The following is my plugin configuration, <plugin> <groupId>com.github.searls</groupId> <artifactId>jasmine-maven-plugin</artifactId> <executions> <execution> <goals> <goal>test</goal> </goals> </execution> </executions> <configuration> <debug>true</debug> <jsSrcDir>${project.basedir}/src/main/webapp/js</jsSrcDir> <jsTestSrcDir>${project.basedir}/src/test/js</jsTestSrcDir> <specRunnerTemplate>REQUIRE_JS</specRunnerTemplate> <customRunnerConfiguration>${project.build.testOutputDirectory}/config.txt</customRunnerConfiguration> <preloadSources> <source>${project.build.directory}/dependency/js/lib/require.js</source> </preloadSources> </configuration> </plugin> | mazjer | klieber | closed | 1.3.1.1 | 2013-04-18 | 1.3.1.2 |
| 173 | * jetty = 8.1.10.v20130312 * maven-core = 3.0.5 * commons-logging = 1.1.2 * powermock = 1.4.12 | klieber | klieber | closed | 2013-04-08 | 1.3.1.1 | |
| 172 | This pull request uses `plexus-resources` to load File parameters from either a file path, class path, or URL. | klieber | klieber | closed | enhancement | 2013-04-05 | 1.3.1.1 |
| 171 | klieber | klieber | closed | 1.3.1.0 | 2013-04-04 | 1.3.1.1 | |
| 170 | I have a Jenkins server on a Windows 7 64-bit machine that is building the [OpenSocial Explorer](https://github.com/OpenSocial/explorer) project using maven. The Jenkins installer for Windows placed JENKINS_HOME at C:\Program Files (x86)\Jenkins, which in turn means that the OpenSocial Explorer's workspace is at C:\Program Files (x86)\Jenkins\jobs\OpenSocial Explorer\workspace. This is causing issues with the generation of specs. They are being generated with absolute URLs instead of relative URLs. For instance, if I run "mvn jasmine:bdd" and go to the resulting page, I see this in the page source: ```javascript var specs = ['file:/c:/Program%20Files%20(x86)/Jenkins/jobs/OpenSocial%20Explorer/workspace/opensocial-explorer-webcontent/src/test/javascript/DropDownMenuTest.js', 'file:/c:/Program%20Files%20(x86)/Jenkins/jobs/OpenSocial%20Explorer/workspace/opensocial-explorer-webcontent/src/test/javascript/LoadingTest.js', 'file:/c:/Program%20Files%20(x86)/Jenkins/jobs/OpenSocial%20Explorer/workspace/opensocial-explorer-webcontent/src/test/javascript/ModalDialogTest.js', 'file:/c:/Program%20Files%20(x86)/Jenkins/jobs/OpenSocial%20Explorer/workspace/opensocial-explorer-webcontent/src/test/javascript/editorarea/EditorAreaTest.js', 'file:/c:/Program%20Files%20(x86)/Jenkins/jobs/OpenSocial%20Explorer/workspace/opensocial-explorer-webcontent/src/test/javascript/gadgetarea/GadgetAreaTest.js']; ``` What I expect to see (and what I see on a working system) are relative paths like this: ```javascript var specs = ['spec/javascript/DropDownMenuTest.js', 'spec/javascript/LoadingTest.js', 'spec/javascript/ModalDialogTest.js', 'spec/javascript/editorarea/EditorAreaTest.js', 'spec/javascript/editorarea/EditorToolbarTest.js', 'spec/javascript/gadgetarea/GadgetAreaTest.js']; ``` On the system that is encountering the error, I can reproduce the error by running maven from the command line in the Jenkins workspace folder. I can also move the workspace folder for the Jenkins job to the "C:\" directory and running "mvn jasmine:bdd" works. Therefore, there seems to be an issue with the path. If I set a custom workspace path in Jenkins such that the build workspace is at "C:\\.jenkins\jobs\OpenSocial Explorer\workspace", the builds will complete normally. | sieverssj | klieber | closed | 1.3.1.0 | 2013-04-03 | 1.3.1.1 |
| 169 | After switching from 1.2.0.0 i am unable to run test using jasmine:bdd. I want to preload sources from target of my project but path are badly generated and included files cannot be opened in browser. Its only applied to path with ${project.build.directory} included: ```` <plugin> <groupId>com.github.searls</groupId> <artifactId>jasmine-maven-plugin</artifactId> <version>1.3.1.0</version> <configuration> <preloadSources> <source>${project.build.directory}/${project.build.finalName}/js/jquery.js</source> </preloadSources> ... </configuration> </plugin> ```` this configuration generates SpecRunner.html with scripts included like this: ```` <script type="text/javascript" src="file:/home/mlip/projects/ciber/target/ciber/js/jquery.js"></script> ```` This makes browser unable to open them when running tests. When changed version to 1.2.0.0 generated path is good: ```` <script type="text/javascript" src="target/ciber/js/jquery.js"></script> ```` | michal-lipski | klieber | closed | 1.3.1.0 | 2013-04-03 | 1.3.1.1 |
| 163 | Adds a new configuration parameter `autoRefreshInterval`. The default value of the parameter is `0` which means that the test runner should not auto refresh. If the parameter is set to a positive number then the test runner will automatically refresh at that interval (in seconds). The parameter only applies to the `jasmine:bdd` goal and will be ignored by the `jasmine:test` goal. Example config with auto refresh set to every 5 seconds: ```xml <plugin> <groupId>com.github.searls</groupId> <artifactId>jasmine-maven-plugin</artifactId> <version>${jasmine-maven-plugin.version}</version> <configuration> <autoRefreshInterval>5</autoRefreshInterval> </configuration> </plugin> ``` You can also set the refresh interval by command line which might be more useful: ``` mvn jasmine:bdd -Djasmine.autoRefreshInterval=5 ``` | klieber | klieber | closed | enhancement | 2013-03-17 | 1.3.1.1 |
| 162 | I try to keep my javascript code separate from third party libraries. Something like src main/js myJavascript.js ... webapp/js/lib jquery.js .... test/js myJavascriptSpec.js So I need for those libraries to be available during unit testing. I've modified the pluging to enable serving the files in the path *jsLibSrcDir* under the *libDirectoryName* path. The above directory layout will match this configuration: ``` xml <configuration> <jsSrcDir>src/main/js</jsSrcDir> <jsTestSrcDir>src/test/js</jsTestSrcDir> <jsLibSrcDir>src/main/js/lib</jsLibSrcDir> <libDirectoryName>js/lib</libDirectoryName> ``` | cgalesanco | klieber | closed | enhancement | 2013-03-15 | 1.3.1.5 |
| 160 | Newest HTMLUnit removed the rhino globals we were using to detect if we were running under HTMLUnit so things reverted to slow runnning. This will make it use a long updateInterval when running with the JsApiReporter which should only be when running the test goal. | dtabuenc | klieber | closed | 1.3.1.0 | 2013-03-13 | 1.3.1.1 |
| 159 | I'd like the customerRunnerTemplate parameter to work similar to how the maven-checkstyle-plugin handles it's [configLocation](http://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-mojo.html#configLocation) parameter. It accepts a string and then attempts to resolve it first as a classpath resource, then as a URL, and finally as a File (today's behavior). This will improve the ability to share templates. With this solution you could jar up the resource and distribute it that way or better yet, serve the template up on a CDN server and just point to the URL. | klieber | klieber | closed | enhancement | 2013-03-11 | 1.3.1.1 |
| 158 | I found this issue when using a template with the statement: Template: ```javascript var specs = $specsList$; ``` Resolved source, which is a syntax error: ```javascript var specs = ; ``` The standard require_js template should have the same issue. $specsList$ binds to an empty string instead of "[]" when no specs are found. In practice this is an issue when: 1. First starting a project that inherits from a common POM the build will fail initially when no specs are found. 2. Attempting to filter out specs using <specIncludes> - if you get the pattern wrong you get an exception instead of "0 specs, 0 failures". The following (DefaultSpecRunnerHtmlGenerator line 56) resolves the issues: ```javascript // ORIGINAL SOURCE template.add("specsList", this.createJsonArray(specs)); // Objects is from guava template.add("specsList", Objects.firstNonNull(this.createJsonArray(specs), "[]")); ``` | johnomalley | klieber | closed | 2013-03-11 | 1.3.1.0 | |
| 157 | * Adds configuration for maven site plugin * Adding use of maven-plugin-annotations to keep documentation and configuration seperate | klieber | klieber | closed | 2013-03-10 | 1.3.1.0 | |
| 156 | Adding a new parameter for the `test` goal called `keepServerAlive`. When set to `true` the server will keep running after the `test` goal exits so that other plugins like saga-maven-plugin may connect to it. The server will exit when the build exits. Default value for the parameter is `false`. | klieber | klieber | closed | 2013-03-08 | 1.3.1.0 | |
| 149 | Pull request #145 changed the `jasmine:test` goal so that it ran through jetty exactly the same as the `jasmine:bdd` goal. The problem with this is any user using the [saga-maven-plugin](http://timurstrekalov.github.com/saga/) to collect code coverage it will no longer work. That is because saga runs after the jasmine-maven-plugin and uses the `SpecRunner.html` file that the jasmine-maven-plugin generates. By the time it get's to the code coverage step the jetty server will no longer be running and so the plugin will fail. Also, in the current state of the saga-maven-plugin it cannot be executed against a web server. I've discussed this with @timurstrekalov (the maintainer of the saga-maven-plugin) in issue timurstrekalov/saga#50 and he believes he can make some changes to the plugin so that it can be run against a web server. I will have to add back in the custom lifecycle that pull request #145 removed so that the saga-maven-plugin can hook into it and execute before the jetty server is shutdown. I'm considering adding the following lifecycle phases: 1. jasmine-pre-test 1. jasmine-test 1. jasmine-post-test Then the jasmine-maven-plugin will start the jetty server in the `jasmine-pre-test` phase, execute the tests in the `jasmine-test` phase, and shutdown the server in the `jasmine-post-test` phase. To use the saga-maven-plugin you will then just need to bind the coverage goal to the `jasmine-test` phase rather than the `verify` phase. | klieber | klieber | closed | 1.3.1.0 | 2013-02-25 | 1.3.1.0 |
| 148 | This patch enables jasmine-maven-plugin to manage symlinks. Git supports symlinks, and it is a nice feature in some cases. | rvalle | klieber | closed | enhancement | 2013-02-21 | 1.3.1.3 |
| 146 | See https://github.com/searls/jasmine-maven-plugin/issues/68 | johnomalley | klieber | closed | enhancement | 2013-02-15 | 1.3.1.1 |
| 145 | This pull request brings the jasmine:bdd and jasmine:test closer together by having them both use jetty to run the specs. This eliminates the need to copy the sources/specs into the `target` directory and also eliminates the need to have a custom `jasmine-lifecycle`. As a result, we also no longer need to include `<extensions>true</extension>` in the plugin configuration. The following still needs to be completed before this pull request is merged in: * ~~Rename classes/variables like `CreatesManualRunner` to something more generic like `CreatesRunner`~~ * ~~Add some parameter validation before starting the jetty server so we can avoid starting it if we already know our configuration is wrong. An example would be validating that if a `customerRunnerTemplate` is provided then the file actually exists. Currently, this would start jetty and then you would get a FileNotFoundException in jetty's standard error and then the build would fail with a long stack trace from HtmlUnit complaining that you tried to run javascript on a plain text file. So, needless to say, it might take awhile for a user to figure out what happened.~~ * ~~Currently, all the paths to the source files and spec files use the relative path like `src/main/scripts` in the spec runners but it would make more sense if the used the value of the `srcDirectoryName` and `specDirectoryName` parameters (which default to `src` and `spec`, respectively).~~ I will work on those items above over the next few days. | klieber | klieber | closed | enhancement | 2013-02-15 | 1.3.1.0 |
| 142 | I noticed that often where `jasmine:bdd` works, `jasmine:test` does not. This seems to be the case because `jasmine:test` does not create a server but tried to do everything on file level. Which makes sense for performance reasons, but it breaks in certain scenarios. E.g. setting `baseUrl: "/src/js/"` in a custom require-js runner configuration works fine on the bdd mojo, but it breaks on the `test` mojo because Caused by: java.io.FileNotFoundException: /src/js/app.js (No such file or directory) Using a relative baseUrl works fine though. In this case, to ensure that both mojos work the same, I suggest making `jasmine:test` use absolute paths. What do you think? | rweng | klieber | closed | enhancement | 2013-02-14 | 1.3.1.0 |
| 141 | Test code changes because of java 1.6 compiler see bug http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7034548 | kreyssel | klieber | closed | 1.3.1.0 | 2013-02-14 | 1.3.1.0 |
| 138 | This should upgrade Jasmine and all dependencies/plugins to the latest version except for Mockito and PowerMock. I was running into an issue that was breaking the tests when upgrading them so I decided to leave them where they are at until the next release. It should be noted that @kreyssel did a lot of this same work in #136 but I was unable to get a successful merge of those changes into the master and it also included changes that were unrelated (using maven invoker plugin) so in the end it wasn't used. | klieber | klieber | closed | 2013-02-11 | 1.3.1.0 | |
| 137 | This pull request adds a TravisCI configuration file that will run both the maven build and the cucumber features against openjdk7, openjdk6, and oraclejdk7. It also upgrades capybara to 2.0.2 which in turn upgrades selenium-web-driver and fixes the browser tests. Finally, I also modified the `Rakefile` so that it fails when any of the shell commands fail. In order for this to be complete we will also need @searls to sign in to TravisCI and activate the repository. Here are the instructions for doing that, taken from the [getting started](http://about.travis-ci.org/docs/user/getting-started/) page. *Step two: Activate GitHub Service Hook #* *Once you're signed in go to your profile page. You'll see a list of your repositories. Flip the on/off switch for each repository that you want to hook up on Travis CI. Then visit the GitHub service hooks page for that project and paste your GitHub username and Travis token into the settings for the Travis service if it is not already pre-filled.* *If your repository belongs to an organization or flipping the switch did not set up the hook, please set it up manually on GitHub. It will take just a couple of minutes.* | klieber | klieber | closed | 2013-02-08 | 1.3.1.0 | |
| 135 | There is a bug of current htmlunit used by jasmine-maven-plugin: http://sourceforge.net/p/htmlunit/bugs/1381/ any plan to upgrade it? | ShijunK | klieber | closed | enhancement | 2013-02-01 | 1.3.1.0 |
| 132 | we noticed that mvn jasmine:bdd web server does not follow symlinks. Git does support Symlinks and we find it convenient in some cases. It would be nice to enable symlinks in the underlying web server. | husio-org | klieber | closed | enhancement | 2013-01-15 | 1.3.1.3 |
| 128 | This fixes the severe performance issues with big test suites due to unnecessary screen updates and how Rhino handles asynchronous things. | dtabuenc | closed | 1.2.0.0 | 2012-12-07 | 1.3.1.0 | |
| 127 | I have a jasmine test suite of around 400 tests. This runs in about 6-10 seconds in most browsers. When running it from maven, the time has seemed to start to increase exponentially lately. A few days ago I raised the timeout from default of 300 to 500. A few days later it needed raising up to 1000, now it's timing out at 1000 so I have to raise it again. I know we can expect HTMLUnit to be slower than running in-browser. But this is now several magnitudes slower (6seconds vs 15+ minutes). Is there anything other than html unit being slow that could be causing the slowness? Is there any recommended way to get a time breakdown per-spec so that I can see if it's just one spec that is causing it to hang or if it's just slow overall? | dtabuenc | closed | 1.2.0.0 | 2012-12-06 | 1.3.1.0 | |
| 124 | This pull request makes the RequireJsSpecRunnerHtmlGenerator and other customizations introduced by the require.js changes unnecessary. This is done simply by changing the DefaultSpecRunnerHtmlGenerator so that it provides more template variables. Then we can build the a spec runner template that supports require.js using the DefaultSpecRunnerHtmlGenerator. The specRunnerTemplate configuration parameter is still available, except now it is an enum and it is used simply to choose pre-built templates. You can take a look at the enum here: [SpecRunnerTemplate.java](https://github.com/klieber/jasmine-maven-plugin/blob/e5aa554a9a3015c9faff53afd3781d6bf2918892/src/main/java/com/github/searls/jasmine/runner/SpecRunnerTemplate.java) Here is an example of using the REQUIRE_JS built in template: ```xml <plugin> <groupId>com.github.searls</groupId> <artifactId>jasmine-maven-plugin</artifactId> <version>${jasmine-maven-plugin.version}</version> <extensions>true</extensions> <executions> <execution> <goals> <goal>test</goal> </goals> </execution> </executions> <configuration> <specRunnerTemplate>REQUIRE_JS</specRunnerTemplate> <preloadSources> <source>lib/require.js</source> </preloadSources> </configuration> </plugin> ``` And the template looks like this: ```html <!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=$sourceEncoding$"> <title>Jasmine Spec Runner</title> $cssDependencies$ $javascriptDependencies$ $preloadScriptTags$ </head> <body> <script type="text/javascript"> if(window.location.href.indexOf("ManualSpecRunner.html") !== -1) { document.body.appendChild(document.createTextNode("Warning: opening this HTML file directly from the file system is deprecated. You should instead try running `mvn jasmine:bdd` from the command line, and then visit `http://localhost:8234` in your browser. ")) } var specs = $specs$; var configuration = { $if(customRunnerConfiguration)$ $customRunnerConfiguration$ $endif$ }; if (!configuration.baseUrl) { configuration.baseUrl = '$sourceDir$'; } if (!configuration.paths) { configuration.paths = {}; } if (!configuration.paths.specs) { var specDir = '$specDir$'; if (!specDir.match(/^file/)) { specDir = '/'+specDir; } configuration.paths.specs = specDir; } require.config(configuration); require(specs, function() { window.reporter = new jasmine.$reporter$(); jasmine.getEnv().addReporter(reporter); if ('$reporter$' == 'HtmlReporter') { jasmine.getEnv().specFilter = function(spec) { return window.reporter.specFilter(spec); }; } jasmine.getEnv().execute(); }); </script> </body> </html> ``` This change not only simplifies the code quite a bit but it also gives users the power to truly customize their templates how they wish. For instance, I prefer to use [testr](https://github.com/mattfysh/testr.js) for testing require.js modules rather than wrapping each test in a `define` so the built in template doesn't work for me. With this pull request now I can just use this configuration: ``` <plugin> <groupId>com.github.searls</groupId> <artifactId>jasmine-maven-plugin</artifactId> <version>${jasmine-maven-plugin.version}</version> <extensions>true</extensions> <executions> <execution> <goals> <goal>test</goal> </goals> </execution> </executions> <configuration> <preloadSources> <source>lib/require.js</source> <source>lib/testr.js</source> </preloadSources> <customRunnerTemplate>src/test/config/testr_runner.htmltemplate</customRunnerTemplate> </configuration> </plugin> ``` My testr_runner.htmltemplate will look something like this: ```html <!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=$sourceEncoding$"> <title>Jasmine Spec Runner</title> $cssDependencies$ $javascriptDependencies$ $preloadScriptTags$ </head> <body> <script type="text/javascript"> if(window.location.href.indexOf("ManualSpecRunner.html") !== -1) { document.body.appendChild(document.createTextNode("Warning: opening this HTML file directly from the file system is deprecated. You should instead try running `mvn jasmine:bdd` from the command line, and then visit `http://localhost:8234` in your browser. ")) } var sources = $sources$; var sourceDir = '$sourceDir$'; // remove sourceDir and .js extension from each source for (var i=0; i < sources.length; i++) { sources[i] = sources[i].replace(sourceDir+'/','').replace(/\.js\$/,''); } $if(customRunnerConfiguration)$ $customRunnerConfiguration$ $else$ require.config({ baseUrl: sourceDir }); testr.config({ specBaseUrl: '$specDir$' }); $endif$ require(sources, function() { var currentWindowOnload = window.onload; window.onload = function() { if (currentWindowOnload) { currentWindowOnload(); } execJasmine(); }; function execJasmine() { window.reporter = new jasmine.$reporter$(); jasmine.getEnv().addReporter(reporter); jasmine.getEnv().execute(); } }); </script> </body> </html> ``` The best part of this change is that it no longer is the plugin's responsibility to support all the possible frameworks one might be using. In fact, we really wouldn't even have to keep a built-in REQUIRE_JS spec runner template in the plugin. You could simply just provide a wiki page with example templates for using different frameworks. | klieber | klieber | closed | enhancement | 2012-11-16 | 1.3.1.0 |
| 120 | Here's a pull attempting to make the RequireJsSpecRunner take into account the reporters specfilter, enabling running individual specs when using require.js. The solution was suggested on the mailing list, and seems to work ok - though I'm not sure this is the desired solution. Comments are appreciated. | torgeir | klieber | closed | enhancement | 2012-11-01 | 1.3.1.0 |
| 118 | The relative paths to the test/spec folder differs from the bdd to test goal: * bdd: spec/ * test: src/test/javascript/ I need to do AJAX requests to mock HTML fragments in my test source. I used the crude solution identified here for now: https://github.com/searls/jasmine-maven-plugin/issues/35 This is not ideal though. Is there a way to make the paths sync? Or is there a way to copy my src/test/resources to the target/jasmine folder for consistent access to these AJAX fixtures? | bbergstrom | klieber | closed | enhancement | 2012-10-22 | 1.3.1.0 |
| 109 | Is there any documentation anywhere for require JS support? | hayesmaker | closed | documentation | 2012-09-27 | 1.3.1.0 | |
| 100 | This is related to issue #33: I'm thrilled that the jasmine-maven-plugin now supports RequireJS (and would urge that this feature be documented better on the main site since it took a while for me to track down that the feature was even supported), but I have one request regarding the behavior of the plugin: Could the logic for the 'scriptLoaderPath' configuration variable be changed to support loading the script loader from a location external to the project's source directory? We want to be able to keep our 3rd party vendor source files (including require.js) in a different 'vendor' directory that is a peer to our 'src' directory to avoid pollution with our own source files, but the current plugin seems unable to search beyond the directory provided in 'jsSrcDir' for the file it needs no matter what value we put in 'scriptLoaderPath'. Thank you for building this tool, it has been a huge help to us! | JHouk | closed | enhancement | 2012-09-04 | 1.3.1.0 | |
| 99 | specrunner.html is wrong, missing handling of filtering. Without the extra lines below all test will be executed all the time even if only one section was executed using the "run" link/button. Line missing is described below: window.reporter = new jasmine.$reporter$(); >>>> missing lines if (reporter.specFilter){ env = jasmine.getEnv() env.specFilter = function(spec){ return reporter.specFilter(spec) } } >>>> end of missing lines jasmine.getEnv().addReporter(reporter); | SebTardif | closed | enhancement | 2012-08-21 | 1.3.1.0 | |
| 90 | When using the require.js mode (i.e. <specRunnerTemplate>REQUIRE_JS</specRunnerTemplate>) it appears that <preloadSources> are being added to the require.config as the priority attribute. The problem is that the order that the scripts are loaded isn't necessarily the order they appear in the pom.xml. The reasoning as well as a potential fix for this is outlined here: http://stackoverflow.com/questions/6135259/requirejs-order-does-not-work-with-priority-config-and-cdn-dependencies The drawback of this fix is that it requires the optional order.js plugin to require.js. Maybe there's another way to do the same thing.. | butchpeters | closed | bug | 2012-07-11 | 1.3.1.0 | |
| 87 | Hi, thank you for your cool plugin! I'm trying to use jasmine-maven-plugin with CoffeeScript and RequireJS. Now I have a trouble and a suggestion to solve it. ## problem I use CoffeeScript to code. Example: ```js // main.js require(['cs!original.module'], function(m){ // ... }); ``` ```coffee # original.module.coffee define [], () -> # ... ``` But ProcessResourcesMojo translated `original.module.coffee` to javascript, so [RequireJS's CoffeeScript plugin](http://requirejs.org/docs/download.html#cs) cannot load it correctly. Error messages like `reserved word "function" on line 1` will be displayed. ## solution Avoid translation for src if requirejs is used. We don't have to change ProcessTestResourcesMojo because requirejs doesn't load test resources. Please tell me your solution, or let's discuss about mine. I want to know who uses jasmine-maven-plugin with RequireJS and CoffeeScript, and their solution. Thank you! | KengoTODA | closed | bug | 2012-07-02 | 1.3.1.4 | |
| 85 | I would like to be able to reference the value specified for the jsTestSrcDir in the configuration inside my custom runner template. This is so that I can load extra test libraries (i.e. testr.js etc). Regards Brian | gurrie | closed | enhancement | 2012-06-21 | 1.3.1.0 | |
| 81 | closes #80 From now on user can specify proxy for HtmlUnitDriver so <preloadSources> won't fail build in such a case when URLs has been specified in <source> element instead of relative local paths. Example: ``` mvn test -Dhttp.proxyHost=myproxyhost.com -Dhttp.proxyPort=8000 ``` | sarxos | closed | enhancement | 2012-05-09 | 1.3.1.4 | |
| 80 | When I setup <preloadSources> and point them to some URLs, eg: ```xml <configuration> <preloadSources> <source>http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js</source> <source>https://raw.github.com/documentcloud/underscore/master/underscore.js</source> <source>https://raw.github.com/documentcloud/backbone/master/backbone.js</source> </preloadSources> </configuration> ``` There is no way to run mvn test when you are behind proxy. Proxy settings are being passed by: ``` $ mvn clean test -Dhttp.proxyHost=myproxyhost.com -Dhttp.proxyPort=8000 ``` In such a case you will get: ``` [INFO] Executing Jasmine Specs 2012-05-09 15:54:24 com.gargoylesoftware.htmlunit.html.HtmlPage loadExternalJavaScriptFile SEVERE: Error loading JavaScript from [http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js]. org.apache.http.conn.HttpHostConnectException: Connection to http://ajax.googleapis.com refused at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:158) at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149) at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121) at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:573) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:776) at com.gargoylesoftware.htmlunit.HttpWebConnection.getResponse(HttpWebConnection.java:152) at com.gargoylesoftware.htmlunit.WebClient.loadWebResponseFromWebConnection(WebClient.java:1439) at com.gargoylesoftware.htmlunit.WebClient.loadWebResponse(WebClient.java:1358) at com.gargoylesoftware.htmlunit.html.HtmlPage.loadJavaScriptFromUrl(HtmlPage.java:1008) at com.gargoylesoftware.htmlunit.html.HtmlPage.loadExternalJavaScriptFile(HtmlPage.java:950) at com.gargoylesoftware.htmlunit.html.HtmlScript.executeScriptIfNeeded(HtmlScript.java:349) at com.gargoylesoftware.htmlunit.html.HtmlScript$1.execute(HtmlScript.java:230) at com.gargoylesoftware.htmlunit.html.HtmlScript.onAllChildrenAddedToPage(HtmlScript.java:240) at com.gargoylesoftware.htmlunit.html.HTMLParser$HtmlUnitDOMBuilder.endElement(HTMLParser.java:598) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at com.gargoylesoftware.htmlunit.html.HTMLParser$HtmlUnitDOMBuilder.endElement(HTMLParser.java:556) at org.cyberneko.html.HTMLTagBalancer.callEndElement(HTMLTagBalancer.java:1142) at org.cyberneko.html.HTMLTagBalancer.endElement(HTMLTagBalancer.java:1044) at org.cyberneko.html.filters.DefaultFilter.endElement(DefaultFilter.java:206) at org.cyberneko.html.filters.NamespaceBinder.endElement(NamespaceBinder.java:329) at org.cyberneko.html.HTMLScanner$ContentScanner.scanEndElement(HTMLScanner.java:3018) at org.cyberneko.html.HTMLScanner$ContentScanner.scan(HTMLScanner.java:2005) at org.cyberneko.html.HTMLScanner.scanDocument(HTMLScanner.java:908) at org.cyberneko.html.HTMLConfiguration.parse(HTMLConfiguration.java:499) at org.cyberneko.html.HTMLConfiguration.parse(HTMLConfiguration.java:452) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at com.gargoylesoftware.htmlunit.html.HTMLParser$HtmlUnitDOMBuilder.parse(HTMLParser.java:789) at com.gargoylesoftware.htmlunit.html.HTMLParser.parse(HTMLParser.java:225) at com.gargoylesoftware.htmlunit.html.HTMLParser.parseHtml(HTMLParser.java:179) at com.gargoylesoftware.htmlunit.DefaultPageCreator.createHtmlPage(DefaultPageCreator.java:221) at com.gargoylesoftware.htmlunit.DefaultPageCreator.createPage(DefaultPageCreator.java:106) at com.gargoylesoftware.htmlunit.WebClient.loadWebResponseInto(WebClient.java:433) at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:311) at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:373) at org.openqa.selenium.htmlunit.HtmlUnitDriver.get(HtmlUnitDriver.java:345) at org.openqa.selenium.htmlunit.HtmlUnitDriver.get(HtmlUnitDriver.java:332) at com.github.searls.jasmine.runner.SpecRunnerExecutor.execute(SpecRunnerExecutor.java:31) at com.github.searls.jasmine.TestMojo.executeSpecs(TestMojo.java:57) at com.github.searls.jasmine.TestMojo.run(TestMojo.java:35) at com.github.searls.jasmine.AbstractJasmineMojo.execute(AbstractJasmineMojo.java:233) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at com.gargoylesoftware.htmlunit.SocksSocketFactory.connectSocket(SocksSocketFactory.java:89) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148) ... 62 more ``` I believe this could be fixed in TestMojo by checking if proxy has been set: ```java private WebDriver createDriver() { ... String proxyHost = System.setProperty("http.proxyHost"); String proxyPort = System.setProperty("http.proxyPort"); ... // set proxy in web driver ``` HtmlUnitDriver::setProxy(String, int) would have to be used: http://www.jarvana.com/jarvana/view/org/seleniumhq/selenium/selenium-htmlunit-driver/2.0a1/selenium-htmlunit-driver-2.0a1-javadoc.jar!/org/openqa/selenium/htmlunit/HtmlUnitDriver.html#setProxy%28java.lang.String,%20int%29 | sarxos | klieber | closed | enhancement | 2012-05-09 | 1.3.1.4 |
| 72 | Using `mvn package -DskipTests` it skip the tests correctly. But with the option `mvn package -Dmaven.test.skip=true` the plugin doesn't skip the tests. | axelhzf | klieber | closed | enhancement | 2012-03-27 | 1.3.1.3 |
| 69 | Visually it works, but the tests are still running and the only thing this template runner is doing is to show the filtered results. I am not sure if other specRunnerTemplates are facing the same issue. If you have a reasonable big test suite it can be useful specially for debugging that the filtering is applied to the execution and not only to visualizing the test results. Looking at the source code of the page, the problem seems to be that the querystring ?spec=... just affects the TrivialReporter.prototype.specFilter. A simple solution for the issue would be to override the jasmine environment specFilter with a slightly modified version of the TrivialReporter.prototype.specFilter, like: jasmine.getEnv().specFilter = function(spec) { var paramMap = {}; var params = window.location.search.substring(1).split('&'); for (var i = 0; i < params.length; i++) { var p = params[i].split('='); paramMap[decodeURIComponent(p[0])] = decodeURIComponent(p[1]); } if (!paramMap.spec) { return true; } return spec.getFullName().indexOf(paramMap.spec) === 0; } Sorry for not making this a pull request, but I was not sure where this code should go or even if it should go anywhere :P | waltercacau | closed | enhancement | 2012-03-16 | 1.3.1.0 | |
| 68 | I need to test some Raphael.js code. And my guess is that HTMLUnit does not support SVG. Is it possible to automate tests of this kind with this plugin? Is it possible to use PhantomJS as headless browser for unit testing within this plugin? If it is not, it would be a great feature to add! | rvalle | klieber | closed | enhancement | 2012-03-01 | 1.3.1.1 |
| 61 | <customRunnerConfiguration> and <specRunnerTemplate> are not documented in teh tailoring section of http://searls.github.com/jasmine-maven-plugin. This is very useful information if you want to use Jasmine in a requirejs project. | marceloverdijk | klieber | closed | documentation | 2012-01-25 | 1.3.1.0 |
| 44 | I want to generate some of the javascript for the specs to inject a port number into it. I'd rather keep the generated stuff in 'target', but then I'd need to be able to add more directories to the list. | bimargulies | klieber | closed | enhancement | 2011-11-02 | 1.3.1.5 |
| 42 | It would be nice to be able to skip these tests without skipping surefire, or vica versa. In other words, an alternative parameter with a distinctive name. | bimargulies | klieber | closed | enhancement | 2011-11-01 | 1.3.1.3 |
| 40 | I wish I could see a conventional maven-site-plugin site for the plugin. There's a maven plugin to allow the site plugin to write to a gh-pages ... | bimargulies | klieber | closed | enhancement | 2011-11-01 | 1.3.1.0 |
| 36 | Searls, BTW, I've just finished using jasmine:bdd for a couple days with a Ext JS 4 application and love it. It works great. I do have an issue with jasmine:test. It is probably specific to Ext JS 4 and likely won't affect others. It appears that during jasmine:bdd, Jetty delivers the files over http://. But during jasmine:test, the files are delivered as file:/ ``` mvn jasmine:bdd <script type="text/javascript" src="../../src/main/webapp/app.js"></script> mvn jasmine:test <script type="text/javascript" src="file:/Users/admin/workspace/git/ibis/ucas-webapp/target/jasmine/src/app.js"></script> ``` This gets in the way of the ext dynamic loading...I guess because of Same Origin Policy with the browsers...they don't like file:/ protocol. I understand that it's not your goal to make this work for Ext JS 4. But I just wanted to make sure that you are indeed writing the Spec scripts with the file:/ protocol and this is not a bug. Cheers, Dehru | dehru | closed | 1.0.2-beta-5 | 2011-09-28 | 1.3.1.0 | |
| 31 | any possibilities to turn off/on the chatty htmlUnit error messages in this plugin? 16.09.2011 11:49:31 com.gargoylesoftware.htmlunit.DefaultCssErrorHandler error WARNUNG: CSS error: null [8:438] Fehler in Ausdruck. Ungültiger Token "=". Erwartet wurde einer von: <S>, <COMMA>, "/", <PLUS>, "-", <HASH>, < STRING>, ")", <URI>, "inherit", <EMS>, <EXS>, <LENGTH_PX>, <LENGTH_CM>, <LENGTH_MM>, <LENGTH_IN>, <LENGTH_PT>, <LENGTH_PC>, <ANGLE_DEG>, <ANGL E_RAD>, <ANGLE_GRAD>, <TIME_MS>, <TIME_S>, <FREQ_HZ>, <FREQ_KHZ>, <DIMENSION>, <PERCENTAGE>, <NUMBER>, <FUNCTION>, <IDENT>. 16.09.2011 11:49:31 com.gargoylesoftware.htmlunit.DefaultCssErrorHandler error WARNUNG: CSS error: null [8:443] Fehler in Style-Regel. Ungültiger Token "opacity". Erwartet wurde einer von: "}", ";". http://htmlunit.sourceforge.net/faq.html#AJAXDoesNotWork reference:http://htmlunit.sourceforge.net/faq.html#AJAXDoesNotWork | xsocher | closed | enhancement | 2011-09-16 | 2.0 | |
| 5 | Add a configuration option to enable auto-refresh in the manual test runner after X seconds, as some folks have grown accustomed to spec-driving with this <meta http-equiv="refresh" content="3"> | searls | klieber | closed | enhancement | 2010-12-09 | 1.3.1.1 |