Announcement Announcement Module
No announcement yet.
Roo project not working until web integration tests are created Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Roo project not working until web integration tests are created

    Perhaps I'm misunderstanding how the web tier is supposed to work, but I don't seem to get anything showing up in tomcat until I create a selenium test.

    Like so:

    Am I doing something wrong? This is the stock vote example that comes with M2.

  • #2

    Thanks for providing this screencast. We should always do this - gives the whole thing a complete new dimension .

    I have just created a brand new project 'vote' on a Windows and also a Linux machine and it works fine for me... Go figure.

    I guess we need to take another look on a Mac machine... Can you swtich on 'development mode' before running the script and see if that causes any interesting output?

    Btw, you can simply run:

    roo> development mode
    roo> script vote.roo
    No need to import it as external file. This is because we ship the sample scripts in one of the jars already .



    • #3
      Oh nice. Is there anyway to save roo's outfile to a file? Or were you able to get everything you need from the screencast?


      • #4
        Well for the output you could simply copy the shell output to a file... but from the script I cannot see anything go wrong. Changing to 'development mode' does not show anything interesting either? Adding the selenium test does not really change the behaviour of the Spring MVC infrastructure.

        I guess I have to get my hands on a Mac to test this. Maybe you can open a Jira ticket for this and provide a link to your screencast.

        Can you also confirm the same happens when you run the clinic.roo and the wedding.roo scripts?



        • #5
          Done. Answered your questions and am watching the issue at

          Just let me know in the comments there if there's anything else I can do.


          • #6
            Thanks for this. I'll need a few days before I have time to look into this issue a little closer.



            • #7
              It appears this problem is more on your side rather than a general Roo or OSX problem. There is a video which shows Roo in action and the application working without having to generate any Selenium tests:


              I'll leave the bug ticket open until we find out more.