A cli rascal test runner for use from the maven plugin. - #2755
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #2755 +/- ##
========================================
- Coverage 46% 45% -1%
+ Complexity 6727 6715 -12
========================================
Files 842 844 +2
Lines 66809 66995 +186
Branches 9987 10011 +24
========================================
- Hits 30791 30774 -17
- Misses 33631 33838 +207
+ Partials 2387 2383 -4 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
|
I like this feature 👍 I'll try to allocate time for a review next week. |
8fa1f46 to
6287931
Compare
|
|
RascalTest does not have a test itself, parallel to RascalShell and RascalCheck and RascalCompile. I think we should have a different PR to resolve this omision for all commandline tools in one go. |
|
@DavyLandman testing this on Windows is redundant since it uses the same setup as RascalCompile for running the checker. |
… files in the chunks and not in their imported modules
|



To use this add this to your pom.xml and make sure the
<srcs>configuration for the rascal-maven-plugin matches what you want to test. You can also add a new<srcs>tag here with a different<configuration>under<execution>:This does not (yet) work for compiled Rascal code, but the exact same interface could be implemented for generated test code (whether or not we use JUnit for that or not).