import jcifs.internal.smb2.ServerMessageBlock2;
import jcifs.internal.smb2.Smb2Constants;
import jcifs.internal.util.SMBUtil;

/**
 * Test class for Smb2CloseRequest functionality
 */
@DisplayName("Smb2CloseRequest Tests")
class Smb2CloseRequestTest {

    private Configuration mockConfig;
    private CIFSContext mockContext;
    private byte[] testFileId;
    private String testFileName;
    private Smb2CloseRequest request;

package tests_test

import (
	"context"
	"errors"
	"testing"
	"time"

	"gorm.io/gorm"
	. "gorm.io/gorm/utils/tests"
)

func TestTransaction(t *testing.T) {
	tx := DB.Begin()
	user := *GetUser("transaction", Config{})

	if err := tx.Save(&user).Error; err != nil {
		t.Fatalf("No error should raise, but got %v", err)
	}

	if err := tx.First(&User{}, "name = ?", "transaction").Error; err != nil {

這裡我們在應用的啟動事件中建立資料表。

在正式環境中，你大概會在啟動應用前使用遷移腳本來處理。🤓

/// tip | 提示

SQLModel 之後會提供包裝 Alembic 的遷移工具，但目前你可以直接使用 [Alembic](https://alembic.sqlalchemy.org/en/latest/)。

///

### 建立 Hero { #create-a-hero }

因為每個 SQLModel 模型同時也是一個 Pydantic 模型，你可以在「型別標註」中像使用 Pydantic 模型一樣使用它。

例如，如果你宣告一個參數型別為 `Hero`，它會從「JSON body」中讀取。

import org.codelibs.fess.util.ComponentUtil;
import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.TestInfo;

/**
 * Test class for Set-based field lookup improvements in QueryFieldConfig.
 * This class tests the performance and correctness of Set-based lookups
 * for search fields, facet fields, and sort fields.
 */
public class QueryFieldConfigSetBasedLookupTest extends UnitFessTestCase {

import java.util.Objects;
import junit.framework.Test;
import junit.framework.TestCase;
import junit.framework.TestSuite;
import org.jspecify.annotations.NullMarked;
import org.jspecify.annotations.Nullable;

/**
 * Tests for {@link Collections2}.
 *
 * @author Chris Povirk
 * @author Jared Levy
 */
@GwtCompatible
@NullMarked
public class Collections2Test extends TestCase {
  @J2ktIncompatible
  @GwtIncompatible // suite

import org.junit.jupiter.api.DisplayName;
import org.junit.jupiter.api.Test;
import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.ValueSource;

/**
 * Unit tests for ServerData class
 */
public class ServerDataTest {

    private ServerData serverData;

    @BeforeEach
    public void setUp() {
        serverData = new ServerData();
    }

    /**

import org.junit.jupiter.params.provider.ValueSource;
import org.mockito.Mock;
import org.mockito.junit.jupiter.MockitoExtension;

/**
 * Test class for SocketInputStream using JUnit 5 and Mockito.
 * Tests the NetBIOS session layer protocol implementation.
 */
@ExtendWith(MockitoExtension.class)
class SocketInputStreamTest {

    /**
     * Creates a NetBIOS session message header.
     * The header format is:

import jcifs.ntlmssp.av.AvTargetName;
import jcifs.ntlmssp.av.AvTimestamp;

/**
 * Test class for NTLMSSP Type 3 Message functionality
 */
@ExtendWith(MockitoExtension.class)
@DisplayName("Type3Message Tests")
class Type3MessageTest {

    @Mock
    private CIFSContext mockContext;

    @BeforeEach
    void setUp() {
        // Basic setup for mock context if needed
    }

    /**

import java.math.BigInteger;
import java.util.List;
import java.util.Set;
import junit.framework.Test;
import junit.framework.TestSuite;
import org.jspecify.annotations.NullUnmarked;

/**
 * Tests for {@link ImmutableRangeSet}.
 *
 * @author Louis Wasserman
 */
@GwtIncompatible // ImmutableRangeSet
@NullUnmarked
public class ImmutableRangeSetTest extends AbstractRangeSetTest {

  // We ought to be able to implement GenericDeclaration instead its parent AnnotatedElement.
  // That would give us this method declaration. But for some reason, implementing
  // GenericDeclaration leads to weird errors in Android tests:
  // IncompatibleClassChangeError: interface not implemented
  /** See {@link java.lang.reflect.GenericDeclaration#getTypeParameters()}. */
  public abstract TypeVariable<?>[] getTypeParameters();