After much hard work spanning an entire year, we are proud to announce
the first official release of the ScalaTest for Scala IDE Plugin! Not
only does this plugin give Scala programmers the level of
test-framework/IDE integration that Java programmers have enjoyed with
JUnit, it goes quite a bit farther:
1. You can pretty much right click on anything that looks runnable and
run it as a test.
2. You can run just the tests you select in code, run tests you select
in reported results, rerun all tests or just previously failed tests,
or run tests in a selected class, file, or package.
3. The results pane mirrors the structure or the specification (i.e.,
if your BDD-style specification text is nested in the source, it will
appear nested in the results pane).
4. You can hop from results to test, scope, class, or line of failed code.
5. You can unfold the top of that stack that is automatically folded
so only the offending line of code is shown.
6. And, because ScalaTest is a platform that can support different
styles of testing, the plugin can be extended to grant full IDE
support for non-ScalaTest-native styles, such as a ScalaCheck
Properties classes, Specs2 Specifications, or custom styles.
You can use the plugin with any release of ScalaTest, but you'll enjoy
the most seamless IDE integration if you use ScalaTest 2.0.M2 (a very
carefully tested milestone release). You can plug it into either the
latest stable release of the Scala IDE for Eclipse (version 2.0.2), or
a nightly build of Eclipse 2.1.0.
So, how do you get the plugin? Select Help -> Install New Software in
Eclipse, and enter as your update site one of the "Scala IDE Ecosystem
update site" URLs on this page:
Any chance it will work in Eclipse Juno soon? I know the release notes indicate Indigo is required.
(BTW It seemed to install okay into Juno. But when I tried to run a test, the progress display appears but this error message was in the console for the test run:
On Thursday, July 26, 2012 2:44:54 AM UTC-4, Bill Venners wrote:
> Hello All,
> After much hard work spanning an entire year, we are proud to announce > the first official release of the ScalaTest for Scala IDE Plugin! Not > only does this plugin give Scala programmers the level of > test-framework/IDE integration that Java programmers have enjoyed with > JUnit, it goes quite a bit farther:
> 1. You can pretty much right click on anything that looks runnable and > run it as a test. > 2. You can run just the tests you select in code, run tests you select > in reported results, rerun all tests or just previously failed tests, > or run tests in a selected class, file, or package. > 3. The results pane mirrors the structure or the specification (i.e., > if your BDD-style specification text is nested in the source, it will > appear nested in the results pane). > 4. You can hop from results to test, scope, class, or line of failed code. > 5. You can unfold the top of that stack that is automatically folded > so only the offending line of code is shown. > 6. And, because ScalaTest is a platform that can support different > styles of testing, the plugin can be extended to grant full IDE > support for non-ScalaTest-native styles, such as a ScalaCheck > Properties classes, Specs2 Specifications, or custom styles.
> You can use the plugin with any release of ScalaTest, but you'll enjoy > the most seamless IDE integration if you use ScalaTest 2.0.M2 (a very > carefully tested milestone release). You can plug it into either the > latest stable release of the Scala IDE for Eclipse (version 2.0.2), or > a nightly build of Eclipse 2.1.0.
> So, how do you get the plugin? Select Help -> Install New Software in > Eclipse, and enter as your update site one of the "Scala IDE Ecosystem > update site" URLs on this page:
On Thu, Jul 26, 2012 at 6:01 AM, Kevin Esler <Kevin.Es...@gmail.com> wrote:
> Nice work! Thank you.
> Any chance it will work in Eclipse Juno soon? I know the release notes
> indicate Indigo is required.
> (BTW It seemed to install okay into Juno. But when I tried to run a test,
> the progress display appears but this error message was in the console for
> the test run:
> On Thursday, July 26, 2012 2:44:54 AM UTC-4, Bill Venners wrote:
>> Hello All,
>> After much hard work spanning an entire year, we are proud to announce
>> the first official release of the ScalaTest for Scala IDE Plugin! Not
>> only does this plugin give Scala programmers the level of
>> test-framework/IDE integration that Java programmers have enjoyed with
>> JUnit, it goes quite a bit farther:
>> 1. You can pretty much right click on anything that looks runnable and
>> run it as a test.
>> 2. You can run just the tests you select in code, run tests you select
>> in reported results, rerun all tests or just previously failed tests,
>> or run tests in a selected class, file, or package.
>> 3. The results pane mirrors the structure or the specification (i.e.,
>> if your BDD-style specification text is nested in the source, it will
>> appear nested in the results pane).
>> 4. You can hop from results to test, scope, class, or line of failed code.
>> 5. You can unfold the top of that stack that is automatically folded
>> so only the offending line of code is shown.
>> 6. And, because ScalaTest is a platform that can support different
>> styles of testing, the plugin can be extended to grant full IDE
>> support for non-ScalaTest-native styles, such as a ScalaCheck
>> Properties classes, Specs2 Specifications, or custom styles.
>> You can use the plugin with any release of ScalaTest, but you'll enjoy
>> the most seamless IDE integration if you use ScalaTest 2.0.M2 (a very
>> carefully tested milestone release). You can plug it into either the
>> latest stable release of the Scala IDE for Eclipse (version 2.0.2), or
>> a nightly build of Eclipse 2.1.0.
>> So, how do you get the plugin? Select Help -> Install New Software in
>> Eclipse, and enter as your update site one of the "Scala IDE Ecosystem
>> update site" URLs on this page:
> --
> You received this message because you are subscribed to the Google
> Groups "scalatest-users" group.
> To post to this group, send email to scalatest-users@googlegroups.com
> To unsubscribe from this group, send email to
> scalatest-users+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/scalatest-users?hl=en > ScalaTest itself, and documentation, is available here:
> http://www.artima.com/scalatest
Just curious about the error message "Unrecognized arguments: -k,
localhost, 62574.", are you using ScalaTest 2.0.M2? The -k argument is
only recognized by ScalaTest 2.0, when it detects that you have ScalaTest
1.8.x it should just use the default Runner UI in ScalaTest, do you have
both ScalaTest 1.x and ScalaTest 2.0 in the classpath?
On Thu, Jul 26, 2012 at 7:01 PM, Kevin Esler <Kevin.Es...@gmail.com> wrote:
> Nice work! Thank you.
> Any chance it will work in Eclipse Juno soon? I know the release notes
> indicate Indigo is required.
> (BTW It seemed to install okay into Juno. But when I tried to run a test,
> the progress display appears but this error message was in the console for
> the test run:
> On Thursday, July 26, 2012 2:44:54 AM UTC-4, Bill Venners wrote:
>> Hello All,
>> After much hard work spanning an entire year, we are proud to announce
>> the first official release of the ScalaTest for Scala IDE Plugin! Not
>> only does this plugin give Scala programmers the level of
>> test-framework/IDE integration that Java programmers have enjoyed with
>> JUnit, it goes quite a bit farther:
>> 1. You can pretty much right click on anything that looks runnable and
>> run it as a test.
>> 2. You can run just the tests you select in code, run tests you select
>> in reported results, rerun all tests or just previously failed tests,
>> or run tests in a selected class, file, or package.
>> 3. The results pane mirrors the structure or the specification (i.e.,
>> if your BDD-style specification text is nested in the source, it will
>> appear nested in the results pane).
>> 4. You can hop from results to test, scope, class, or line of failed
>> code.
>> 5. You can unfold the top of that stack that is automatically folded
>> so only the offending line of code is shown.
>> 6. And, because ScalaTest is a platform that can support different
>> styles of testing, the plugin can be extended to grant full IDE
>> support for non-ScalaTest-native styles, such as a ScalaCheck
>> Properties classes, Specs2 Specifications, or custom styles.
>> You can use the plugin with any release of ScalaTest, but you'll enjoy
>> the most seamless IDE integration if you use ScalaTest 2.0.M2 (a very
>> carefully tested milestone release). You can plug it into either the
>> latest stable release of the Scala IDE for Eclipse (version 2.0.2), or
>> a nightly build of Eclipse 2.1.0.
>> So, how do you get the plugin? Select Help -> Install New Software in
>> Eclipse, and enter as your update site one of the "Scala IDE Ecosystem
>> update site" URLs on this page:
> --
> You received this message because you are subscribed to the Google
> Groups "scalatest-users" group.
> To post to this group, send email to scalatest-users@googlegroups.com
> To unsubscribe from this group, send email to
> scalatest-users+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/scalatest-users?hl=en > ScalaTest itself, and documentation, is available here:
> http://www.artima.com/scalatest
On Thursday, July 26, 2012 10:46:03 AM UTC-4, Chee Seng Chua wrote:
> Hi Kevin,
> Just curious about the error message "Unrecognized arguments: -k, > localhost, 62574.", are you using ScalaTest 2.0.M2? The -k argument is > only recognized by ScalaTest 2.0, when it detects that you have ScalaTest > 1.8.x it should just use the default Runner UI in ScalaTest, do you have > both ScalaTest 1.x and ScalaTest 2.0 in the classpath?
> Thanks.
> Best Regards, > Chee Seng
> On Thu, Jul 26, 2012 at 7:01 PM, Kevin Esler <Kevin.Es...@gmail.com>wrote:
>> Nice work! Thank you.
>> Any chance it will work in Eclipse Juno soon? I know the release notes >> indicate Indigo is required.
>> (BTW It seemed to install okay into Juno. But when I tried to run a test, >> the progress display appears but this error message was in the console for >> the test run:
>> On Thursday, July 26, 2012 2:44:54 AM UTC-4, Bill Venners wrote:
>>> Hello All,
>>> After much hard work spanning an entire year, we are proud to announce >>> the first official release of the ScalaTest for Scala IDE Plugin! Not >>> only does this plugin give Scala programmers the level of >>> test-framework/IDE integration that Java programmers have enjoyed with >>> JUnit, it goes quite a bit farther:
>>> 1. You can pretty much right click on anything that looks runnable and >>> run it as a test. >>> 2. You can run just the tests you select in code, run tests you select >>> in reported results, rerun all tests or just previously failed tests, >>> or run tests in a selected class, file, or package. >>> 3. The results pane mirrors the structure or the specification (i.e., >>> if your BDD-style specification text is nested in the source, it will >>> appear nested in the results pane). >>> 4. You can hop from results to test, scope, class, or line of failed >>> code. >>> 5. You can unfold the top of that stack that is automatically folded >>> so only the offending line of code is shown. >>> 6. And, because ScalaTest is a platform that can support different >>> styles of testing, the plugin can be extended to grant full IDE >>> support for non-ScalaTest-native styles, such as a ScalaCheck >>> Properties classes, Specs2 Specifications, or custom styles.
>>> You can use the plugin with any release of ScalaTest, but you'll enjoy >>> the most seamless IDE integration if you use ScalaTest 2.0.M2 (a very >>> carefully tested milestone release). You can plug it into either the >>> latest stable release of the Scala IDE for Eclipse (version 2.0.2), or >>> a nightly build of Eclipse 2.1.0.
>>> So, how do you get the plugin? Select Help -> Install New Software in >>> Eclipse, and enter as your update site one of the "Scala IDE Ecosystem >>> update site" URLs on this page:
>> -- >> You received this message because you are subscribed to the Google
>> Groups "scalatest-users" group.
>> To post to this group, send email to scalatest-users@googlegroups.com
>> To unsubscribe from this group, send email to
>> scalatest-users+unsubscribe@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/scalatest-users?hl=en >> ScalaTest itself, and documentation, is available here:
>> http://www.artima.com/scalatest
Yes, the Scala IDE for Eclipse plugin itself isn't qualified for Juno.
ScalaTest for Scala IDE is a plugin into the Scala IDE for Eclipse. So
many levels of plugin. Anyway, just for the heck of it you might try
bumping the memory size of the JVM. The other things are fine.
Discovery starting is actually a stray println which we should have
removed, and the -p is just a deprecation warning. -p still works
fine. So the actual problem you hit is you ran out of memory.
On Thu, Jul 26, 2012 at 6:31 PM, Kevin Esler <Kevin.Es...@gmail.com> wrote:
> You're right. I had Scalatest 1.8 in the classpath. I guess it came in as a
> transitive dependency when SBT built the .classpath file.
> Anyway I removed it. Now when I launch Scalatest at a package I see this:
> WARNING: -p has been deprecated and will be reused for a different (but
> still very cool) purpose in ScalaTest 2.0. Please change all uses of -p to
> -R.
> DEBUG: Discovery Starting
> Exception in thread "main" java.lang.OutOfMemoryError: PermGen space
> Maybe not yet qualified on Juno?
> On Thursday, July 26, 2012 10:46:03 AM UTC-4, Chee Seng Chua wrote:
>> Hi Kevin,
>> Just curious about the error message "Unrecognized arguments: -k,
>> localhost, 62574.", are you using ScalaTest 2.0.M2? The -k argument is only
>> recognized by ScalaTest 2.0, when it detects that you have ScalaTest 1.8.x
>> it should just use the default Runner UI in ScalaTest, do you have both
>> ScalaTest 1.x and ScalaTest 2.0 in the classpath?
>> Thanks.
>> Best Regards,
>> Chee Seng
>> On Thu, Jul 26, 2012 at 7:01 PM, Kevin Esler <Kevin.Es...@gmail.com>
>> wrote:
>>> Nice work! Thank you.
>>> Any chance it will work in Eclipse Juno soon? I know the release notes
>>> indicate Indigo is required.
>>> (BTW It seemed to install okay into Juno. But when I tried to run a test,
>>> the progress display appears but this error message was in the console for
>>> the test run:
>>> On Thursday, July 26, 2012 2:44:54 AM UTC-4, Bill Venners wrote:
>>>> Hello All,
>>>> After much hard work spanning an entire year, we are proud to announce
>>>> the first official release of the ScalaTest for Scala IDE Plugin! Not
>>>> only does this plugin give Scala programmers the level of
>>>> test-framework/IDE integration that Java programmers have enjoyed with
>>>> JUnit, it goes quite a bit farther:
>>>> 1. You can pretty much right click on anything that looks runnable and
>>>> run it as a test.
>>>> 2. You can run just the tests you select in code, run tests you select
>>>> in reported results, rerun all tests or just previously failed tests,
>>>> or run tests in a selected class, file, or package.
>>>> 3. The results pane mirrors the structure or the specification (i.e.,
>>>> if your BDD-style specification text is nested in the source, it will
>>>> appear nested in the results pane).
>>>> 4. You can hop from results to test, scope, class, or line of failed
>>>> code.
>>>> 5. You can unfold the top of that stack that is automatically folded
>>>> so only the offending line of code is shown.
>>>> 6. And, because ScalaTest is a platform that can support different
>>>> styles of testing, the plugin can be extended to grant full IDE
>>>> support for non-ScalaTest-native styles, such as a ScalaCheck
>>>> Properties classes, Specs2 Specifications, or custom styles.
>>>> You can use the plugin with any release of ScalaTest, but you'll enjoy
>>>> the most seamless IDE integration if you use ScalaTest 2.0.M2 (a very
>>>> carefully tested milestone release). You can plug it into either the
>>>> latest stable release of the Scala IDE for Eclipse (version 2.0.2), or
>>>> a nightly build of Eclipse 2.1.0.
>>>> So, how do you get the plugin? Select Help -> Install New Software in
>>>> Eclipse, and enter as your update site one of the "Scala IDE Ecosystem
>>>> update site" URLs on this page:
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "scalatest-users" group.
>>> To post to this group, send email to scalatest-users@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> scalatest-users+unsubscribe@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/scalatest-users?hl=en >>> ScalaTest itself, and documentation, is available here:
>>> http://www.artima.com/scalatest
> --
> You received this message because you are subscribed to the Google
> Groups "scalatest-users" group.
> To post to this group, send email to scalatest-users@googlegroups.com
> To unsubscribe from this group, send email to
> scalatest-users+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/scalatest-users?hl=en > ScalaTest itself, and documentation, is available here:
> http://www.artima.com/scalatest
Thanks Bill. I tried bumping up "permgen" to 1gig but no luck. Same problem. WIll wait for official support but it looks good.
BTW I've been using the nightly builds of Eclipse IDE for Juno for several week now with nary a problem, and steadily improving feature set. Looking good.
On Thursday, July 26, 2012 7:35:54 PM UTC-4, Bill Venners wrote:
> Hi Kevin,
> Yes, the Scala IDE for Eclipse plugin itself isn't qualified for Juno. > ScalaTest for Scala IDE is a plugin into the Scala IDE for Eclipse. So > many levels of plugin. Anyway, just for the heck of it you might try > bumping the memory size of the JVM. The other things are fine. > Discovery starting is actually a stray println which we should have > removed, and the -p is just a deprecation warning. -p still works > fine. So the actual problem you hit is you ran out of memory.
> Bill
> On Thu, Jul 26, 2012 at 6:31 PM, Kevin Esler <Kevin.Es...@gmail.com> > wrote: > > You're right. I had Scalatest 1.8 in the classpath. I guess it came in > as a > > transitive dependency when SBT built the .classpath file.
> > Anyway I removed it. Now when I launch Scalatest at a package I see > this:
> > WARNING: -p has been deprecated and will be reused for a different (but > > still very cool) purpose in ScalaTest 2.0. Please change all uses of -p > to > > -R.
> > DEBUG: Discovery Starting
> > Exception in thread "main" java.lang.OutOfMemoryError: PermGen space
> > Maybe not yet qualified on Juno?
> > On Thursday, July 26, 2012 10:46:03 AM UTC-4, Chee Seng Chua wrote:
> >> Hi Kevin,
> >> Just curious about the error message "Unrecognized arguments: -k, > >> localhost, 62574.", are you using ScalaTest 2.0.M2? The -k argument is > only > >> recognized by ScalaTest 2.0, when it detects that you have ScalaTest > 1.8.x > >> it should just use the default Runner UI in ScalaTest, do you have both > >> ScalaTest 1.x and ScalaTest 2.0 in the classpath?
> >> Thanks.
> >> Best Regards, > >> Chee Seng
> >> On Thu, Jul 26, 2012 at 7:01 PM, Kevin Esler <Kevin.Es...@gmail.com> > >> wrote:
> >>> Nice work! Thank you.
> >>> Any chance it will work in Eclipse Juno soon? I know the release notes > >>> indicate Indigo is required.
> >>> (BTW It seemed to install okay into Juno. But when I tried to run a > test, > >>> the progress display appears but this error message was in the console > for > >>> the test run:
> >>> On Thursday, July 26, 2012 2:44:54 AM UTC-4, Bill Venners wrote:
> >>>> Hello All,
> >>>> After much hard work spanning an entire year, we are proud to > announce > >>>> the first official release of the ScalaTest for Scala IDE Plugin! Not > >>>> only does this plugin give Scala programmers the level of > >>>> test-framework/IDE integration that Java programmers have enjoyed > with > >>>> JUnit, it goes quite a bit farther:
> >>>> 1. You can pretty much right click on anything that looks runnable > and > >>>> run it as a test. > >>>> 2. You can run just the tests you select in code, run tests you > select > >>>> in reported results, rerun all tests or just previously failed tests, > >>>> or run tests in a selected class, file, or package. > >>>> 3. The results pane mirrors the structure or the specification (i.e., > >>>> if your BDD-style specification text is nested in the source, it will > >>>> appear nested in the results pane). > >>>> 4. You can hop from results to test, scope, class, or line of failed > >>>> code. > >>>> 5. You can unfold the top of that stack that is automatically folded > >>>> so only the offending line of code is shown. > >>>> 6. And, because ScalaTest is a platform that can support different > >>>> styles of testing, the plugin can be extended to grant full IDE > >>>> support for non-ScalaTest-native styles, such as a ScalaCheck > >>>> Properties classes, Specs2 Specifications, or custom styles.
> >>>> You can use the plugin with any release of ScalaTest, but you'll > enjoy > >>>> the most seamless IDE integration if you use ScalaTest 2.0.M2 (a very > >>>> carefully tested milestone release). You can plug it into either the > >>>> latest stable release of the Scala IDE for Eclipse (version 2.0.2), > or > >>>> a nightly build of Eclipse 2.1.0.
> >>>> So, how do you get the plugin? Select Help -> Install New Software in > >>>> Eclipse, and enter as your update site one of the "Scala IDE > Ecosystem > >>>> update site" URLs on this page:
> >>>> Many thanks to Chua Chee Seng, George Berger, Luc Bourlier, Mirco > >>>> Dotta, Iulian Dragoș and everyone else who helped with this effort.
> >>>> Enjoy!
> >>>> Bill > >>>> ---- > >>>> Bill Venners > >>>> Artima, Inc. > >>>> http://www.artima.com
> >>> -- > >>> You received this message because you are subscribed to the Google > >>> Groups "scalatest-users" group. > >>> To post to this group, send email to scalatest-users@googlegroups.com > >>> To unsubscribe from this group, send email to > >>> scalatest-users+unsubscribe@googlegroups.com > >>> For more options, visit this group at > >>> http://groups.google.com/group/scalatest-users?hl=en > >>> ScalaTest itself, and documentation, is available here: > >>> http://www.artima.com/scalatest
> > -- > > You received this message because you are subscribed to the Google > > Groups "scalatest-users" group. > > To post to this group, send email to scalatest-users@googlegroups.com > > To unsubscribe from this group, send email to > > scalatest-users+unsubscribe@googlegroups.com > > For more options, visit this group at > > http://groups.google.com/group/scalatest-users?hl=en > > ScalaTest itself, and documentation, is available here: > > http://www.artima.com/scalatest
On Fri, Jul 27, 2012 at 9:33 AM, Kevin Esler <Kevin.Es...@gmail.com> wrote:
> Thanks Bill. I tried bumping up "permgen" to 1gig but no luck. Same
> problem. WIll wait for official support but it looks good.
> BTW I've been using the nightly builds of Eclipse IDE for Juno for several
> week now with nary a problem, and steadily improving feature set. Looking
> good.
> On Thursday, July 26, 2012 7:35:54 PM UTC-4, Bill Venners wrote:
>> Hi Kevin,
>> Yes, the Scala IDE for Eclipse plugin itself isn't qualified for Juno.
>> ScalaTest for Scala IDE is a plugin into the Scala IDE for Eclipse. So
>> many levels of plugin. Anyway, just for the heck of it you might try
>> bumping the memory size of the JVM. The other things are fine.
>> Discovery starting is actually a stray println which we should have
>> removed, and the -p is just a deprecation warning. -p still works
>> fine. So the actual problem you hit is you ran out of memory.
>> Bill
>> On Thu, Jul 26, 2012 at 6:31 PM, Kevin Esler <Kevin.Es...@gmail.com>
>> wrote:
>> > You're right. I had Scalatest 1.8 in the classpath. I guess it came in
>> as a
>> > transitive dependency when SBT built the .classpath file.
>> > Anyway I removed it. Now when I launch Scalatest at a package I see
>> this:
>> > WARNING: -p has been deprecated and will be reused for a different (but
>> > still very cool) purpose in ScalaTest 2.0. Please change all uses of -p
>> to
>> > -R.
>> > DEBUG: Discovery Starting
>> > Exception in thread "main" java.lang.OutOfMemoryError: PermGen space
>> > Maybe not yet qualified on Juno?
>> > On Thursday, July 26, 2012 10:46:03 AM UTC-4, Chee Seng Chua wrote:
>> >> Hi Kevin,
>> >> Just curious about the error message "Unrecognized arguments: -k,
>> >> localhost, 62574.", are you using ScalaTest 2.0.M2? The -k argument
>> is only
>> >> recognized by ScalaTest 2.0, when it detects that you have ScalaTest
>> 1.8.x
>> >> it should just use the default Runner UI in ScalaTest, do you have
>> both
>> >> ScalaTest 1.x and ScalaTest 2.0 in the classpath?
>> >> Thanks.
>> >> Best Regards,
>> >> Chee Seng
>> >> On Thu, Jul 26, 2012 at 7:01 PM, Kevin Esler <Kevin.Es...@gmail.com>
>> >> wrote:
>> >>> Nice work! Thank you.
>> >>> Any chance it will work in Eclipse Juno soon? I know the release
>> notes
>> >>> indicate Indigo is required.
>> >>> (BTW It seemed to install okay into Juno. But when I tried to run a
>> test,
>> >>> the progress display appears but this error message was in the
>> console for
>> >>> the test run:
>> >>> On Thursday, July 26, 2012 2:44:54 AM UTC-4, Bill Venners wrote:
>> >>>> Hello All,
>> >>>> After much hard work spanning an entire year, we are proud to
>> announce
>> >>>> the first official release of the ScalaTest for Scala IDE Plugin!
>> Not
>> >>>> only does this plugin give Scala programmers the level of
>> >>>> test-framework/IDE integration that Java programmers have enjoyed
>> with
>> >>>> JUnit, it goes quite a bit farther:
>> >>>> 1. You can pretty much right click on anything that looks runnable
>> and
>> >>>> run it as a test.
>> >>>> 2. You can run just the tests you select in code, run tests you
>> select
>> >>>> in reported results, rerun all tests or just previously failed
>> tests,
>> >>>> or run tests in a selected class, file, or package.
>> >>>> 3. The results pane mirrors the structure or the specification
>> (i.e.,
>> >>>> if your BDD-style specification text is nested in the source, it
>> will
>> >>>> appear nested in the results pane).
>> >>>> 4. You can hop from results to test, scope, class, or line of failed
>> >>>> code.
>> >>>> 5. You can unfold the top of that stack that is automatically folded
>> >>>> so only the offending line of code is shown.
>> >>>> 6. And, because ScalaTest is a platform that can support different
>> >>>> styles of testing, the plugin can be extended to grant full IDE
>> >>>> support for non-ScalaTest-native styles, such as a ScalaCheck
>> >>>> Properties classes, Specs2 Specifications, or custom styles.
>> >>>> You can use the plugin with any release of ScalaTest, but you'll
>> enjoy
>> >>>> the most seamless IDE integration if you use ScalaTest 2.0.M2 (a
>> very
>> >>>> carefully tested milestone release). You can plug it into either the
>> >>>> latest stable release of the Scala IDE for Eclipse (version 2.0.2),
>> or
>> >>>> a nightly build of Eclipse 2.1.0.
>> >>>> So, how do you get the plugin? Select Help -> Install New Software
>> in
>> >>>> Eclipse, and enter as your update site one of the "Scala IDE
>> Ecosystem
>> >>>> update site" URLs on this page:
>> >>>> Many thanks to Chua Chee Seng, George Berger, Luc Bourlier, Mirco
>> >>>> Dotta, Iulian Dragoș and everyone else who helped with this effort.
>> >>>> Enjoy!
>> >>>> Bill
>> >>>> ----
>> >>>> Bill Venners
>> >>>> Artima, Inc.
>> >>>> http://www.artima.com
>> >>> --
>> >>> You received this message because you are subscribed to the Google
>> >>> Groups "scalatest-users" group.
>> >>> To post to this group, send email to scalatest-users@googlegroups.**
>> com <scalatest-users@googlegroups.com>
>> >>> To unsubscribe from this group, send email to
>> >>> scalatest-users+unsubscribe@**googlegroups.com<scalatest-users%2Bunsubscrib e@googlegroups.com>
>> >>> For more options, visit this group at
>> >>> http://groups.google.com/**group/scalatest-users?hl=en<http://groups.google.com/group/scalatest-users?hl=en>
>> >>> ScalaTest itself, and documentation, is available here:
>> >>> http://www.artima.com/**scalatest <http://www.artima.com/scalatest>
> --
> You received this message because you are subscribed to the Google
> Groups "scalatest-users" group.
> To post to this group, send email to scalatest-users@googlegroups.com
> To unsubscribe from this group, send email to
> scalatest-users+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/scalatest-users?hl=en > ScalaTest itself, and documentation, is available here:
> http://www.artima.com/scalatest
> Just a quick update, the Juno Scala IDE source doesn't seems to compile
> against ScalaTest plugin yet, see
> https://groups.google.com/forum/?fromgroups#!msg/scala-ide-dev/jdy3D2... , it
> is missing a pull request (which is in master already), and I think we
> perhaps we need a different maven profile to build for Juno, like we use
> different profile to build for 2.0.2 and nightly (see 'Building' section in
> https://github.com/scalatest/scalatest-eclipse-plugin), I'll try to check
> with luc.
> Cheers,
> Chee Seng
> On Fri, Jul 27, 2012 at 9:33 AM, Kevin Esler <Kevin.Es...@gmail.com>wrote:
>> Thanks Bill. I tried bumping up "permgen" to 1gig but no luck. Same
>> problem. WIll wait for official support but it looks good.
>> BTW I've been using the nightly builds of Eclipse IDE for Juno for
>> several week now with nary a problem, and steadily improving feature set.
>> Looking good.
>> On Thursday, July 26, 2012 7:35:54 PM UTC-4, Bill Venners wrote:
>>> Hi Kevin,
>>> Yes, the Scala IDE for Eclipse plugin itself isn't qualified for Juno.
>>> ScalaTest for Scala IDE is a plugin into the Scala IDE for Eclipse. So
>>> many levels of plugin. Anyway, just for the heck of it you might try
>>> bumping the memory size of the JVM. The other things are fine.
>>> Discovery starting is actually a stray println which we should have
>>> removed, and the -p is just a deprecation warning. -p still works
>>> fine. So the actual problem you hit is you ran out of memory.
>>> Bill
>>> On Thu, Jul 26, 2012 at 6:31 PM, Kevin Esler <Kevin.Es...@gmail.com>
>>> wrote:
>>> > You're right. I had Scalatest 1.8 in the classpath. I guess it came in
>>> as a
>>> > transitive dependency when SBT built the .classpath file.
>>> > Anyway I removed it. Now when I launch Scalatest at a package I see
>>> this:
>>> > WARNING: -p has been deprecated and will be reused for a different
>>> (but
>>> > still very cool) purpose in ScalaTest 2.0. Please change all uses of
>>> -p to
>>> > -R.
>>> > DEBUG: Discovery Starting
>>> > Exception in thread "main" java.lang.OutOfMemoryError: PermGen space
>>> > Maybe not yet qualified on Juno?
>>> > On Thursday, July 26, 2012 10:46:03 AM UTC-4, Chee Seng Chua wrote:
>>> >> Hi Kevin,
>>> >> Just curious about the error message "Unrecognized arguments: -k,
>>> >> localhost, 62574.", are you using ScalaTest 2.0.M2? The -k argument
>>> is only
>>> >> recognized by ScalaTest 2.0, when it detects that you have ScalaTest
>>> 1.8.x
>>> >> it should just use the default Runner UI in ScalaTest, do you have
>>> both
>>> >> ScalaTest 1.x and ScalaTest 2.0 in the classpath?
>>> >> Thanks.
>>> >> Best Regards,
>>> >> Chee Seng
>>> >> On Thu, Jul 26, 2012 at 7:01 PM, Kevin Esler <Kevin.Es...@gmail.com>
>>> >> wrote:
>>> >>> Nice work! Thank you.
>>> >>> Any chance it will work in Eclipse Juno soon? I know the release
>>> notes
>>> >>> indicate Indigo is required.
>>> >>> (BTW It seemed to install okay into Juno. But when I tried to run a
>>> test,
>>> >>> the progress display appears but this error message was in the
>>> console for
>>> >>> the test run:
>>> >>> On Thursday, July 26, 2012 2:44:54 AM UTC-4, Bill Venners wrote:
>>> >>>> Hello All,
>>> >>>> After much hard work spanning an entire year, we are proud to
>>> announce
>>> >>>> the first official release of the ScalaTest for Scala IDE Plugin!
>>> Not
>>> >>>> only does this plugin give Scala programmers the level of
>>> >>>> test-framework/IDE integration that Java programmers have enjoyed
>>> with
>>> >>>> JUnit, it goes quite a bit farther:
>>> >>>> 1. You can pretty much right click on anything that looks runnable
>>> and
>>> >>>> run it as a test.
>>> >>>> 2. You can run just the tests you select in code, run tests you
>>> select
>>> >>>> in reported results, rerun all tests or just previously failed
>>> tests,
>>> >>>> or run tests in a selected class, file, or package.
>>> >>>> 3. The results pane mirrors the structure or the specification
>>> (i.e.,
>>> >>>> if your BDD-style specification text is nested in the source, it
>>> will
>>> >>>> appear nested in the results pane).
>>> >>>> 4. You can hop from results to test, scope, class, or line of
>>> failed
>>> >>>> code.
>>> >>>> 5. You can unfold the top of that stack that is automatically
>>> folded
>>> >>>> so only the offending line of code is shown.
>>> >>>> 6. And, because ScalaTest is a platform that can support different
>>> >>>> styles of testing, the plugin can be extended to grant full IDE
>>> >>>> support for non-ScalaTest-native styles, such as a ScalaCheck
>>> >>>> Properties classes, Specs2 Specifications, or custom styles.
>>> >>>> You can use the plugin with any release of ScalaTest, but you'll
>>> enjoy
>>> >>>> the most seamless IDE integration if you use ScalaTest 2.0.M2 (a
>>> very
>>> >>>> carefully tested milestone release). You can plug it into either
>>> the
>>> >>>> latest stable release of the Scala IDE for Eclipse (version 2.0.2),
>>> or
>>> >>>> a nightly build of Eclipse 2.1.0.
>>> >>>> So, how do you get the plugin? Select Help -> Install New Software
>>> in
>>> >>>> Eclipse, and enter as your update site one of the "Scala IDE
>>> Ecosystem
>>> >>>> update site" URLs on this page:
>>> >>>> Many thanks to Chua Chee Seng, George Berger, Luc Bourlier, Mirco
>>> >>>> Dotta, Iulian Dragoș and everyone else who helped with this effort.
>>> >>>> Enjoy!
>>> >>>> Bill
>>> >>>> ----
>>> >>>> Bill Venners
>>> >>>> Artima, Inc.
>>> >>>> http://www.artima.com
>>> >>> --
>>> >>> You received this message because you are subscribed to the Google
>>> >>> Groups "scalatest-users" group.
>>> >>> To post to this group, send email to scalatest-users@googlegroups.**
>>> com <scalatest-users@googlegroups.com>
>>> >>> To unsubscribe from this group, send email to
>>> >>> scalatest-users+unsubscribe@**googlegroups.com<scalatest-users%2Bunsubscrib e@googlegroups.com>
>>> >>> For more options, visit this group at
>>> >>> http://groups.google.com/**group/scalatest-users?hl=en<http://groups.google.com/group/scalatest-users?hl=en>
>>> >>> ScalaTest itself, and documentation, is available here:
>>> >>> http://www.artima.com/**scalatest <http://www.artima.com/scalatest>
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups "scalatest-users" group.
>>> > To post to this group, send email to scalatest-users@googlegroups.**
>>> com <scalatest-users@googlegroups.com>
>>> > To unsubscribe from this group, send email to
>>> > scalatest-users+unsubscribe@**googlegroups.com<scalatest-users%2Bunsubscrib e@googlegroups.com>
>>> > For more options, visit this group at
>>> > http://groups.google.com/**group/scalatest-users?hl=en<http://groups.google.com/group/scalatest-users?hl=en>
>>> > ScalaTest itself, and documentation, is available here:
>>> > http://www.artima.com/**scalatest <http://www.artima.com/scalatest>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "scalatest-users" group.
>> To post to this group, send email to scalatest-users@googlegroups.com
>> To unsubscribe from this group, send email to
>> scalatest-users+unsubscribe@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/scalatest-users?hl=en >> ScalaTest itself, and documentation, is available here:
>> http://www.artima.com/scalatest
On Thursday, July 26, 2012 11:14:12 PM UTC-4, Chee Seng Chua wrote:
> Hi Kevin,
> >>I tried bumping up "permgen" to 1gig but no luck
> Just to double check, did you add the permgen setting to the Run > Configuration screen (under Arguments tab, VM arguments)?
> Cheers,
> Chee Seng
> On Fri, Jul 27, 2012 at 9:47 AM, Chee Seng Chua <chees...@amaseng.com>wrote:
>> Hi Kevin,
>> Just a quick update, the Juno Scala IDE source doesn't seems to compile >> against ScalaTest plugin yet, see >> https://groups.google.com/forum/?fromgroups#!msg/scala-ide-dev/jdy3D2... , it >> is missing a pull request (which is in master already), and I think we >> perhaps we need a different maven profile to build for Juno, like we use >> different profile to build for 2.0.2 and nightly (see 'Building' section in >> https://github.com/scalatest/scalatest-eclipse-plugin), I'll try to >> check with luc.
>> Cheers, >> Chee Seng
>> On Fri, Jul 27, 2012 at 9:33 AM, Kevin Esler <Kevin.Es...@gmail.com>wrote:
>>> Thanks Bill. I tried bumping up "permgen" to 1gig but no luck. Same >>> problem. WIll wait for official support but it looks good.
>>> BTW I've been using the nightly builds of Eclipse IDE for Juno for >>> several week now with nary a problem, and steadily improving feature set. >>> Looking good.
>>> On Thursday, July 26, 2012 7:35:54 PM UTC-4, Bill Venners wrote:
>>>> Hi Kevin,
>>>> Yes, the Scala IDE for Eclipse plugin itself isn't qualified for Juno. >>>> ScalaTest for Scala IDE is a plugin into the Scala IDE for Eclipse. So >>>> many levels of plugin. Anyway, just for the heck of it you might try >>>> bumping the memory size of the JVM. The other things are fine. >>>> Discovery starting is actually a stray println which we should have >>>> removed, and the -p is just a deprecation warning. -p still works >>>> fine. So the actual problem you hit is you ran out of memory.
>>>> Bill
>>>> On Thu, Jul 26, 2012 at 6:31 PM, Kevin Esler <Kevin.Es...@gmail.com> >>>> wrote: >>>> > You're right. I had Scalatest 1.8 in the classpath. I guess it came >>>> in as a >>>> > transitive dependency when SBT built the .classpath file.
>>>> > Anyway I removed it. Now when I launch Scalatest at a package I see >>>> this:
>>>> > WARNING: -p has been deprecated and will be reused for a different >>>> (but >>>> > still very cool) purpose in ScalaTest 2.0. Please change all uses of >>>> -p to >>>> > -R.
>>>> > DEBUG: Discovery Starting
>>>> > Exception in thread "main" java.lang.OutOfMemoryError: PermGen space
>>>> > Maybe not yet qualified on Juno?
>>>> > On Thursday, July 26, 2012 10:46:03 AM UTC-4, Chee Seng Chua wrote:
>>>> >> Hi Kevin,
>>>> >> Just curious about the error message "Unrecognized arguments: -k, >>>> >> localhost, 62574.", are you using ScalaTest 2.0.M2? The -k argument >>>> is only >>>> >> recognized by ScalaTest 2.0, when it detects that you have ScalaTest >>>> 1.8.x >>>> >> it should just use the default Runner UI in ScalaTest, do you have >>>> both >>>> >> ScalaTest 1.x and ScalaTest 2.0 in the classpath?
>>>> >> Thanks.
>>>> >> Best Regards, >>>> >> Chee Seng
>>>> >> On Thu, Jul 26, 2012 at 7:01 PM, Kevin Esler <Kevin.Es...@gmail.com>
>>>> >> wrote:
>>>> >>> Nice work! Thank you.
>>>> >>> Any chance it will work in Eclipse Juno soon? I know the release >>>> notes >>>> >>> indicate Indigo is required.
>>>> >>> (BTW It seemed to install okay into Juno. But when I tried to run a >>>> test, >>>> >>> the progress display appears but this error message was in the >>>> console for >>>> >>> the test run:
>>>> >>> On Thursday, July 26, 2012 2:44:54 AM UTC-4, Bill Venners wrote:
>>>> >>>> Hello All,
>>>> >>>> After much hard work spanning an entire year, we are proud to >>>> announce >>>> >>>> the first official release of the ScalaTest for Scala IDE Plugin! >>>> Not >>>> >>>> only does this plugin give Scala programmers the level of >>>> >>>> test-framework/IDE integration that Java programmers have enjoyed >>>> with >>>> >>>> JUnit, it goes quite a bit farther:
>>>> >>>> 1. You can pretty much right click on anything that looks runnable >>>> and >>>> >>>> run it as a test. >>>> >>>> 2. You can run just the tests you select in code, run tests you >>>> select >>>> >>>> in reported results, rerun all tests or just previously failed >>>> tests, >>>> >>>> or run tests in a selected class, file, or package. >>>> >>>> 3. The results pane mirrors the structure or the specification >>>> (i.e., >>>> >>>> if your BDD-style specification text is nested in the source, it >>>> will >>>> >>>> appear nested in the results pane). >>>> >>>> 4. You can hop from results to test, scope, class, or line of >>>> failed >>>> >>>> code. >>>> >>>> 5. You can unfold the top of that stack that is automatically >>>> folded >>>> >>>> so only the offending line of code is shown. >>>> >>>> 6. And, because ScalaTest is a platform that can support different >>>> >>>> styles of testing, the plugin can be extended to grant full IDE >>>> >>>> support for non-ScalaTest-native styles, such as a ScalaCheck >>>> >>>> Properties classes, Specs2 Specifications, or custom styles.
>>>> >>>> You can use the plugin with any release of ScalaTest, but you'll >>>> enjoy >>>> >>>> the most seamless IDE integration if you use ScalaTest 2.0.M2 (a >>>> very >>>> >>>> carefully tested milestone release). You can plug it into either >>>> the >>>> >>>> latest stable release of the Scala IDE for Eclipse (version >>>> 2.0.2), or >>>> >>>> a nightly build of Eclipse 2.1.0.
>>>> >>>> So, how do you get the plugin? Select Help -> Install New Software >>>> in >>>> >>>> Eclipse, and enter as your update site one of the "Scala IDE >>>> Ecosystem >>>> >>>> update site" URLs on this page:
>>>> >>>> Many thanks to Chua Chee Seng, George Berger, Luc Bourlier, Mirco >>>> >>>> Dotta, Iulian Dragoș and everyone else who helped with this >>>> effort.
>>>> >>>> Enjoy!
>>>> >>>> Bill >>>> >>>> ---- >>>> >>>> Bill Venners >>>> >>>> Artima, Inc. >>>> >>>> http://www.artima.com
>>>> >>> -- >>>> >>> You received this message because you are subscribed to the Google >>>> >>> Groups "scalatest-users" group. >>>> >>> To post to this group, send email to scalatest-users@googlegroups.*
>>>> *com <scalatest-users@googlegroups.com> >>>> >>> To unsubscribe from this group, send email to >>>> >>> scalatest-users+unsubscribe@**googlegroups.com<scalatest-users%2Bunsubscrib e@googlegroups.com> >>>> >>> For more options, visit this group at >>>> >>> http://groups.google.com/**group/scalatest-users?hl=en<http://groups.google.com/group/scalatest-users?hl=en> >>>> >>> ScalaTest itself, and documentation, is available here: >>>> >>> http://www.artima.com/**scalatest <http://www.artima.com/scalatest>
>>>> > -- >>>> > You received this message because you are subscribed to the Google >>>> > Groups "scalatest-users" group. >>>> > To post to this group, send email to scalatest-users@googlegroups.**
>>>> com <scalatest-users@googlegroups.com> >>>> > To unsubscribe from this group, send email to >>>> > scalatest-users+unsubscribe@**googlegroups.com<scalatest-users%2Bunsubscrib e@googlegroups.com> >>>> > For more options, visit this group at >>>> > http://groups.google.com/**group/scalatest-users?hl=en<http://groups.google.com/group/scalatest-users?hl=en> >>>> > ScalaTest itself, and documentation, is available here: >>>> > http://www.artima.com/**scalatest <http://www.artima.com/scalatest>
>>> -- >>> You received this message because you are subscribed to the Google
>>> Groups "scalatest-users" group.
>>> To post to this group, send email to scalatest-users@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> scalatest-users+unsubscribe@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/scalatest-users?hl=en >>> ScalaTest itself, and documentation, is available here:
On Fri, Jul 27, 2012 at 9:37 AM, Kevin Esler <Kevin.Es...@gmail.com> wrote:
> Bingo! Thanks Chee Seng. Adjusting permgen on the Run Config got it to work.
> All my tests are now running in Juno. Thanks for the help.
> On Thursday, July 26, 2012 11:14:12 PM UTC-4, Chee Seng Chua wrote:
>> Hi Kevin,
>> >>I tried bumping up "permgen" to 1gig but no luck
>> Just to double check, did you add the permgen setting to the Run
>> Configuration screen (under Arguments tab, VM arguments)?
>> Cheers,
>> Chee Seng
>> On Fri, Jul 27, 2012 at 9:47 AM, Chee Seng Chua <chees...@amaseng.com>
>> wrote:
>>> Hi Kevin,
>>> Just a quick update, the Juno Scala IDE source doesn't seems to compile
>>> against ScalaTest plugin yet, see
>>> https://groups.google.com/forum/?fromgroups#!msg/scala-ide-dev/jdy3D2... >>> , it is missing a pull request (which is in master already), and I think we
>>> perhaps we need a different maven profile to build for Juno, like we use
>>> different profile to build for 2.0.2 and nightly (see 'Building' section in
>>> https://github.com/scalatest/scalatest-eclipse-plugin), I'll try to check
>>> with luc.
>>> Cheers,
>>> Chee Seng
>>> On Fri, Jul 27, 2012 at 9:33 AM, Kevin Esler <Kevin.Es...@gmail.com>
>>> wrote:
>>>> Thanks Bill. I tried bumping up "permgen" to 1gig but no luck. Same
>>>> problem. WIll wait for official support but it looks good.
>>>> BTW I've been using the nightly builds of Eclipse IDE for Juno for
>>>> several week now with nary a problem, and steadily improving feature set.
>>>> Looking good.
>>>> On Thursday, July 26, 2012 7:35:54 PM UTC-4, Bill Venners wrote:
>>>>> Hi Kevin,
>>>>> Yes, the Scala IDE for Eclipse plugin itself isn't qualified for Juno.
>>>>> ScalaTest for Scala IDE is a plugin into the Scala IDE for Eclipse. So
>>>>> many levels of plugin. Anyway, just for the heck of it you might try
>>>>> bumping the memory size of the JVM. The other things are fine.
>>>>> Discovery starting is actually a stray println which we should have
>>>>> removed, and the -p is just a deprecation warning. -p still works
>>>>> fine. So the actual problem you hit is you ran out of memory.
>>>>> Bill
>>>>> On Thu, Jul 26, 2012 at 6:31 PM, Kevin Esler <Kevin.Es...@gmail.com>
>>>>> wrote:
>>>>> > You're right. I had Scalatest 1.8 in the classpath. I guess it came
>>>>> > in as a
>>>>> > transitive dependency when SBT built the .classpath file.
>>>>> > Anyway I removed it. Now when I launch Scalatest at a package I see
>>>>> > this:
>>>>> > WARNING: -p has been deprecated and will be reused for a different
>>>>> > (but
>>>>> > still very cool) purpose in ScalaTest 2.0. Please change all uses of
>>>>> > -p to
>>>>> > -R.
>>>>> > DEBUG: Discovery Starting
>>>>> > Exception in thread "main" java.lang.OutOfMemoryError: PermGen space
>>>>> > Maybe not yet qualified on Juno?
>>>>> > On Thursday, July 26, 2012 10:46:03 AM UTC-4, Chee Seng Chua wrote:
>>>>> >> Hi Kevin,
>>>>> >> Just curious about the error message "Unrecognized arguments: -k,
>>>>> >> localhost, 62574.", are you using ScalaTest 2.0.M2? The -k argument
>>>>> >> is only
>>>>> >> recognized by ScalaTest 2.0, when it detects that you have ScalaTest
>>>>> >> 1.8.x
>>>>> >> it should just use the default Runner UI in ScalaTest, do you have
>>>>> >> both
>>>>> >> ScalaTest 1.x and ScalaTest 2.0 in the classpath?
>>>>> >> Thanks.
>>>>> >> Best Regards,
>>>>> >> Chee Seng
>>>>> >> On Thu, Jul 26, 2012 at 7:01 PM, Kevin Esler <Kevin.Es...@gmail.com>
>>>>> >> wrote:
>>>>> >>> Nice work! Thank you.
>>>>> >>> Any chance it will work in Eclipse Juno soon? I know the release
>>>>> >>> notes
>>>>> >>> indicate Indigo is required.
>>>>> >>> (BTW It seemed to install okay into Juno. But when I tried to run a
>>>>> >>> test,
>>>>> >>> the progress display appears but this error message was in the
>>>>> >>> console for
>>>>> >>> the test run:
>>>>> >>> On Thursday, July 26, 2012 2:44:54 AM UTC-4, Bill Venners wrote:
>>>>> >>>> Hello All,
>>>>> >>>> After much hard work spanning an entire year, we are proud to
>>>>> >>>> announce
>>>>> >>>> the first official release of the ScalaTest for Scala IDE Plugin!
>>>>> >>>> Not
>>>>> >>>> only does this plugin give Scala programmers the level of
>>>>> >>>> test-framework/IDE integration that Java programmers have enjoyed
>>>>> >>>> with
>>>>> >>>> JUnit, it goes quite a bit farther:
>>>>> >>>> 1. You can pretty much right click on anything that looks runnable
>>>>> >>>> and
>>>>> >>>> run it as a test.
>>>>> >>>> 2. You can run just the tests you select in code, run tests you
>>>>> >>>> select
>>>>> >>>> in reported results, rerun all tests or just previously failed
>>>>> >>>> tests,
>>>>> >>>> or run tests in a selected class, file, or package.
>>>>> >>>> 3. The results pane mirrors the structure or the specification
>>>>> >>>> (i.e.,
>>>>> >>>> if your BDD-style specification text is nested in the source, it
>>>>> >>>> will
>>>>> >>>> appear nested in the results pane).
>>>>> >>>> 4. You can hop from results to test, scope, class, or line of
>>>>> >>>> failed
>>>>> >>>> code.
>>>>> >>>> 5. You can unfold the top of that stack that is automatically
>>>>> >>>> folded
>>>>> >>>> so only the offending line of code is shown.
>>>>> >>>> 6. And, because ScalaTest is a platform that can support different
>>>>> >>>> styles of testing, the plugin can be extended to grant full IDE
>>>>> >>>> support for non-ScalaTest-native styles, such as a ScalaCheck
>>>>> >>>> Properties classes, Specs2 Specifications, or custom styles.
>>>>> >>>> You can use the plugin with any release of ScalaTest, but you'll
>>>>> >>>> enjoy
>>>>> >>>> the most seamless IDE integration if you use ScalaTest 2.0.M2 (a
>>>>> >>>> very
>>>>> >>>> carefully tested milestone release). You can plug it into either
>>>>> >>>> the
>>>>> >>>> latest stable release of the Scala IDE for Eclipse (version
>>>>> >>>> 2.0.2), or
>>>>> >>>> a nightly build of Eclipse 2.1.0.
>>>>> >>>> So, how do you get the plugin? Select Help -> Install New Software
>>>>> >>>> in
>>>>> >>>> Eclipse, and enter as your update site one of the "Scala IDE
>>>>> >>>> Ecosystem
>>>>> >>>> update site" URLs on this page:
>>>>> >>>> Many thanks to Chua Chee Seng, George Berger, Luc Bourlier, Mirco
>>>>> >>>> Dotta, Iulian Dragoș and everyone else who helped with this
>>>>> >>>> effort.
>>>>> >>>> Enjoy!
>>>>> >>>> Bill
>>>>> >>>> ----
>>>>> >>>> Bill Venners
>>>>> >>>> Artima, Inc.
>>>>> >>>> http://www.artima.com
>>>>> >>> --
>>>>> >>> You received this message because you are subscribed to the Google
>>>>> >>> Groups "scalatest-users" group.
>>>>> >>> To post to this group, send email to
>>>>> >>> scalatest-users@googlegroups.com
>>>>> >>> To unsubscribe from this group, send email to
>>>>> >>> scalatest-users+unsubscribe@googlegroups.com
>>>>> >>> For more options, visit this group at
>>>>> >>> http://groups.google.com/group/scalatest-users?hl=en >>>>> >>> ScalaTest itself, and documentation, is available here:
>>>>> >>> http://www.artima.com/scalatest
>>>>> > --
>>>>> > You received this message because you are subscribed to the Google
>>>>> > Groups "scalatest-users" group.
>>>>> > To post to this group, send email to scalatest-users@googlegroups.com
>>>>> > To unsubscribe from this group, send email to
>>>>> > scalatest-users+unsubscribe@googlegroups.com
>>>>> > For more options, visit this group at
>>>>> > http://groups.google.com/group/scalatest-users?hl=en >>>>> > ScalaTest itself, and documentation, is available here:
>>>>> > http://www.artima.com/scalatest
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "scalatest-users" group.
>>>> To post to this group, send email to scalatest-users@googlegroups.com
>>>> To unsubscribe from this group, send email to
>>>> scalatest-users+unsubscribe@googlegroups.com
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/scalatest-users?hl=en >>>> ScalaTest itself, and documentation, is available here:
>>>> http://www.artima.com/scalatest
> --
> You received this message because you are subscribed to the Google
> Groups "scalatest-users" group.
> To post to this group, send email to scalatest-users@googlegroups.com
> To unsubscribe from this group, send email to
On Fri, Jul 27, 2012 at 10:41 PM, Bill Venners <b...@artima.com> wrote:
> Hi Kevin,
> That's great. Thanks for letting us know.
> Bill
> On Fri, Jul 27, 2012 at 9:37 AM, Kevin Esler <Kevin.Es...@gmail.com>
> wrote:
> > Bingo! Thanks Chee Seng. Adjusting permgen on the Run Config got it to
> work.
> > All my tests are now running in Juno. Thanks for the help.
> > On Thursday, July 26, 2012 11:14:12 PM UTC-4, Chee Seng Chua wrote:
> >> Hi Kevin,
> >> >>I tried bumping up "permgen" to 1gig but no luck
> >> Just to double check, did you add the permgen setting to the Run
> >> Configuration screen (under Arguments tab, VM arguments)?
> >> Cheers,
> >> Chee Seng
> >> On Fri, Jul 27, 2012 at 9:47 AM, Chee Seng Chua <chees...@amaseng.com>
> >> wrote:
> >>> Hi Kevin,
> >>> Just a quick update, the Juno Scala IDE source doesn't seems to compile
> >>> against ScalaTest plugin yet, see
> >>> On Fri, Jul 27, 2012 at 9:33 AM, Kevin Esler <Kevin.Es...@gmail.com>
> >>> wrote:
> >>>> Thanks Bill. I tried bumping up "permgen" to 1gig but no luck. Same
> >>>> problem. WIll wait for official support but it looks good.
> >>>> BTW I've been using the nightly builds of Eclipse IDE for Juno for
> >>>> several week now with nary a problem, and steadily improving feature
> set.
> >>>> Looking good.
> >>>> On Thursday, July 26, 2012 7:35:54 PM UTC-4, Bill Venners wrote:
> >>>>> Hi Kevin,
> >>>>> Yes, the Scala IDE for Eclipse plugin itself isn't qualified for
> Juno.
> >>>>> ScalaTest for Scala IDE is a plugin into the Scala IDE for Eclipse.
> So
> >>>>> many levels of plugin. Anyway, just for the heck of it you might try
> >>>>> bumping the memory size of the JVM. The other things are fine.
> >>>>> Discovery starting is actually a stray println which we should have
> >>>>> removed, and the -p is just a deprecation warning. -p still works
> >>>>> fine. So the actual problem you hit is you ran out of memory.
> >>>>> Bill
> >>>>> On Thu, Jul 26, 2012 at 6:31 PM, Kevin Esler <Kevin.Es...@gmail.com>
> >>>>> wrote:
> >>>>> > You're right. I had Scalatest 1.8 in the classpath. I guess it came
> >>>>> > in as a
> >>>>> > transitive dependency when SBT built the .classpath file.
> >>>>> > Anyway I removed it. Now when I launch Scalatest at a package I
> see
> >>>>> > this:
> >>>>> > WARNING: -p has been deprecated and will be reused for a different
> >>>>> > (but
> >>>>> > still very cool) purpose in ScalaTest 2.0. Please change all uses
> of
> >>>>> > -p to
> >>>>> > -R.
> >>>>> > DEBUG: Discovery Starting
> >>>>> > Exception in thread "main" java.lang.OutOfMemoryError: PermGen
> space
> >>>>> > Maybe not yet qualified on Juno?
> >>>>> > On Thursday, July 26, 2012 10:46:03 AM UTC-4, Chee Seng Chua wrote:
> >>>>> >> Hi Kevin,
> >>>>> >> Just curious about the error message "Unrecognized arguments: -k,
> >>>>> >> localhost, 62574.", are you using ScalaTest 2.0.M2? The -k
> argument
> >>>>> >> is only
> >>>>> >> recognized by ScalaTest 2.0, when it detects that you have
> ScalaTest
> >>>>> >> 1.8.x
> >>>>> >> it should just use the default Runner UI in ScalaTest, do you have
> >>>>> >> both
> >>>>> >> ScalaTest 1.x and ScalaTest 2.0 in the classpath?
> >>>>> >> Thanks.
> >>>>> >> Best Regards,
> >>>>> >> Chee Seng
> >>>>> >> On Thu, Jul 26, 2012 at 7:01 PM, Kevin Esler <
> Kevin.Es...@gmail.com>
> >>>>> >> wrote:
> >>>>> >>> Nice work! Thank you.
> >>>>> >>> Any chance it will work in Eclipse Juno soon? I know the release
> >>>>> >>> notes
> >>>>> >>> indicate Indigo is required.
> >>>>> >>> (BTW It seemed to install okay into Juno. But when I tried to
> run a
> >>>>> >>> test,
> >>>>> >>> the progress display appears but this error message was in the
> >>>>> >>> console for
> >>>>> >>> the test run:
> >>>>> >>> On Thursday, July 26, 2012 2:44:54 AM UTC-4, Bill Venners wrote:
> >>>>> >>>> Hello All,
> >>>>> >>>> After much hard work spanning an entire year, we are proud to
> >>>>> >>>> announce
> >>>>> >>>> the first official release of the ScalaTest for Scala IDE
> Plugin!
> >>>>> >>>> Not
> >>>>> >>>> only does this plugin give Scala programmers the level of
> >>>>> >>>> test-framework/IDE integration that Java programmers have
> enjoyed
> >>>>> >>>> with
> >>>>> >>>> JUnit, it goes quite a bit farther:
> >>>>> >>>> 1. You can pretty much right click on anything that looks
> runnable
> >>>>> >>>> and
> >>>>> >>>> run it as a test.
> >>>>> >>>> 2. You can run just the tests you select in code, run tests you
> >>>>> >>>> select
> >>>>> >>>> in reported results, rerun all tests or just previously failed
> >>>>> >>>> tests,
> >>>>> >>>> or run tests in a selected class, file, or package.
> >>>>> >>>> 3. The results pane mirrors the structure or the specification
> >>>>> >>>> (i.e.,
> >>>>> >>>> if your BDD-style specification text is nested in the source, it
> >>>>> >>>> will
> >>>>> >>>> appear nested in the results pane).
> >>>>> >>>> 4. You can hop from results to test, scope, class, or line of
> >>>>> >>>> failed
> >>>>> >>>> code.
> >>>>> >>>> 5. You can unfold the top of that stack that is automatically
> >>>>> >>>> folded
> >>>>> >>>> so only the offending line of code is shown.
> >>>>> >>>> 6. And, because ScalaTest is a platform that can support
> different
> >>>>> >>>> styles of testing, the plugin can be extended to grant full IDE
> >>>>> >>>> support for non-ScalaTest-native styles, such as a ScalaCheck
> >>>>> >>>> Properties classes, Specs2 Specifications, or custom styles.
> >>>>> >>>> You can use the plugin with any release of ScalaTest, but you'll
> >>>>> >>>> enjoy
> >>>>> >>>> the most seamless IDE integration if you use ScalaTest 2.0.M2 (a
> >>>>> >>>> very
> >>>>> >>>> carefully tested milestone release). You can plug it into either
> >>>>> >>>> the
> >>>>> >>>> latest stable release of the Scala IDE for Eclipse (version
> >>>>> >>>> 2.0.2), or
> >>>>> >>>> a nightly build of Eclipse 2.1.0.
> >>>>> >>>> So, how do you get the plugin? Select Help -> Install New
> Software
> >>>>> >>>> in
> >>>>> >>>> Eclipse, and enter as your update site one of the "Scala IDE
> >>>>> >>>> Ecosystem
> >>>>> >>>> update site" URLs on this page:
> >>>>> >>>> Many thanks to Chua Chee Seng, George Berger, Luc Bourlier,
> Mirco
> >>>>> >>>> Dotta, Iulian Dragoș and everyone else who helped with this
> >>>>> >>>> effort.
> >>>>> >>>> Enjoy!
> >>>>> >>>> Bill
> >>>>> >>>> ----
> >>>>> >>>> Bill Venners
> >>>>> >>>> Artima, Inc.
> >>>>> >>>> http://www.artima.com
> >>>>> >>> --
> >>>>> >>> You received this message because you are subscribed to the
> Google
> >>>>> >>> Groups "scalatest-users" group.
> >>>>> >>> To post to this group, send email to
> >>>>> >>> scalatest-users@googlegroups.com
> >>>>> >>> To unsubscribe from this group, send email to
> >>>>> >>> scalatest-users+unsubscribe@googlegroups.com
> >>>>> >>> For more options, visit this group at
> >>>>> >>> http://groups.google.com/group/scalatest-users?hl=en > >>>>> >>> ScalaTest itself, and documentation, is available here:
> >>>>> >>> http://www.artima.com/scalatest
> >>>>> > --
> >>>>> > You received this message because you are subscribed to the Google
> >>>>> > Groups "scalatest-users" group.
> >>>>> > To post to this group, send email to
> scalatest-users@googlegroups.com
> >>>>> > To unsubscribe from this group, send email to
> >>>>> > scalatest-users+unsubscribe@googlegroups.com
> >>>>> > For more options, visit this group at
> >>>>> > http://groups.google.com/group/scalatest-users?hl=en > >>>>> > ScalaTest itself, and documentation, is available here:
> >>>>> > http://www.artima.com/scalatest
And by the way, please tell us about your experience with the plugin.
We appreciate any bug reports, suggestions for improvements, and
general comments too.
Thanks.
Bill
On Fri, Jul 27, 2012 at 9:42 AM, Chee Seng Chua <chees...@amaseng.com> wrote:
> On Fri, Jul 27, 2012 at 10:41 PM, Bill Venners <b...@artima.com> wrote:
>> Hi Kevin,
>> That's great. Thanks for letting us know.
>> Bill
>> On Fri, Jul 27, 2012 at 9:37 AM, Kevin Esler <Kevin.Es...@gmail.com>
>> wrote:
>> > Bingo! Thanks Chee Seng. Adjusting permgen on the Run Config got it to
>> > work.
>> > All my tests are now running in Juno. Thanks for the help.
>> > On Thursday, July 26, 2012 11:14:12 PM UTC-4, Chee Seng Chua wrote:
>> >> Hi Kevin,
>> >> >>I tried bumping up "permgen" to 1gig but no luck
>> >> Just to double check, did you add the permgen setting to the Run
>> >> Configuration screen (under Arguments tab, VM arguments)?
>> >> Cheers,
>> >> Chee Seng
>> >> On Fri, Jul 27, 2012 at 9:47 AM, Chee Seng Chua <chees...@amaseng.com>
>> >> wrote:
>> >>> Hi Kevin,
>> >>> Just a quick update, the Juno Scala IDE source doesn't seems to
>> >>> compile
>> >>> against ScalaTest plugin yet, see
>> >>> On Fri, Jul 27, 2012 at 9:33 AM, Kevin Esler <Kevin.Es...@gmail.com>
>> >>> wrote:
>> >>>> Thanks Bill. I tried bumping up "permgen" to 1gig but no luck. Same
>> >>>> problem. WIll wait for official support but it looks good.
>> >>>> BTW I've been using the nightly builds of Eclipse IDE for Juno for
>> >>>> several week now with nary a problem, and steadily improving feature
>> >>>> set.
>> >>>> Looking good.
>> >>>> On Thursday, July 26, 2012 7:35:54 PM UTC-4, Bill Venners wrote:
>> >>>>> Hi Kevin,
>> >>>>> Yes, the Scala IDE for Eclipse plugin itself isn't qualified for
>> >>>>> Juno.
>> >>>>> ScalaTest for Scala IDE is a plugin into the Scala IDE for Eclipse.
>> >>>>> So
>> >>>>> many levels of plugin. Anyway, just for the heck of it you might try
>> >>>>> bumping the memory size of the JVM. The other things are fine.
>> >>>>> Discovery starting is actually a stray println which we should have
>> >>>>> removed, and the -p is just a deprecation warning. -p still works
>> >>>>> fine. So the actual problem you hit is you ran out of memory.
>> >>>>> Bill
>> >>>>> On Thu, Jul 26, 2012 at 6:31 PM, Kevin Esler <Kevin.Es...@gmail.com>
>> >>>>> wrote:
>> >>>>> > You're right. I had Scalatest 1.8 in the classpath. I guess it
>> >>>>> > came
>> >>>>> > in as a
>> >>>>> > transitive dependency when SBT built the .classpath file.
>> >>>>> > Anyway I removed it. Now when I launch Scalatest at a package I
>> >>>>> > see
>> >>>>> > this:
>> >>>>> > WARNING: -p has been deprecated and will be reused for a different
>> >>>>> > (but
>> >>>>> > still very cool) purpose in ScalaTest 2.0. Please change all uses
>> >>>>> > of
>> >>>>> > -p to
>> >>>>> > -R.
>> >>>>> > DEBUG: Discovery Starting
>> >>>>> > Exception in thread "main" java.lang.OutOfMemoryError: PermGen
>> >>>>> > space
>> >>>>> > Maybe not yet qualified on Juno?
>> >>>>> > On Thursday, July 26, 2012 10:46:03 AM UTC-4, Chee Seng Chua
>> >>>>> > wrote:
>> >>>>> >> Hi Kevin,
>> >>>>> >> Just curious about the error message "Unrecognized arguments: -k,
>> >>>>> >> localhost, 62574.", are you using ScalaTest 2.0.M2? The -k
>> >>>>> >> argument
>> >>>>> >> is only
>> >>>>> >> recognized by ScalaTest 2.0, when it detects that you have
>> >>>>> >> ScalaTest
>> >>>>> >> 1.8.x
>> >>>>> >> it should just use the default Runner UI in ScalaTest, do you
>> >>>>> >> have
>> >>>>> >> both
>> >>>>> >> ScalaTest 1.x and ScalaTest 2.0 in the classpath?
>> >>>>> >> Thanks.
>> >>>>> >> Best Regards,
>> >>>>> >> Chee Seng
>> >>>>> >> On Thu, Jul 26, 2012 at 7:01 PM, Kevin Esler
>> >>>>> >> <Kevin.Es...@gmail.com>
>> >>>>> >> wrote:
>> >>>>> >>> Nice work! Thank you.
>> >>>>> >>> Any chance it will work in Eclipse Juno soon? I know the release
>> >>>>> >>> notes
>> >>>>> >>> indicate Indigo is required.
>> >>>>> >>> (BTW It seemed to install okay into Juno. But when I tried to
>> >>>>> >>> run a
>> >>>>> >>> test,
>> >>>>> >>> the progress display appears but this error message was in the
>> >>>>> >>> console for
>> >>>>> >>> the test run:
>> >>>>> >>> On Thursday, July 26, 2012 2:44:54 AM UTC-4, Bill Venners wrote:
>> >>>>> >>>> Hello All,
>> >>>>> >>>> After much hard work spanning an entire year, we are proud to
>> >>>>> >>>> announce
>> >>>>> >>>> the first official release of the ScalaTest for Scala IDE
>> >>>>> >>>> Plugin!
>> >>>>> >>>> Not
>> >>>>> >>>> only does this plugin give Scala programmers the level of
>> >>>>> >>>> test-framework/IDE integration that Java programmers have
>> >>>>> >>>> enjoyed
>> >>>>> >>>> with
>> >>>>> >>>> JUnit, it goes quite a bit farther:
>> >>>>> >>>> 1. You can pretty much right click on anything that looks
>> >>>>> >>>> runnable
>> >>>>> >>>> and
>> >>>>> >>>> run it as a test.
>> >>>>> >>>> 2. You can run just the tests you select in code, run tests you
>> >>>>> >>>> select
>> >>>>> >>>> in reported results, rerun all tests or just previously failed
>> >>>>> >>>> tests,
>> >>>>> >>>> or run tests in a selected class, file, or package.
>> >>>>> >>>> 3. The results pane mirrors the structure or the specification
>> >>>>> >>>> (i.e.,
>> >>>>> >>>> if your BDD-style specification text is nested in the source,
>> >>>>> >>>> it
>> >>>>> >>>> will
>> >>>>> >>>> appear nested in the results pane).
>> >>>>> >>>> 4. You can hop from results to test, scope, class, or line of
>> >>>>> >>>> failed
>> >>>>> >>>> code.
>> >>>>> >>>> 5. You can unfold the top of that stack that is automatically
>> >>>>> >>>> folded
>> >>>>> >>>> so only the offending line of code is shown.
>> >>>>> >>>> 6. And, because ScalaTest is a platform that can support
>> >>>>> >>>> different
>> >>>>> >>>> styles of testing, the plugin can be extended to grant full IDE
>> >>>>> >>>> support for non-ScalaTest-native styles, such as a ScalaCheck
>> >>>>> >>>> Properties classes, Specs2 Specifications, or custom styles.
>> >>>>> >>>> You can use the plugin with any release of ScalaTest, but
>> >>>>> >>>> you'll
>> >>>>> >>>> enjoy
>> >>>>> >>>> the most seamless IDE integration if you use ScalaTest 2.0.M2
>> >>>>> >>>> (a
>> >>>>> >>>> very
>> >>>>> >>>> carefully tested milestone release). You can plug it into
>> >>>>> >>>> either
>> >>>>> >>>> the
>> >>>>> >>>> latest stable release of the Scala IDE for Eclipse (version
>> >>>>> >>>> 2.0.2), or
>> >>>>> >>>> a nightly build of Eclipse 2.1.0.
>> >>>>> >>>> So, how do you get the plugin? Select Help -> Install New
>> >>>>> >>>> Software
>> >>>>> >>>> in
>> >>>>> >>>> Eclipse, and enter as your update site one of the "Scala IDE
>> >>>>> >>>> Ecosystem
>> >>>>> >>>> update site" URLs on this page:
>> >>>>> >>>> Select ScalaTest for Scala IDE (and the others if you don't
>> >>>>> >>>> have
>> >>>>> >>>> them
>> >>>>> >>>> already), and click Next then Finish.
>> >>>>> >>>> Information on the features of the integration (and some
>> >>>>> >>>> screenshots
>> >>>>> >>>> (and the source code)) is here:
>> >>>>> >>>> Many thanks to Chua Chee Seng, George Berger, Luc Bourlier,
>> >>>>> >>>> Mirco
>> >>>>> >>>> Dotta, Iulian Dragoș and everyone else who helped with this
>> >>>>> >>>> effort.
>> >>>>> >>>> Enjoy!
>> >>>>> >>>> Bill
>> >>>>> >>>> ----
>> >>>>> >>>> Bill Venners
>> >>>>> >>>> Artima, Inc.
>> >>>>> >>>> http://www.artima.com
>> >>>>> >>> --
>> >>>>> >>> You received this message because you are subscribed to the
>> >>>>> >>> Google
>> >>>>> >>> Groups "scalatest-users" group.
>> >>>>> >>> To post to this group, send email to
>> >>>>> >>> scalatest-users@googlegroups.com
>> >>>>> >>> To unsubscribe from this group, send email to
>> >>>>> >>> scalatest-users+unsubscribe@googlegroups.com
>> >>>>> >>> For more options, visit this group at
>> >>>>> >>> http://groups.google.com/group/scalatest-users?hl=en
Is there a release of the Scalatest Eclipse plugin for 2.10? I did
try the 2.9 version, but it doesn't do anything (no run as ->
scalatest anywhere I can see, for example).
Unfortunately we don't have one built for juno deployed. Last time I
checked it seems that the Scala IDE Juno branch is missing a pull request
that needs a little tweak for the plugin to compile correctly:-
On Tue, Aug 28, 2012 at 12:09 PM, James Moore <ja...@restphone.com> wrote:
> Is there a release of the Scalatest Eclipse plugin for 2.10? I did
> try the 2.9 version, but it doesn't do anything (no run as ->
> scalatest anywhere I can see, for example).
> --
> You received this message because you are subscribed to the Google
> Groups "scalatest-users" group.
> To post to this group, send email to scalatest-users@googlegroups.com
> To unsubscribe from this group, send email to
> scalatest-users+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/scalatest-users?hl=en > ScalaTest itself, and documentation, is available here:
> http://www.artima.com/scalatest
On Tue, Aug 28, 2012 at 11:00 PM, James Moore <ja...@restphone.com> wrote:
> On Mon, Aug 27, 2012 at 9:31 PM, Chee Seng Chua <chees...@amaseng.com>
> wrote:
> > Hi James,
> > Unfortunately we don't have one built for juno deployed.
> Sorry, I didn't mean for Juno, I meant for Indigo with the 2.10 IDE,
> not the 2.9.
> --
> You received this message because you are subscribed to the Google
> Groups "scalatest-users" group.
> To post to this group, send email to scalatest-users@googlegroups.com
> To unsubscribe from this group, send email to
> scalatest-users+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/scalatest-users?hl=en > ScalaTest itself, and documentation, is available here:
> http://www.artima.com/scalatest
