func TestParserParse(t *testing.T) {
	// Iterate over test data set and run tests
	for _, data := range jwtTestData {
		t.Run(data.name, func(t *testing.T) {
			// Parse the token
			var err error

			// Figure out correct claims type
			switch claims := data.claims.(type) {
			case *MapClaims:
				if data.tokenString == "" {
					data.tokenString = mapClaimsToken(claims)
				}

        assertNotNull(result);
        assertNotNull(result.getContent());
    }

    /**
     * Test that null input stream throws CrawlerSystemException with correct message.
     */
    public void test_getText_nullInputStream_throwsWithMessage() {
        try {
            textExtractor.getText(null, null);
            fail("Expected CrawlerSystemException");

    withContext(Dispatchers.IO) {
      fileSystem.write(outputFile) {
        importResults.writeOut(this)
      }
    }

  /**
   * These assertions ensure the [PublicSuffixDatabase] remains correct. The specification is
   * very flexible regarding wildcard rules, but this flexibility is not something currently used
   * in practice. To simplify the implementation, we've avoided implementing the flexible rules in

    /** The specified user already exists */
    int NT_STATUS_USER_EXISTS = 0xC0000063;
    /** The specified user does not exist */
    int NT_STATUS_NO_SUCH_USER = 0xC0000064;
    /** The specified network password is not correct */
    int NT_STATUS_WRONG_PASSWORD = 0xC000006a;
    /** Logon failure: unknown user name or bad password */
    int NT_STATUS_LOGON_FAILURE = 0xC000006d;
    /** Logon failure: user account restriction */

    @Test
    void testWitnessEventTypes() {
        assertEquals(7, WitnessEventType.values().length);

        WitnessEventType[] events = WitnessEventType.values();

        // Verify all expected event types with correct values
        assertEquals(1, WitnessEventType.RESOURCE_CHANGE.getValue());
        assertEquals(2, WitnessEventType.CLIENT_MOVE.getValue());
        assertEquals(3, WitnessEventType.SHARE_MOVE.getValue());

  the network is not). Therefore, let's concentrate on the state where no
  network <beyond localhost> exists, and leave the more extreme state to users
  to diagnose and correct as necessary.

* Why is Offline Mode Important?

  Offline mode is essential for breaking the requirement that m2 operate in a
  network-connected environment. It means legitimizing a development environment

				pop := dirStack[len(dirStack)-1]
				select {
				case <-ctx.Done():
					return ctx.Err()
				case out <- metaCacheEntry{name: pop}:
				}
				if opts.Recursive {
					// Scan folder we found. Should be in correct sort order where we are.
					err := scanDir(pop)
					if err != nil {
						if errors.Is(err, context.Canceled) {
							return err
						}
						internalLogIf(ctx, err)
					}
				}

        }
    }

    @Nested
    @DisplayName("Size Calculation Tests")
    class SizeTests {

        @ParameterizedTest
        @DisplayName("Should calculate correct size for various path lengths")
        @CsvSource({ "'', 4", "'a', 6", "'\\\\', 8", "'\\\\server', 20", "'\\\\server\\share', 32", "'\\\\server\\share\\path', 42",

            int terminationPos = Strings.findUNITermination(bufferWithTermination, 0, bufferWithTermination.length);

            // Then
            assertEquals(stringBytes.length, terminationPos, "Should find termination at correct position");
        }

        @Test
        @DisplayName("findUNITermination should throw exception when termination not found")
        void testFindUNITerminationNotFound() {
            // Given

     */
    public void setHeartbeatInterval(long heartbeatInterval) {
        this.heartbeatInterval = heartbeatInterval;
    }

    /**
     * Validates that the heartbeat response is correct.
     * The response sequence number should match the request sequence number.
     *
     * @return true if the response is valid
     */
    public boolean isValidResponse() {