Using the attached example I would expect "doAfterSpec" to print at least once for every SpecsExample definition but it only prints when there is a single 'should' containing a single spec.

Please checks specs 1.6.1-SNAPSHOT for a fix: http://scala-tools.org/repo- snapshots/org/scala-tools/testing/specs/1.6.1-SNAPSHOT/

I just tried with http://scala-tools.org/repo-snapshots/org/scala-tools/testing/specs/1.6.1-SNAPSHOT/specs-1.6.1-SNAPSHOT.jar (MD5 checksum of a83fd4f6dd1414b4441feebefa6c8949) and got the same result. I tried it running through simple-build-tool inside my project and just using scala from the command line by itself.

running 'scala -cp specs-1.6.1-SNAPSHOT.jar:. example.SpecsExample2' yields the following with all files located in the same directory:

Specification "SpecsExample2" Numbers should doAfter + add doAfter doLast + divide

Which is the same result I was receiving before (no doAfterSpec).

java -version shows the following in case it helps: java version "1.6.0_15" Java(TM) SE Runtime Environment (build 1.6.0_15-b03-226) Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02-92, mixed mode)

A quick run under Java 5 provided the same results though. I'm running Scala 2.7.6.final in all cases.

If there's any more information I can provide please let me know. Thanks for taking a look at this so quickly!

Ok, I'll checked what's wrong with my deployment because it definitely worked for me.

Can you please try with the latest jar? Thanks.

Seems to be working well now.

Sadly my specs are still throwing errors with 1.6.1-SNAPSHOT and not with 1.5.0 but I'll have to do some more investigating.

Thanks again for responding so quickly.

Please keep me updated with your errors because the execution model of specs has changed between 1.5.0 and 1.6.0. You may have to add shareVariables() to get a similar behavior as before: http://code.google.com/p/specs/wiki/DeclareSpecifications#What_if_I_want_to_share_state ?