TEST: 51Did browser acceptance tests, driving the PMP demo

[jwrosewell]

Why

The browser tests belong in this shared suite so that the same tests can
check every implementation. They drive the demo where the preference
platform lives, with everything the tests need placed in that demo, so that
when the demo is copied into the other languages the same tests show every
copy behaves the same way.

So the fifteen 51Did browser acceptance tests move here from the cloud
service, where they were drafted, and drive the demo Examples/Cloud/pmp-web
in
device-detection-dotnet-examples
(device-detection-dotnet-examples#952)
instead of pages the tests built themselves. The demo was moved to
Examples/Cloud/pmp-web, with the project file pmp-web.csproj, from its earlier folder on 15 September 2026.

What is here

Six commits, the fifth and sixth under the review follow up below. 34558ec is the tests exactly as they were when drafted, with
only the namespace moved and a nullable context added, so a reviewer can
compare them line for line. 6f07e30 makes them drive the demo, e1a9d70
corrects one test's description of how PMP finds the client script,
which is by its tag, and 69499f0 reads the resource key from the names
51Degrees agreed for keys and launches the demo from its new path.

• Browser51Did/, category Browser51Did. What the tests prove, the route
  each loads and the variables are in
  Browser51Did/README.md.
• Examples/ExampleApps.cs gains ExampleApps.Demos and TryCreateDemo.
  The dotnet demo is launched from Examples/Cloud/pmp-web the way the GettingStarted-Web
  example is, with exactly 51DEGREES_RESOURCE_KEY,
  51DEGREES_CLOUD_ENDPOINT and ASPNETCORE_URLS. A demo is chosen with
  DEMO_URL or DEMO_LANG, apart from the Contract tests' EXAMPLE_URL and
  EXAMPLE_LANG, because the two are different apps. DEMO_MODE chooses
  cloud or pipeline pages, and the client script's request path comes
  from that mode.
• The key and endpoint names follow the 51Degrees naming scheme agreed on
  8 September 2026. The suite reads 51DEGREES_RESOURCE_KEY first and
  _51DEGREES_RESOURCE_KEY_51DID where that is unset, which is the name CI
  sets for a resource key carrying the 51Did product, and always hands the
  key to the demo as 51DEGREES_RESOURCE_KEY. The endpoint is
  51DEGREES_CLOUD_ENDPOINT alone. DEMO_URL, DEMO_LANG and DEMO_MODE
  choose the demo rather than carry a key, so the scheme does not name them.
• Browser51DidTestAttribute takes the resource key out of every test
  result, being messages, stack traces and output, because this repository
  and its CI logs are public and a failure message routinely quotes a script
  source naming the key. A test not marked with it fails.
• Every assertion from the cloud copy is kept, and the consent test also
  checks the stub delivers exactly TcString.Personalized().
• The common path's ordering assertion counts rounds inside the page, at the
  press and at the first frame the share card is visible. Polling from the
  test failed 3 times in 7 before the move and once in 10 over HTTPS after
  it, and a timeline recorded in the page showed the card visible 198 ms
  before the answered round finished in the failing run, so the page had not
  waited and the poll had looked late.

Proof

Against a locally run cloud on http://localhost:5050 carrying the client
script from javascript-templates eb02894 through
FiftyOne.Pipeline.JavaScriptBuilder 4.5.105-createlast.1, with the dotnet
demo launched by the suite:

Total tests: 15
     Passed: 14
    Skipped: 1

The skip is IsGdpr_ReadFromTheClientScript_SetsGdprApplies, which cannot
pass until IsGdpr is released in the cloud and says so. The guard reported
Client script guard passed for the dotnet demo's /cloud/ pages, with the
iteration limit message and __51d_pmp found in the served script. The
unredacted output of that run held the resource key no times.

The common path over HTTPS, run alone ten times against the same demo with
the in-page measure, passed ten times.

After 69499f0, dotnet build -c Release gave 0 warnings and 0 errors, and
the category run with neither resource key name set gave 15 skipped, each
reason naming 51DEGREES_RESOURCE_KEY and _51DEGREES_RESOURCE_KEY_51DID.
The run of 14 passed and 1 skipped above was on e1a9d70 with the demo at
its old path, and has not been repeated since the move.

Outstanding

• /pipeline/ mode now runs against the demo's /pipeline/ pages. There the
  suite gave 15 tests, 8 passed, 6 failed and 1 skipped. Five failures are
  the share card, which PMP now shows only where third party
  cookies are confirmed, and one is a defect in this suite's
  NoClientScriptTag_PmpAddsItAndTheAnswerStillCreates in that mode,
  described in the demo pull request.
• The consumer that runs this category stopped on its first run at the
  check for the new client script, as it must until the cloud release
  carries that script.
• The tests that create a 51Did for a standard or personalized answer need
  a resource key whose products include CloudV5FODiD. The consumer that runs
  this category builds a throwaway record from the licence in
  _51DEGREES_LICENSE_KEY_51DID. The harness asks the service first, and
  skips with the service's own reason when the key cannot create.
• The consumer that runs this suite pins both this repository and the demo
  repository, and the two pins have to move together, to bf56d0e or later
  here and to the demo commit that carries Examples/Cloud/pmp-web,
  because this suite now launches the demo from the new path.

Depends on

It merges together with the demo pull request,
device-detection-dotnet-examples#952,
after the cloud release that carries the new client script.

Review follow up, 15 September 2026

• 13a6692 DOC: Say what the pipeline mode proves now the demo serves its
  pages. Browser51Did/README.md said every run uses /cloud/ until a demo
  serves the pipeline pages, and that the tests about the PMP adding a
  script prove the cloud's script in either mode. Both were stale once the
  demo gained /pipeline/ and 69499f0 wired the mode in. The section now
  says the dotnet demo serves /pipeline/, that those pages show the user
  prompt block only with the pipeline packages carrying the new template,
  and that NoClientScriptTag_PmpAddsItAndTheAnswerStillCreates fails
  in that mode because Visitor.ClientRequests looks on the pipeline's
  path while the PMP adds the cloud's script. Step 2 of adding a demo in
  another language names /pipeline/ too. Verified by reading Demo.cs
  (DemoMode.JsonEndpointPath), Visitor.cs lines 165 to 170 and
  PmpAddsClientScriptTests.cs lines 89 and 94. dotnet build SeleniumApiTests.csproj at 69499f0 gave 0 warnings and 0 errors, and
  a README change does not alter that. The commit count under "What is
  here" was four and is corrected to five in this edit.

Review follow up, 16 September 2026

• bf56d0e FIX: Say PMP throughout, and drop a helper naming an address
  that is going away. Two things. First the naming rule, which is that every
  name uses pmp and every sentence says PMP rather than "the platform".
  PlatformAcceptanceTests and PlatformAddsClientScriptTests are renamed
  with their files, along with Visitor.WaitForPmp, PmpLoaded, PmpState,
  PmpPreference, OpenPmp, Harness.NoPmpMessage, the five test methods
  and the CommonPath parameter. Three things keep the older spelling on
  purpose and the commit message says why: Routes.NoPlatform and
  Routes.PlatformOnly, whose values are the URL paths the demo serves, so
  renaming the pair needs the demo's own page names to move in the same
  release; the client script's own console wording, which NoPmpMessage
  matches as a substring; and the consent platform tests, where a consent
  management platform is a different product from PMP.
• Second, Harness.PlatformLoaderUrl() named {CloudUrl}/api/v4/pmp and
  nothing called it. That address answers 404 once the loader takes the
  resource key in its path, as api/v4/pmp/<resource key>.js, so the helper
  is removed rather than corrected. An address the suite does not ask for is
  better absent than wrong.
• Four comments pointed at another repository's internal paths and change
  numbers, which a reader here cannot follow, and one of them printed into
  the test output. Each now says what the thing is instead. The same goes for
  the references to an internal list of demonstrations.
• dotnet build SeleniumApiTests.csproj -c Release gave 0 warnings and
  0 errors after the rename. The change is names and comments only, so the
  run recorded under Proof still stands, and the browser run has not been
  repeated since.