FullExceptionFormatterTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Retain stacktrace when test method is inherited

By default Gradle is trying to find "test class name" in the stacktrace (which is smart!), however,

there are cases when test class name never appears in the stacktrace.

For instance, it might happen when test class uses inheritance.

The inheritance is typically used to test over different implementations.

The fix is to retain the stacktrace in case none of the lines match.

fixes #11220

Signed-off-by: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>

    • -0
    • +20
    ./FullExceptionFormatterTest.groovy
  1. … 7 more files in changeset.
Make ClassMethodNameStackTraceSpec support anonymous class matching (#4797)

Make ClassMethodNameStackTraceSpec support anonymous class matching

This fixes https://github.com/gradle/gradle/issues/4681

Previously, when TestExceptionFormatter formats test stacktraces, it tries to

find the exactly matched class/method name as stacktrace truncation point.

However, some kotlin-based tests have only anonymous classes in their stacktraces,

which makes it impossible to find the exact truncation point. This PR treats

`SomeClass$1$1$1` and `SomeClass` equally when performing class name matching.

    • -0
    • +19
    ./FullExceptionFormatterTest.groovy
  1. … 2 more files in changeset.
Busted up some package cycles and switched on classcycle checks for 'messaging' project.

  1. … 32 more files in changeset.
Moved `o.g.messaging.*` to `o.g.internal.*`.

  1. … 295 more files in changeset.
Start migrating test classes to the most appropriate subproject

Story: gradle/langos#103

Item: refactor-plugins

    • -0
    • +252
    ./FullExceptionFormatterTest.groovy
  1. … 124 more files in changeset.