Revision bca58b0cef32b342eece2c135fdc62e32b69e557 authored by moz-wptsync-bot on 16 March 2018, 13:38:52 UTC, committed by moz-wptsync-bot on 20 March 2018, 02:29:46 UTC
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1445883 gecko-commit: 0f81334efa0a008db8931a41eef2d26a77d0e800 gecko-integration-branch: mozilla-inbound gecko-reviewers: smaug
1 parent c51eaff
CONTRIBUTING.md
Annotation-Protocol: Guidelines for Contributing Tests
======================================================
This document describes the method people should use for authoring tests and
integrating them into the repository. Anyone is welcome to submit new tests to
this collection. If you do, please create the tests following the guidelines
below. Then submit them as a pull request so they can be evaluated
Structure
---------
Tests are organized by client or server, and then by major section of the Annotation
Protocol specification. The folders associated with these are:
* client - tests a client needs to run
* server - tests to be run against a server
Within these folders, special files ending with the suffix ".html" provide the source
for the test as a set javascript calls to perform the test.
* scripts - JavaScript that are included by tests
* tools - supporting scripts and files
Client Test Cases
-----------------
@@@TODO@@@ describe the structure of client test cases.
Server Test Cases
-----------------
@@@TODO@@@ describe the structure of server test cases.
Command Line Tools
------------------
### Stand-alone Annotation Server ###
Computing file changes ...
