You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Brian Hulette (Jira)" <ji...@apache.org> on 2021/03/03 03:22:00 UTC

[jira] [Updated] (BEAM-11436) Nullness checks are excessive for test classes

     [ https://issues.apache.org/jira/browse/BEAM-11436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Hulette updated BEAM-11436:
---------------------------------
    Fix Version/s: Not applicable
       Resolution: Fixed
           Status: Resolved  (was: Open)

> Nullness checks are excessive for test classes
> ----------------------------------------------
>
>                 Key: BEAM-11436
>                 URL: https://issues.apache.org/jira/browse/BEAM-11436
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Brian Hulette
>            Assignee: Brian Hulette
>            Priority: P2
>              Labels: stale-assigned
>             Fix For: Not applicable
>
>          Time Spent: 8h 20m
>  Remaining Estimate: 0h
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)