App-DocKnot

 view release on metacpan or  search on metacpan

t/data/generate/remctl/docknot.yaml  view on Meta::CPAN

    functions.  For the full test suite, you will need to have a keytab that
    can authenticate to a running KDC.  Using a test KDC environment, if you
    have one, is recommended.

    Follow the instructions in `tests/config/README` to configure the test
    suite.

    Now, you can run the test suite with:
  suffix: |
    On particularly slow or loaded systems, you may see intermittent failures
    from the `server/streaming` test because it's timing-sensitive.

    The test suite will also need to be able to bind to 127.0.0.1 on port
    11119 and 14373 to run test network server programs.

    To test anonymous authentication, the KDC configured in the test suite
    needs to support service tickets for the anonymous identity (not a
    standard configuration).  This test will be skipped if the KDC does not
    support this.

    To test user handling in remctld, you will need the `fakeroot` command

t/data/generate/remctl/output/readme  view on Meta::CPAN

      make check

  If a test fails, you can run a single test with verbose output via:

      tests/runtests -o <name-of-test>

  Do this instead of running the test program directly since it will
  ensure that necessary environment variables are set up.

  On particularly slow or loaded systems, you may see intermittent
  failures from the server/streaming test because it's timing-sensitive.

  The test suite will also need to be able to bind to 127.0.0.1 on port
  11119 and 14373 to run test network server programs.

  To test anonymous authentication, the KDC configured in the test suite
  needs to support service tickets for the anonymous identity (not a
  standard configuration).  This test will be skipped if the KDC does not
  support this.

  To test user handling in remctld, you will need the fakeroot command

t/data/generate/remctl/output/readme-md  view on Meta::CPAN

If a test fails, you can run a single test with verbose output via:

```
    tests/runtests -o <name-of-test>
```

Do this instead of running the test program directly since it will ensure
that necessary environment variables are set up.

On particularly slow or loaded systems, you may see intermittent failures
from the `server/streaming` test because it's timing-sensitive.

The test suite will also need to be able to bind to 127.0.0.1 on port
11119 and 14373 to run test network server programs.

To test anonymous authentication, the KDC configured in the test suite
needs to support service tickets for the anonymous identity (not a
standard configuration).  This test will be skipped if the KDC does not
support this.

To test user handling in remctld, you will need the `fakeroot` command

t/data/update/remctl/docknot.yaml  view on Meta::CPAN

    functions.  For the full test suite, you will need to have a keytab that
    can authenticate to a running KDC.  Using a test KDC environment, if you
    have one, is recommended.

    Follow the instructions in `tests/config/README` to configure the test
    suite.

    Now, you can run the test suite with:
  suffix: |
    On particularly slow or loaded systems, you may see intermittent failures
    from the `server/streaming` test because it's timing-sensitive.

    The test suite will also need to be able to bind to 127.0.0.1 on port
    11119 and 14373 to run test network server programs.

    To test anonymous authentication, the KDC configured in the test suite
    needs to support service tickets for the anonymous identity (not a
    standard configuration).  This test will be skipped if the KDC does not
    support this.

    To test user handling in remctld, you will need the `fakeroot` command

t/data/update/remctl/old/test/suffix  view on Meta::CPAN

On particularly slow or loaded systems, you may see intermittent failures
from the `server/streaming` test because it's timing-sensitive.

The test suite will also need to be able to bind to 127.0.0.1 on port
11119 and 14373 to run test network server programs.

To test anonymous authentication, the KDC configured in the test suite
needs to support service tickets for the anonymous identity (not a
standard configuration).  This test will be skipped if the KDC does not
support this.

To test user handling in remctld, you will need the `fakeroot` command