*            the uid to set
     */
    @Override
    public final void setUid(final int uid) {
        this.uid = uid;
    }

    /**
     * Gets the signature sequence number
     * @return the signSeq
     */
    public int getSignSeq() {
        return this.signSeq;
    }

    /**
     * Sets the signature sequence number
     * @param signSeq
     *            the signSeq to set

* Share database connections.
* Enforce security, authentication, role requirements, etc.
* And many other things...

All these, while minimizing code repetition.

## First Steps { #first-steps }

Let's see a very simple example. It will be so simple that it is not very useful, for now.

But this way we can focus on how the **Dependency Injection** system works.

  }

  /*
   * We need to perform operations in a thread pool, even for simple cases, because the queue might
   * be a SynchronousQueue.
   */
  private ExecutorService threadPool;

  @Override
  public void setUp() {
    threadPool = newCachedThreadPool();
  }

  @Override
  public void tearDown() throws InterruptedException {
    threadPool.shutdown();

import org.ietf.jgss.Oid;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

import jcifs.CIFSException;
import jcifs.spnego.NegTokenInit;

/**
 * This class used to provide Kerberos feature when setup GSSContext.
 *
 * @author Shun
 */
class Kerb5Context implements SSPContext {

    private static final Logger log = LoggerFactory.getLogger(Kerb5Context.class);

 */
class TransWaitNamedPipeResponseTest {

    @Mock
    private Configuration mockConfig;

    private TransWaitNamedPipeResponse response;

    @BeforeEach
    void setUp() {
        MockitoAnnotations.openMocks(this);
        response = new TransWaitNamedPipeResponse(mockConfig);
    }

    @Test
    @DisplayName("Constructor should initialize TransWaitNamedPipeResponse")

 */
@TestInstance(Lifecycle.PER_METHOD)
public class SecureCredentialStorageTest {

    private SecureCredentialStorage storage;
    private char[] masterPassword;

    @BeforeEach
    public void setUp() throws Exception {
        masterPassword = "MasterPassword123!@#".toCharArray();
        storage = new SecureCredentialStorage(masterPassword.clone());
    }

    @AfterEach
    public void tearDown() throws Exception {

        client = runner.client();
    }

    @AfterClass
    public static void afterClass() throws Exception {
        runner.close();
        runner.clean();
    }

    @Before
    public void setUp() {
        builder = new SuggestSettingsBuilder();
    }

    @Test
    public void testConstructor() {
        // Test default constructor
        SuggestSettingsBuilder testBuilder = new SuggestSettingsBuilder();

		uploadID          string // uploadID of the transaction.
		invalidPartNumber bool   // Sets an invalid multipart.
		maximumPartNumber bool   // Sets a maximum parts.
		accessKey         string
		secretKey         string
		// expected output.
		expectedRespStatus int
	}{

         * the first occurrence. So when we're in lenient/compat mode, we have to deal with such broken POMs and mimic
         * the way 2.x works. When we're in strict mode, the removal of duplicates just saves other merging steps from
         * aftereffects and bogus error messages.
         */
        List<Dependency> dependencies = model.getDependencies();
        Map<String, Dependency> normalized = new LinkedHashMap<>(dependencies.size() * 2);

    private SID mockSid2;

    @Mock
    private SID mockSid3;

    @Mock
    private SID mockDomainSid;

    private String testServerName;
    private SID[] testSids;

    @BeforeEach
    void setUp() {
        testServerName = "test-server.domain.com";
        testSids = new SID[] { mockSid1, mockSid2, mockSid3 };
    }

    // Test resolveSids with array
    @Test