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

Tests #50

Closed
ineiti opened this issue Nov 2, 2015 · 4 comments
Closed

Tests #50

ineiti opened this issue Nov 2, 2015 · 4 comments

Comments

@ineiti
Copy link
Member

ineiti commented Nov 2, 2015

A lot of tests are failing - we should clean them up.

@ineiti
Copy link
Member Author

ineiti commented Nov 7, 2015

Just to be sure that the compilation doesn't fail, it could be enough to put a dummy-test in all directories (e.g. app/*), so when running go test, it tests at least whether everything compiles.

@nikkolasg
Copy link
Contributor

And/Or we could set up an associated Travis CI account so it automatically tries to build everything at each pushed commit.

@ineiti
Copy link
Member Author

ineiti commented Nov 9, 2015

Yes, there is quite a list on what we could/should do - I propose we do our monthly meeting early this week (Monday or Tuesday) and set up some more detailed ‘HOWTO’ about our desired workflow.

On 09 Nov 2015, at 08:44, nikkolasg notifications@github.com wrote:

And/Or we could set up an associated Travis CI account so it automatically tries to build everything at each pushed commit.


Reply to this email directly or view it on GitHub #50 (comment).

@ineiti
Copy link
Member Author

ineiti commented Nov 16, 2015

Closed by #90

@ineiti ineiti closed this as completed Nov 16, 2015
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