-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
does sbt-scct support running test outside of scala project against instrumented classes? #62
Comments
Update it myself. Tried for standard code, running test still required source code to be in the classpath even though instrumented classes are already there. Is this by design and required to get the report? C:\ScalaExamples\standard_proj_819_test>scala -cp ".;scct_2.9.2-0.2-SNAPSHOT.jar" com.autodesk.my.MyTestObject |
Continuing with the original question, I created a Play project and a junit test in scala which in turns calls a SoapUI test (test one GET api). I used scct:test to run the test and the soapui test runs and passed. However, the code coverage date shows 0% coverage which I observed from zero increase with other non-soapui junit test. C:\ScalaExamples\PlayAppTestScala\todolist>sbt scct:test C:\ScalaExamples\PlayAppTestScala\todolist>set SCRIPT_DIR=C:\Program Files (x86)\sbt\ C:\ScalaExamples\PlayAppTestScala\todolist>java -Xmx512M -XX:PermSize=128m -jar "C:\Program Files (x86)\sbt\sbt-launch.jar" scct:test |
Looks I have to put test under scala project hierarchy tree. What if the test is not written in scala or java, neither does it use any Scala main testing framework and sit outside of the tree? What are the steps to follow in that case? Is there any step like to allow first, compile source code with scct-sbt, so that tests outside of scala project run against the instrumented source?
The text was updated successfully, but these errors were encountered: