d5d0fae4bb
prpl_core.yml now pulls strongswan-default and sixteen strongswan modules for the IPsec datamodel. They drag in dependencies nothing selects explicitly -- strongswan-ipsec via mod-stroke, and libgcrypt plus libgpg-error via mod-gcrypt -- so every board that ships strongswan sees a wider package set than its expected output records. Refresh the expectations for the three boards that build strongswan: - 005-build-config.t on mxl25641-hdk-6, wnc-freedom and urx851-b0-dk. urx851-b0-dk has no hardware test job, so its copy of the same expected output would have drifted unnoticed until the board is exercised again; keep the three in sync. - 011-tls.t on mxl25641-hdk-6 and wnc-freedom. The grep pattern and the version-tolerant libopenssl / libustream-openssl regexes are left untouched; only strongswan-mod-openssl is added. Enumerating the whole strongswan package set belongs in 005-build-config.t, not in a test whose subject is the single TLS library. The same module set also widens what charon advertises through the IPsec root object. Rather than track those capability strings, 133-tr181-ipsec.t now asserts only that the datamodel starts with no entries, so the expectation no longer moves with the strongswan module selection. Also drop CONFIG_VERSION_CODE_FILENAMES from the wnc-freedom expected build config. The symbol is no longer emitted, which is OpenWrt base drift rather than a VPN change, but the expectation cannot pass while it is listed. References: FEAT-150, PCF-2467 Signed-off-by: Alexandre Fiset <alexandre.fiset@softathome.com> |
||
|---|---|---|
| .. | ||
| cram | ||
| README.md | ||
Content
This directory contains tests.
cram
Contains Cram based tests. Cram is a functional testing framework for command line applications. Cram tests look like snippets of interactive shell sessions. Cram runs each command and compares the command output in the test with the command's actual output.
Tests in this directory should be run against device, usually over network via SSH connection.