Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-11436

Nullness checks are excessive for test classes

    XMLWordPrintableJSON

Details

    Description

      We don't have checkerframework nullness annotations for JUnit, which often leads to difficult nullness errors. The most onerous is that assertNotNull requires the argument to be NonNull already.

      Attachments

        Issue Links

          relates to

          Improvement - An improvement or enhancement to an existing feature or task. BEAM-10402 [Umbrella] Eliminate nullability errors from Beam Java

          • P3 - Non-urgent bugs, features, and improvements
          • Open
          links to

          Web Link GitHub Pull Request #14101

          Activity

            People

              bhulette Brian Hulette
              bhulette Brian Hulette
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 8h 20m
                  8h 20m