Skip to content

Unittests #25

Open
Open

Description

@OleMchls

I guess this will never happen but would be super awesome ❤️

Activity

  1. OleMchls commented on Oct 8, 2013

    @OleMchls
    MemberAuthor

    travis? 👍

  2. ClemensSahs commented on Dec 10, 2013

    @ClemensSahs

    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

  3. OleMchls commented on Dec 10, 2013

    @OleMchls
    MemberAuthor

    Looks cool! Maybe we can help to get it running on your machine. What's missing?

  4. ClemensSahs commented on Dec 11, 2013

    @ClemensSahs

    @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

    task :travis do
      system "jekyll serve --detach --port 4000"
    end # task :travis
  5. OleMchls commented on Dec 11, 2013

    @OleMchls
    MemberAuthor

    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.

  6. ClemensSahs commented on Dec 11, 2013

    @ClemensSahs

    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.

  7. ClemensSahs commented on Dec 11, 2013

    @ClemensSahs

    all my builds you found on travis

  8. ClemensSahs commented on Dec 12, 2013

    @ClemensSahs

    @Nesquick
    now we have green tests

    https://travis-ci.org/ClemensSahs/phpughh.github.com/builds/15333301

    I rebase this and send a PR

  9. icewolfs commented on Dec 12, 2013

    @icewolfs
    Member
  10. OleMchls commented on Dec 12, 2013

    @OleMchls
    MemberAuthor

    @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?

  11. ClemensSahs commented on Dec 12, 2013

    @ClemensSahs

    @Nesquick
    yes readme is in my todo list ;)
    no currently i rebase the history and pushing this up currently

    branch: feature/travis
    Build Status

    I send PR now ;) readme will follow sone as possible

  12. OleMchls commented on Dec 12, 2013

    @OleMchls
    MemberAuthor

    yep, lets continue this at the PR 😃

    #66

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions