Copilot commented on code in PR #9617: URL: https://github.com/apache/gravitino/pull/9617#discussion_r2663499386
########## catalogs/hive-metastore-common/src/test/java/org/apache/gravitino/hive/TestHiveClientPool.java: ########## @@ -0,0 +1,97 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ + +package org.apache.gravitino.hive; + +import static org.junit.jupiter.api.Assertions.assertEquals; +import static org.junit.jupiter.api.Assertions.assertThrows; +import static org.junit.jupiter.api.Assertions.assertTrue; + +import com.google.common.collect.Lists; +import java.util.List; +import java.util.Properties; +import org.apache.gravitino.exceptions.GravitinoRuntimeException; +import org.apache.gravitino.hive.client.HiveClient; +import org.junit.jupiter.api.AfterEach; +import org.junit.jupiter.api.BeforeEach; +import org.junit.jupiter.api.Test; +import org.mockito.Mockito; Review Comment: Consider using static imports for Mockito methods to improve readability and align with the project's conventions. Most test files in the codebase use static imports like `import static org.mockito.Mockito.mock;`, `import static org.mockito.Mockito.spy;`, etc., instead of using `Mockito.` prefix throughout the test class. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
