AbstractBuildResultLoggerFunctionalTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Move some console functional test coverage to `logging` to live with the other console test coverage. Also add more coverage for the reporting of the build result at the end of the build (actionable tasks, and so on).

    • -75
    • +0
    ./AbstractBuildResultLoggerFunctionalTest.groovy
  1. … 11 more files in changeset.
Add assertRawErrorOutput method to execution result fixtures

    • -3
    • +3
    ./AbstractBuildResultLoggerFunctionalTest.groovy
  1. … 5 more files in changeset.
Add test coverage for console attached to stderr but not stdout

    • -2
    • +2
    ./AbstractBuildResultLoggerFunctionalTest.groovy
  1. … 9 more files in changeset.
Simplify ConsoleAttachment so that it always carries the console metadata with it

    • -0
    • +1
    ./AbstractBuildResultLoggerFunctionalTest.groovy
  1. … 10 more files in changeset.
Make rich/verbose consoles behave similar to plain when streams are not attached

    • -2
    • +2
    ./AbstractBuildResultLoggerFunctionalTest.groovy
  1. … 24 more files in changeset.
Fix BuildResult logging tests

    • -7
    • +11
    ./AbstractBuildResultLoggerFunctionalTest.groovy
  1. … 12 more files in changeset.
Split CodeNarc configuration for integration tests

Now that there are rules specific to integration tests, we have a dedicated

configuration file. This should avoid some accidental noise, and removes

the need to check for `Integration` in the test name, which helped discover

a few more problems.

    • -0
    • +1
    ./AbstractBuildResultLoggerFunctionalTest.groovy
  1. … 7 more files in changeset.
Ensure console tests run with plain, rich and verbose modes

    • -0
    • +69
    ./AbstractBuildResultLoggerFunctionalTest.groovy
  1. … 19 more files in changeset.