Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test Plan #1

Open
23 of 32 tasks
aaronpk opened this issue Nov 1, 2016 · 1 comment
Open
23 of 32 tasks

Test Plan #1

aaronpk opened this issue Nov 1, 2016 · 1 comment

Comments

@aaronpk
Copy link
Owner

aaronpk commented Nov 1, 2016

Testing your Subscriber

Discovery

  • GET or HEAD, finding the Link header with rel=hub and rel=self
  • GET and look in XML contents
  • GET and look in HTML contents
  • Must prioritize Link header over HTML link tag

Subscription

  • Request a subscription to a hub that sends a 307/308 redirect to another hub
  • Subscribe to a URL that returns a 301 redirect to another URL (see #98)
  • Subscribe to a URL that reports a different rel=self from the input URL

Tracking Features

  • Request a subscription with callback, mode, topic parameters
  • Request a subscription with a secret
  • Request a subscription with lease_seconds
  • Unsubscribe

Subscription Verification

  • Reject a verification request with an invalid topic URL

Tracking Features

  • Acknowledge a valid pending subscription

Distribution

  • Accept a valid signature for authenticated distribution
  • Reject an invalid signature
  • Reject delivery with no signature if subscription was made with a secret

Tracking Features

  • Return 2xx when the notification payload is delivered

Testing your Publisher

The spec only describes how the publisher advertise the hub and topic URLs.

  • Publisher advertises the URLs in HTTP headers
  • Publisher advertises the URLs in HTML tags
  • Publisher advertises the URLs in XML tags
  • Publisher advertises the hub URL in the .host-meta file

These tests are not for compliance, but help publishers test whether their feeds are working properly.

  • A notification is received when the publisher has updated the content

Testing your Hub

Subscription

  • Allows subscription requests with callback, mode and topic parameters
  • Allows subscriptions with a secret
  • Must ignore additional parameters
  • Must allow subscribers to re-request active subscriptions
  • Supports unsubscribing

Tracking Features

  • Allows subscribers to request a lease duration
  • Ignores a lease duration request

Distribution

  • Sends a notification with matching content type
  • Sends only a diff in the notification
  • Sends a notification with a valid signature
@aaronpk
Copy link
Owner Author

aaronpk commented Nov 17, 2016

Double check this list matches the exit criteria w3c/websub#56

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant