Need an example for multiple tests adding up to 100

[education]

Need an example for multiple tests adding up to 100

[shaharyi]

An update:
I found in Gradle CLI docs that you can specify the test classes:
gradle test --tests MyTestClass
But If there is a compilation problem in ANY of the tests, the score is zero.
Only if all tests compile, each of them get their respective points.
Is there a way to easily fix this, perhaps in Gradle or Actions config?

[stevenbitner]

I'm no Gradle expert, but I had a similar issue in the past and used the sourceSets attribute to exclude all classes that were not required for a given test. For example:

task test_constructor (type: Test) {
	filter.includeTestsMatching "ConstructorTest"
}

// other test tasks here
// ....

sourceSets {
    if (project.gradle.startParameter.taskNames.contains("test_constructor")) {
        test.java.exclude '**/LotsOfGuessesTest*'
        test.java.exclude '**/TestMain*'
        test.java.exclude '**/TestMainLoop*'
        sourceSets.main.java.excludes = ['Main*']
    }
    else if (project.gradle.startParameter.taskNames.contains("test_loser")) {
        test.java.exclude '**/TestMain*'
        test.java.exclude '**/TestMainLoop*'
        sourceSets.main.java.excludes = ['Main*']
    }
    else if (project.gradle.startParameter.taskNames.contains("test_lots_of_guesses")) {
        test.java.exclude '**/TestMain*'
        test.java.exclude '**/TestMainLoop*'
        sourceSets.main.java.excludes = ['Main*']
    }
    else if (project.gradle.startParameter.taskNames.contains("test_main")) {
        test.java.exclude '**/TestMainLoop*'
    }
}

Then, in my autograding.json file I call the tests one by one. To call the "constructor" test from the Gradle snippet above for instance, the test is:

{
  "name": "Test constructors",
  "setup": "",
  "run": "timeout 60 gradle test_constructor",
  "input": "",
  "output": "",
  "comparison": "included",
  "timeout": 1,
  "points": 20
}

I hope this helps.

[shaharyi]

I'll try that, thanks Steve!

…

On Thu, Nov 3, 2022 at 9:00 PM Steve Bitner ***@***.***> wrote: I'm no Gradle expert, but I had a similar issue in the past and used the sourceSets attribute to exclude all classes that were not required for a given test. For example: task test_constructor (type: Test) { filter.includeTestsMatching "ConstructorTest" } // other test tasks here// .... sourceSets { if (project.gradle.startParameter.taskNames.contains("test_constructor")) { test.java.exclude '**/LotsOfGuessesTest*' test.java.exclude '**/TestMain*' test.java.exclude '**/TestMainLoop*' sourceSets.main.java.excludes = ['Main*'] } else if (project.gradle.startParameter.taskNames.contains("test_loser")) { test.java.exclude '**/TestMain*' test.java.exclude '**/TestMainLoop*' sourceSets.main.java.excludes = ['Main*'] } else if (project.gradle.startParameter.taskNames.contains("test_lots_of_guesses")) { test.java.exclude '**/TestMain*' test.java.exclude '**/TestMainLoop*' sourceSets.main.java.excludes = ['Main*'] } else if (project.gradle.startParameter.taskNames.contains("test_main")) { test.java.exclude '**/TestMainLoop*' } } Then, in my autograding.json file I call the tests one by one. To call the "constructor" test from the Gradle snippet above for instance, the test is: { "name": "Test constructors", "setup": "", "run": "timeout 60 gradle test_constructor", "input": "", "output": "", "comparison": "included", "timeout": 1, "points": 20 } I hope this helps. — Reply to this email directly, view it on GitHub <#56 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH66V74TLPPDZDL4TUDT6OTWGQDVHANCNFSM542U26ZQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>