Giter Club home page Giter Club logo

Comments (5)

wujek-srujek avatar wujek-srujek commented on August 11, 2024

Gradle 3.0 now provides such separation by default, so whatever this plugin sets should be undone when 3.0 is used to be consistent with Gradle defaults.

from gradle-testsets-plugin.

rkrisztian avatar rkrisztian commented on August 11, 2024

Indeed Gradle 3 organizes test results and reports much better (see JavaBasePlugin). I would like to see these conventions followed by the TestSets plugin:

        xmlReport.getConventionMapping().map("destination", new Callable<Object>() {
            public Object call() throws Exception {
                return new File(convention.getTestResultsDir(), test.getName());
            }
        });
        htmlReport.getConventionMapping().map("destination", new Callable<Object>() {
            public Object call() throws Exception {
                return new File(convention.getTestReportDir(), test.getName());
            }
        });
        test.getConventionMapping().map("binResultsDir", new Callable<Object>() {
            public Object call() throws Exception {
                return new File(convention.getTestResultsDir(), test.getName() + "/binary");
            }
        });

The current solution makes the build directory look rather messy.

from gradle-testsets-plugin.

wujek-srujek avatar wujek-srujek commented on August 11, 2024

If it is of any help, this is what I currently use to un-do the customizations introduced by this plugin:

afterEvaluate {
    tasks.withType(Test) {
        // the testsets plugin changes test report and result directories but they are mixed up
        // and different than Gradle 3.x defaults (the plugin existed before that)
        // set the directories as Gradle itself would do it
        reports.html.destination = new File(project.testReportDir, name)
        reports.junitXml.destination = new File(project.testResultsDir, name)

from gradle-testsets-plugin.

dbalakirev avatar dbalakirev commented on August 11, 2024

The workaround proposed by @wujek-srujek works fine.

However I am hoping to see my PR merged (see linked above).

from gradle-testsets-plugin.

tkrullmann avatar tkrullmann commented on August 11, 2024

Marking this as fixed. Thanks @dbalakirev!

from gradle-testsets-plugin.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.