# 2023-04-02 [Cover Reports](https://github.com/diffblue/website-docs/blob/develop/knowledge-base/diffblue-cover-reports/getting-started/README.md), Diffblue's offering to provide a variety of ways to visualise an application based on information derived from Diffblue Cover, now allows restricting reports uploading to users/clients with a configured username and password. By default, Diffblue Cover will allow any user to upload files to Cover Reports. However, you may want to limit access so that only certain users can upload files. For example, you may choose to enable authentication if you only want your CI processes to upload data for a project, so that data is comparable and uploaded with a consistent timespan. See the [Authenticating Cover Reports Uploads documentation](https://github.com/diffblue/website-docs/blob/develop/knowledge-base/diffblue-cover-reports/authentication/README.md) for more details. ## Enhancements * Reports: Cover now supports restricting uploading of reports to users with a configured username and password. See the [Authenticating Cover Reports Uploads documentation](https://github.com/diffblue/website-docs/blob/develop/knowledge-base/diffblue-cover-reports/authentication/README.md) for more details. \[Ref: TG-18859] * Cover now provides a stack trace when it encounters `R012` (JNI sandbox policy violation) to help identify the reason tests could not be written. \[Ref: TG-18729] * Cover now uses improved inputs while writing tests for methods with complex logic containing `Collection`s and `List`s. \[Ref: TG-18673] * CLI: Cover now provides snippets of code to be added to POM files without `ERROR` and `WARN` line prefixes to make copy and pasting easier. \[Ref: TG-16741] * IntelliJ Plugin: Cover now reports more project checks in the Project Environment Health Check panel. \[Ref: TG-18790] * IntelliJ Plugin: Cover now supports automated fixing of projects with a missing `junit-jupiter-engine` dependency via the Project Environment Health Check panel. \[Ref: TG-18904] ## Resolved Issues * Resolved an issue which caused Cover to fail to parse test results with a custom Gradle validation task. \[Ref: TG-18984] * Resolved an issue which, in some circumstances, caused Cover to not write tests for setters with an `Object` argument setting an `int`. \[Ref: TG-18965] * Resolved an issue which, in some circumstances, caused Cover to not write tests for some methods due to problems with resolving generic types. \[Ref: TG-18654] * IntelliJ Plugin: Resolved an issue which caused Cover to report errors while attempting to write tests on packages above the `main` package. \[Ref: TG-18807] * IntelliJ Plugin: Resolved an issue which caused Cover to select a suboptimal working directory (such as `src/main`) when writing tests for Gradle projects. \[Ref: TG-18102] * Reports: Resolved an issue which caused Cover to not update project group pages when new data was uploaded. \[Ref: TG-17927] ## Known Issues * Cover may produce tests for JUnit 4.10 and lower that do not compile due to the use of `assertNotEquals`. \[Ref: TG-17605] * Reports: Firefox users may encounter `It seems like we encountered an error. Try refreshing this page or contact your administrator.` while loading the Coverage Reports tab. \[Ref: TG-18257] * IntelliJ Plugin: Upgrading to IntelliJ IDEA 2022.3 may, in some circumstances, cause existing run configurations to no longer produce tests. Removing any run configurations for that entity and writing tests again will recreate a working run configuration. \[Ref: TG-18282] --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://cover-docs-preview.diffblue.com/updates-and-upgrades/release-archive/2023-04-02.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.