Customer Portal - Staging Acceptance
91-web-project-acceptance.yaml
HTTP(S)
What this example does
Technical project acceptance: Customer Portal - Staging Acceptance. Use the YAML as a reviewable checklist and retain the test output as supporting evidence.
Checks and behavior
- Sends an GET request to https://portal.example.com/health.
- Checks allowed/denied HTTP status codes.
- Validates required, forbidden or matching HTTP headers.
- Looks for expected response content and/or rejects known error markers.
- TLS settings cover certificate trust, certificate expiry.
- Applies response-time thresholds for operational alerting.
- Formats results for text output.
Adapt example domains, addresses, credentials and thresholds to your environment before use.
YAML configuration
# Copyright (c) 2026 mati peterson. Maintainer: mati peterson <ipsonic@mailbox.org>. Project: https://ipsonic.com/probe/. Disclaimer: Provided AS IS, without warranty of any kind. Use at your own risk; validate checks and configurations before production use.
# Customer-facing technical acceptance template; replace all example values.
name: "Customer Portal - Staging Acceptance"
url: "https://portal.example.com/health"
request:
method: GET
user_agent: "ipsonic-probe-acceptance/1.0"
headers:
Accept: "application/json"
timeouts:
connect: 3
response: 10
tls:
verify: true
min_valid_days: 30
tests:
status:
allow: [200]
headers:
exists:
- Content-Type
- Strict-Transport-Security
contains:
Content-Type:
- application/json
body:
contains:
- '"status"'
- '"healthy"'
not_contains:
- Traceback
- Internal Server Error
monitoring:
service_name: "Customer Portal Staging Acceptance"
output: text
on_failure: critical
thresholds:
response_time:
warning: 2
critical: 5
assertions:
- id: http.header
severity: warning
- id: http.status
severity: critical
- id: http.body
severity: critical