search

jlgrock / ClosureJavascriptFramework

A group of plug-ins that can be used in conjunction with maven to execute the Google Closure Compiler on JavaScript code. This Framework allows for scaling and modularity.
MIT License
16 stars 7 forks source link

Exception in Reading Failure Statistic #13

Closed jlgrock closed 12 years ago

jlgrock commented 12 years ago

The following code (:

TestFailureStatistic tfs = this.testFailureStatistics.get(this.testFailureStatistics.size()-1);

Is causing the following error: [INFO] --- closure-testing-maven-plugin:1.12.0:js-closure-test (default-js-closure-test) @ integration-testing --- INFO Generating Test Suite INFO Calculating File Set ERROR -1 java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.ArrayList.elementData(ArrayList.java:371) at java.util.ArrayList.get(ArrayList.java:384) at com.github.jlgrock.javascriptframework.closuretesting.resultparsing.testingcomponents.TestCase.addToLastTestFailureStatistic(TestCase.java:284) at com.github.jlgrock.javascriptframework.closuretesting.resultparsing.parsers.TestCaseParser.setDivProperty(TestCaseParser.java:108) at com.github.jlgrock.javascriptframework.closuretesting.resultparsing.parsers.TestCaseParser.parse(TestCaseParser.java:52) at com.github.jlgrock.javascriptframework.closuretesting.resultparsing.ParseRunner.parseFiles(ParseRunner.java:99) at com.github.jlgrock.javascriptframework.closuretesting.ClosureTestingMojo.parseFiles(ClosureTestingMojo.java:206) at com.github.jlgrock.javascriptframework.closuretesting.ClosureTestingMojo.execute(ClosureTestingMojo.java:53) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) 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:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188) at org.apache.maven.cli.MavenCli.main(MavenCli.java:134) 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)

jlgrock commented 12 years ago

I have fixed the exception that would happen, but not the root cause. If the regex fails now, it doesn't put in the addition of a success/failure. I don't know if this will fix the problem or not. I'm going to assume this case was only showing up in the case of long js error chains, which should be caught separately. So, I'm going to be closing this one and I'll open a new issue if it rears its ugly head again.