Minimal E2E tests

[lidel]

This issue tracks the minimal set of end-to-end regression tests we want to have,
along with pointers at preexisting fixtures we could reuse.

Goal

We want a minimal set of regression tests that are easy to maintain, don't take a lot of space.

Coverage does not need to be complete. We will add gateway-conformance in the future. We need something before that happens.

Minimal regression tests

Below is a quick brain dump of E2E tests we need to tackle development going forward.

SW configuration screen

• Opening root document ends up on #ipfs-sw-config - fix: first-hit handling renders redirect page correctly #163

Critical gateway modes

We can test these in isolation with hello bytes inlined inside of identity CID:

• Confirm path gateway mode works
  • Open http://127.0.0.1:{port}/ipfs/bafkqablimvwgy3y (no subdomain possible on IPs) and confirm the response was HTTP 200 and the body was hello - test: path-routing of identity CID #146
• Confirm subdomain gateway mode detection and origin isolation works - test: e2e subdomain redirect tests #151
  • Open http://sw.localhost:{port}/ipfs/bafkqablimvwgy3y and confirm the final response was HTTP 301 to http://bafkqablimvwgy3y.ipfs.sw.localhost:{port}
  • Open http://bafkqablimvwgy3y.ipfs.sw.localhost:{port} and confirm the final response was HTTP 200 and the body was hello

Basic web hosting

We can reuse fixtures from gateway-conformance:

• Opening a directory with index.html returns index.html
  • Reuse gateway-conformance/fixtures/gateway-cache/fixtures.car (fixture info)
  • Open http://127.0.0.1:{port}/ipfs/bafybeifq2rzpqnqrsdupncmkmhs3ckxxjhuvdcbvydkgvch3ms24k5lo7q the final response was HTTP 301 to the same URL but with trailing / (http://127.0.0.1:{port}/ipfs/bafybeifq2rzpqnqrsdupncmkmhs3ckxxjhuvdcbvydkgvch3ms24k5lo7q/)
    • This one depends on Trailing / for UnixFS directory normalization is missing  #62 being resolved first.
  • Open http://127.0.0.1:{port}/ipfs/bafybeifq2rzpqnqrsdupncmkmhs3ckxxjhuvdcbvydkgvch3ms24k5lo7q/ and confirm content type is text/html and the body matches the expected byte length of index.html
• Opening UnixFS file from HAMT-sharded directory
  • Reuse gateway-conformance/fixtures/trustless_gateway_car/single-layer-hamt-with-multi-block-files.car
  • Read /ipfs/bafybeidbclfqleg2uojchspzd4bob56dqetqjsj27gy2cq3klkkgxtpn4i/685.txt, confirm content type is text/plain, and body length in bytes matches.
• HTTP Range request works and fetches only relevant blocks
  • This one depends on deps: latest @helia/verified-fetch & http range support testing #122 landign first.
  • Reuse gateway-conformance/fixtures/trustless_gateway_car/file-3k-and-3-blocks-missing-block.car: A file chunked into 3 blocks, each 1024 bytes. The middle block is missing to ensure range request only triggers fetch of necessary blocks.
  • HTTP Range: bytes=0-0 request for /ipfs/QmYhmPjhFjYFyaoiuNzYv8WGavpSRDwdHWe5B4M5du5Rtk, expect response to be HTTP 206 with body equal to the first byte of the file
  • HTTP Range: bytes=2200- request for /ipfs/QmYhmPjhFjYFyaoiuNzYv8WGavpSRDwdHWe5B4M5du5Rtk, expect response to be HTTP 206 with body equal to the expected tail of the file

[SgtPooki]

Opening root document ends up on #ipfs-sw-config

Do we want to change the landing page or do you mean we want to confirm new subdomains land on ipfs-sw-config page? or that accessing <rootDomain>/#/ipfs-sw-config loads the config page

The rest make sense

[lidel]

I meant just a quick smoke test to confirm config page is rendered on initial load, when there is no SW.

Have separate one for sw.localhost domain, and cid.ipfs.sw.localhost:port subdomain, as we may enable autoreload for subdomain at some point, and it will require separate test anyway.

[SgtPooki]

@lidel all e2e tests are merged in except tests for confirming config/redirect page loading

Only thing is a question I had in #159 regarding testing all 872 bytes for the Range: bytes=2200- request for /ipfs/QmYhmPjhFjYFyaoiuNzYv8WGavpSRDwdHWe5B4M5du5Rtk test

[SgtPooki]

#162 was also merged that can allow for testing inbrowser.dev and inbrowser.link.