Changes between Version 4 and Version 5 of GitHubTracPluginTests

Show
Ignore:
Timestamp:
09/24/10 23:40:11 (11 years ago)
Author:
cotto
Comment:

add better (or non-worse) instructions for testing the github hook

Legend:

Unmodified
Added
Removed
Modified
  • GitHubTracPluginTests

    v4 v5  
    8989 1. '''Verify that the svn revisions redirect the appropriate git commit at GitHub.''' (look for the git-svn-id on the GitHub page) 
    9090 
    91 === github hooks === 
     91=== github hook === 
    9292 
    93 ''The plugin responds correctly to GitHub's post-receive urls.'' 
     93''The plugin responds correctly to GitHub's post-receive callback.'' 
    9494 
    9595Procedure:  
    9696 1. Start with the generic config options. 
    97  1. Get an example of the data sent with a post-receive callback. (todo: how) 
    98  1. Use curl or wget to post the data to the github hook url (todo: specific instructions) 
     97 1. Get an example of the payload sent to a post-receive callback from http://www.postbin.org/12dx3gx .  Save it to a file and change one of the commit id and git-svn-id values to something unique (but still valid). 
     98 1. Use curl to post the data to the github hook url: curl --data-urlencode payload@your_file_here !http://localhost:8080/trac/test/github/APITOKEN (use the API token from github.apitoken in trac.ini) 
    9999 1. Create a wiki page that refers to the newly-added commit. 
    100100 1. '''Verify that the link to the commit is displayed correctly, including its tooltip.'''