stevedlawrence opened a new issue, #17:
URL: https://github.com/apache/daffodil-sbt/issues/17
The convention for testing schema projects is to write all tests in a TDML
file and then create a Scala file that used JUnit to run those tests. This
leads to a bit of duplication and verbosity. It would be nice if we could
reduce this to make running tests easier. Some possibilities discussed:
1. An idea might be to automatically generate this kind of file in a
test-managed directory during sbt compile (or sbt Test/compile or sbt test).
Then we still can open this kind of Scala file in our IDEs to debug individual
tests within the debugger, but our responsibility for creating and updating
these files is handed over to the sbt plugin.
2. Do something like this:
```scala
@Test def test_test01(): Unit = doTest(runner)
```
And the doTest function looks at the stack to figure out the function
that called it, strips off the "test_" prefix and calls runner.runOneTest
passing in the name. It still requires managing scala file, but it's a bit less
verbose.
3. I wonder if now that IDE's have much better SBT support, if creating an
SBT Test Interface for TDML would just magically give IDE's the capabilities we
expect out of IDEs (e.g. list of tests, ability to right-click a location in a
TDML file to run a test).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
