Spec\acceptance test with ScalaTest+Gradle

[bzz]

This is an experiment on solving #1 using Gradle+Ivy+ScalaTest for build\deps mngt\Tests

• setup infra: gradle wrapper, project structure, build script, test wrapper
• make tests fail
• speed-up: turn-off everything, except test (i.e Java\Scala compilation)
• propagate URL as an argument to test

Pre-requests:

1. JRE installed

How to run:

• ./test_spec (AKA cd /spec && ./gradlew test)

Pros:

• only 1 pre-reuqest: jvm (binary packages exist for most OS)
• flexible test style

Cons:

• Ugly dir structure hidden in /spec now
• less elegant then https://github.com/nytlabs/hive/blob/master/spec/
• 5 sec runtime

[bzz]

Somehow, I already feel embarrassment on how ugly this look like on practice...
@felizbear could you give it a try (and not puke)?

This definitely can be improved, the only question is "does it worth an effort"?
I would prefer having more PRs like that (differetn stacks) before putting more effort on this one..

[heruka-urgyen]

It took 55 seconds to build on the first run, around half of the time on consecutive runs. Curiously, it does not indicate whether tests passed or not. I modified one test to be assert(Set.empty.size == 1), however got no visual feedback that the test have failed. Am I doing something wrong?

[bzz]

This is time equivalent to brew install npm && npm install && npm test all together (for the first run) - so I'm pretty sure it at least
the same as node one.

Thanks for trying, now I'm willing to enhance this a little bit more, after
Jasmin example.

On Tue, Dec 23, 2014 at 8:17 PM, felizbear [email protected] wrote:

It took 55 seconds to build on the first run, around half of the time on
consecutive runs. Curiously, it does not indicate whether tests passed or
not. I modified one test to be assert(Set.empty.size == 1), however got
no visual feedback that the test have failed. Am I doing something wrong?

—
Reply to this email directly or view it on GitHub
#2 (comment)
.

Kind regards,
Alexander.