Running scalan tests.

[Dr. Ivan Zapreev]

I feel myself a bit of a spammer, but I could not yet find much on running the scalan tests (unit, integration, and etc)
The main README.md provides a very scarce information of this matter. Is there any specific test framework you are using?
Any possible info on the subject will be greatly appreciated :-D

[Alexey Romanov]

We are just using ScalaTest. Just running `test` and `it:test` (and `lms-backend/it:test` until #14 is fixed) in SBT should be enough. Are there any problems with running them?

[Dr. Ivan Zapreev]

Thanks! Actually, I've already figured it out  :) And yes, everything goes smoothly, I only miss a general summary after running all the tests. For the rest it works just fine.

[Dr. Ivan Zapreev]

By the way, how do you run BoilerplateToolRun tests? Is there a script that invokes it?

Because in your listing I see it is invoked with a long set of java parameters. In the scalan project, though, I only have the generated classes:

zapreevi:~/workspace/scalan-ce$ find . -name "*BoilerplateToolRun*"
./meta/target/scala-2.10/classes/scalan/meta/BoilerplateToolRun$.class
./meta/target/scala-2.10/classes/scalan/meta/BoilerplateToolRun.class
zapreevi:~/workspace/scalan-ce$ 
 

Is it your own script you use or is there a special way to do it? Please share your wisdom, the meta/README.dm is not very helpful.

[Dr. Ivan Zapreev]

The answer is in picture. Although it would go faster if you would just comment on this.

[Alexey Romanov]

I personally just run it from SBT. On the other hand, you are right that `meta/README.md` should be removed and its usage documented in root README. It's an artifact from `meta` originally being in a separate repository.

[Dr. Ivan Zapreev]

Oh well ... no problem. I did not try to run it from sbt, but may be next time ))))