Stress-Test Deployment

Now test the path beyond your laptop.

Test 1: deploy a small reviewed change

Change one harmless visible sentence or project field.

Commit it.

Push through your normal deployment path.

Tie the public result to:

commit → workflow/deployment → public output

Test 2: base-path-sensitive asset/link

Verify one project link and one image/CSS asset using the actual production URL.

Test 3: failed deployment evidence

If you have a safe disposable branch/repository or instructor-provided scenario, inspect a failed Pages build/deploy run.

Do not intentionally break a production site other people depend on.

Classify:

source/build failure
artifact/upload failure
deploy/environment failure
public-site content failure

Test 4: recovery path

Identify a known-good commit.

Explain how your project workflow would restore/replace a bad release through Git history and the normal deployment system.

Test 5: public privacy check

Inspect the actual deployed site and repository as an unauthenticated/public visitor where possible.

What can they see that you forgot was public?

Checkpoint

Your deployment is defensible when you can identify what is live, where it came from, and what evidence you would use to recover from a bad release.