You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I currently don't have the environment to tests this local. If anyone have suggestion to solve the building error than we have a running test case. travis branch
@Nesquick
This is nice but a environment on this machine... this will never happen under a broken OS. And the machine is not strong enough to handle virtual machines too.
Back to topic:
I solve the building error and see now that the server is not running, perhaps anyone have a Idea.
Could you add a section in README.md how to run the tests?
My only concern is what this setup is a bit complex, what do we need grunt for? Maybe you could explain what's happening there. I would like to help you with this, but I don't see the latest travis build nor am I able to get this running on my machine.
Grunt is the only way I found to call node.js tests directly, if we can call the JS tests directly its better than my currently solution. I search only a few minuets for this solution.
Alternative I found selenium on ruby, this setup is not so complex.
Yes I can add this in to readme.md but in front of this I this stuff finished.
@ClemensSahs Thanks a lot! I will check this out en details to see if we can get rid of grunt and simplify the setup. But again, thank you very much for adding this 👍
Activity
OleMchls commentedon Oct 8, 2013
travis? 👍
ClemensSahs commentedon Dec 10, 2013
yes travis!
I currently don't have the environment to tests this local. If anyone have suggestion to solve the building error than we have a running test case.
travis
branch
until this evening
OleMchls commentedon Dec 10, 2013
Looks cool! Maybe we can help to get it running on your machine. What's missing?
ClemensSahs commentedon Dec 11, 2013
@Nesquick
This is nice but a environment on this machine... this will never happen under a broken OS. And the machine is not strong enough to handle virtual machines too.
Back to topic:
I solve the building error and see now that the server is not running, perhaps anyone have a Idea.
doku say that we can run with --detach or -B
OleMchls commentedon Dec 11, 2013
Could you add a section in README.md how to run the tests?
My only concern is what this setup is a bit complex, what do we need grunt for? Maybe you could explain what's happening there. I would like to help you with this, but I don't see the latest travis build nor am I able to get this running on my machine.
ClemensSahs commentedon Dec 11, 2013
Grunt is the only way I found to call node.js tests directly, if we can call the JS tests directly its better than my currently solution. I search only a few minuets for this solution.
Alternative I found selenium on ruby, this setup is not so complex.
Yes I can add this in to readme.md but in front of this I this stuff finished.
ClemensSahs commentedon Dec 11, 2013
all my builds you found on travis
ClemensSahs commentedon Dec 12, 2013
@Nesquick
now we have green tests
https://travis-ci.org/ClemensSahs/phpughh.github.com/builds/15333301
I rebase this and send a PR
icewolfs commentedon Dec 12, 2013
@ClemensSahs @Nesquick awesome!
OleMchls commentedon Dec 12, 2013
@ClemensSahs Thanks a lot! I will check this out en details to see if we can get rid of grunt and simplify the setup. But again, thank you very much for adding this 👍
So is this the current branch? https://github.com/ClemensSahs/phpughh.github.com/compare/feature;travis_2
Could your write one or two sentences what's happening and how to set it up?
ClemensSahs commentedon Dec 12, 2013
@Nesquick
yes readme is in my todo list ;)
no currently i rebase the history and pushing this up currently
branch: feature/travis

I send PR now ;) readme will follow sone as possible
OleMchls commentedon Dec 12, 2013
yep, lets continue this at the PR 😃
#66