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

How to test? #4

Open
mavit opened this issue Jul 14, 2015 · 1 comment
Open

How to test? #4

mavit opened this issue Jul 14, 2015 · 1 comment

Comments

@mavit
Copy link
Contributor

mavit commented Jul 14, 2015

A couple of lines in the readme on how to run my own copy of the calendar website wouldn't go amiss, so I can check that the trivial patch I just submitted didn't contain any hilarious syntax-error typos.

I'm guessing I have to do npm something, then run node on something obvious to anyone who's ever used Node before?

@stuartlangridge
Copy link
Contributor

erm. The reason that how to test it oneself is not documented is that the calendar is reliant on having a Google calendar back end; you can't easily take that away. So it won't run for ordinary people, and explaining how to set up a calendar and access tokens so that the code can use that calendar is not very useful.

However, this does point to the notion that we ought to have a "halfway house" mode which allows one to test a specific individual feed and print out the output from it, to confirm that an addition like this does the right thing. So let's leave this issue open and perhaps we'll get a chance to do that.

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

2 participants