Skip to content

Testing

phil/well-known-bundle
AreaWhat is covered
WellKnownPathNames, absolute paths, route names, the bounds, every refused path
SecurityTxtEvery field and its order, the required ones, each refused value, Expires dates and days the calendar lacks
WebFingerQuery, WebFingerResourceacct:, https: and other schemes, normalization, repeated rel, the bounds, every refused query
WebFingerDescriptor, WebFingerLink, WebFinger, StaticWebFingerResolverThe JRD written, merging, filtering by relation, resolvers in order
NodeInfo, NodeInfoSoftware, NodeInfoUsage, ConfiguredNodeInfoProviderThe 2.1 document, empty objects, every refused value
DidDIDs, methods, the bounds
The documentsBodies, media types, CORS, redirects, signing, hosts, 400 and 404
WellKnownControllerCache headers, ETag and 304, a document's own cache, errors and redirects, an unknown document
WellKnownRouteLoaderRoutes, methods, defaults, the cache resource, the type
PhilWellKnownBundle, WellKnownServices, WellKnownPassDefaults, every document, files, every refused configuration, file and tag
SecurityTxtExpiryCheckUp, degraded from the warning, down from Expires, the days rounded up, the date in UTC, the refused warning, its registration
A whole applicationEvery document served with its headers, 304 and HEAD, the bodies, the signer, WebFinger with a resolver, change-password, 405, every address a 404 when its document is off, and the expiry among the checks of phil/monitoring-bundle
vendor/bin/phpunit packages/well-known-bundle/tests

Fuzzing

The webfinger-query target reads text nobody wrote as a WebFinger query: it returns a query whose resource reads back to the same URI, or throws InvalidValue, and nothing else. From the monorepo root:

PHIL_DEV_PACKAGES=well-known-bundle composer fuzz

Benchmarks

WebFingerBench serves a WebFinger query among 1,000 accounts, an unknown account, and a fixed document, through the controller:

composer bench -- packages/well-known-bundle/tests/Benchmark